> For the complete documentation index, see [llms.txt](https://docs.alphaus.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphaus.cloud/v3.0-english/getting-started/login-for-the-first-time.md).

# Login for the first time

## Provide your Cloud Account Credentials

Before you can use the software, you need to setup your vendor credentials first. For tutorials on steps to finding and providing credentials, please refer to each cloud vendor's references in the side menu.

## Create Roles & User Accounts

Mobingi ALM Enterprise Edition provides multiple user accounts accessibility and collaboration modules. You start with creating ALM user accounts that will be used for log in to ALM console. Users can collaborate on provisioning, deploying or monitoring resources on your cloud account. You should also assign them roles to limit the actions for each individual user account (or groups) on accessing certain resources which you want to protect by [RBAC](https://docs.mobingi.com/mobingi-alm/rbac/overview).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.alphaus.cloud/v3.0-english/getting-started/login-for-the-first-time.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.