> For the complete documentation index, see [llms.txt](https://docs.impossiblecloud.com/partner-portal-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.impossiblecloud.com/partner-portal-help/management-console-guide/getting-started/accessing-the-management-console.md).

# Accessing the Management Console

1. Visit the ICMC [login page](https://partner.impossiblecloud.com/).
2. Enter your registered email address.
3. Type in your password and click "Continue." For password requirements, see the next page.

{% hint style="info" %}
Brute-force protection ensures security against a single IP address attempting to attack a single user account. If a specific IP address fails multiple login attempts for the same user, brute-force protection takes the following actions:

* Blocks the suspicious IP address from logging in as that user.
* Sends an email notification to the affected user.
  {% endhint %}

Session lifetime limits determine how long the system should retain a login session. For security reasons, users are logged out automatically after certain intervals:

* **Inactivity timeout**: Period after a user's session expires - given they do not interact with the console. This occurs after **3 minutes** **of inactivity**.
* **Require login after**: Period after a user's session expires - independent of their interaction with the console. This is set to **30 days after login**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.impossiblecloud.com/partner-portal-help/management-console-guide/getting-started/accessing-the-management-console.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.