> For the complete documentation index, see [llms.txt](https://docs.north.cloud/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.north.cloud/docs/account-management/settings/iam-permissions/getting-started.md).
# Getting Started
How to begin granting permissions across your team or organization.
### To get started with IAM Permissions
1. Navigate to **Settings** in [app.north.cloud](https://app.north.cloud)
2. Select **IAM Permissions**
3. Click **Invite user**
4. Choose the cloud accounts the user can access
5. Assign feature-level permissions
6. Send the invite
New users do not receive full access by default. All access must be explicitly granted during the invite process.
### Update permissions over time
Permissions can be updated at any time as roles change or teams grow.
Admins can:
* Add or remove account access
* Change feature permissions
* Restrict or expand user capabilities
Changes take effect immediately.
### Using IAM Permissions with Noros
Noros respects user permissions.
When a user interacts with Noros:
* Noros can only retrieve data the user has access to
* Restricted accounts or features are excluded from responses
If you want to limit what data Noros can surface for a user, restrict their account or feature access accordingly.
More granular Noros controls are planned for future updates.
---
# 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.north.cloud/docs/account-management/settings/iam-permissions/getting-started.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.
