> For the complete documentation index, see [llms.txt](https://help.cloudstoragesec.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cloudstoragesec.com/trouble-shooting/password-not-received.md).
# Password not received after deployment
Sometimes you may not receive the welcome email which includes your temporary password. If that's the case, here are the steps to logging in for the first time.
## AWS Cognito
1. Go to AWS Cognito and click into the `CloudStorageSecPool`.
2. If you go into the `admin` user, you will see that a password reset is not available. Therefore you will need to create a new user. Once you create a new user, mark the email as verified and set your password from here.
3. Once the user is created, you will need to add it to two Groups, `Admins` and `Primary`.
{% hint style="warning" %}
**Sometimes you may run into an issue where the Groups are not created**
In that case you will have to go to DynamoDB and set both VisibleGroups and Groups table, as the screenshots below show:
{% endhint %}
Add user to group in Cognito
3. You are now ready to log into our console and start using our solution (please note: a password change will be needed upon first login for this new user)
If you are still experiencing issues, please [Contact Us](/contact-us.md).
---
# 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://help.cloudstoragesec.com/trouble-shooting/password-not-received.md?ask=&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.
{% endhint %}
