> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/codescan/getting-started/users-roles-and-permissions/adding-users-to-a-codescan-cloud-organisation/accepting-invitations-to-add-a-user-to-a-codescan-organization.md).
# Accepting invitations to add a user to a CodeScan Organization
#### Accepting an invitation (Auth0 only)
1. Wait for your Admin to invite you to the CodeScan Cloud organization.
2. If you can't find the invitation link in your Inbox, check Spam and Junk folders.
3. Once you have the invitation link, click on it (please note it's valid only for a certain period of time and can only be used once):
4. You will be redirected to the Login screen. As it's your first time to CodeScan, select the **Sign Up** option:
5. On the sign-up screen you will enter your details and create a password, which you will use to log into your CodeScan account:
6. Depending on your team's requirements, you can also enable MFA (can be done later)
7. Congrats! You should be able to access CodeScan now.
If you encounter any issues, please reach out to
---
# 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://knowledgebase.autorabit.com/product-guides/codescan/getting-started/users-roles-and-permissions/adding-users-to-a-codescan-cloud-organisation/accepting-invitations-to-add-a-user-to-a-codescan-organization.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.
