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

# Cloudbrink Management Portal

Cloudbrink provides customers with a simple and easily accessible web console for managing their account. Customers can define the policies and also get visibility & troubleshooting information from the same management portal.&#x20;

&#x20;

Cloudbrink management portal is available at <https://admin.cloudbrink.com/>[.](https://admin.cloudbrink.com/) Customers can login to their account using the credentials shared by the Cloudbrink Sales/Support team.&#x20;

&#x20;

The management portal login is protected using a 2-factor authentication (2FA) method. There are two options in the 2FA.

&#x20;

1\)     SAML Auth → If customer is using SAML based authentication by integrating with any standard IDP (Azure AD, Okta, PingID, OneLogin, etc.), then the IDP takes care of 2FA as per customer’s security policies.&#x20;

2\)     Local Admin Users → Customers can add some admin user accounts locally on the Cloudbrink management portal. In this case, the admin user account will need a username, password and email ID. The admin user can login using username + password + the OTP sent to the email ID as part of login process.

(a) Note: It is important to give a valid email ID for local admin user accounts because OTP will be sent to this email ID for second factor auth.&#x20;


---

# 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.cloudbrink.com/configuration/cloudbrink-management-portal.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.
