> 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/integral-zone/iz-suite/iz-core/organization/roles.md).
# Roles
### Built-in Roles
| Role Name | Description | Modules .6+ |
| --------------------------------------------------- | -------------------------------------------------------------------------- | -------------------------------- |
| **`IZ Core Admin`** .6+ | Admin access to all IZ Core Modules | **`Organization`** |
| **`Global Settings`** | **`Agents`** | **`Users`** |
| **`Schedules`** | **`Audit`** .5+ | **`Quality Control Admin`** .5+ |
| Admin access to Quality Control Settings | **`Quality Gates`** | **`Quality Profiles`** |
| **`Rules`** | **`Metric Profiles`** | **`Metrics`** .4+ |
| **`IZ Pulse Admin`** .4+ | Admin access to IZ Pulse Settings | **`Status Pages`** |
| **`Categories`** | **`Endpoints`** | **`Maintenance Schedules`** |
| **`IZ Scan CLI`** | Role with appropriate permissions to be used with IDE Plugin or CICD Scans | **`IZ Scan CLI / IDE`** .3+ |
| **`_ORG_ IZ Eye Admin`** .3+ | Admin access to IZ Eye for a specific organization | **`Mule Application`** |
| **`Exchange APIs`** | **`API Manager Apps`** .2+ | **`_ORG_ IZ Scan Admin`** .2+ |
| Admin access to IZ Scan for a specific organization | **`Mule Projects`** | **`API Projects`** .6+ |
| **`IZ Core Viewer`** .6+ | View access to all IZ Core Modules | **`Organization`** |
| **`Global Settings`** | **`Agents`** | **`Users`** |
| **`Schedules`** | **`Audit`** .5+ | **`Quality Control Viewer`** .5+ |
| View access to Quality Control Settings | **`Quality Gates`** | **`Quality Profiles`** |
| **`Rules`** | **`Metric Profiles`** | **`Metrics`** .4+ |
| **`IZ Pulse Viewer`** .4+ | View access to IZ Pulse Settings | **`Status Pages`** |
| **`Categories`** | **`Endpoints`** | **`Maintenance Schedules`** .3+ |
| **`_ORG_ IZ Eye Viewer`** .3+ | View access to IZ Eye for a specific organization | **`Mule Application`** |
| **`Exchange APIs`** | **`API Manager Apps`** .2+ | **`_ORG_ IZ Scan Viewers`** .2+ |
| View access to IZ Scan for a specific organization | **`Mule Projects`** | **`API Projects`** |
#### Permissions Added in 26.4.1
* **AWS:** two permission categories, **`Falcon Eye AWS`** and **`Falcon Scan AWS`**, hold the permissions of each AWS service for IZ Eye (inventory) and IZ Scan (configuration scanning). A service's permissions are available only when the service is enabled on the tenant's licence. The administrator who onboards an AWS organization receives the AWS permissions on it automatically.
* **Java:** Java scan permissions are granted automatically on server start: every role that holds Python scan permissions on an organization receives the matching Java permissions there. Users see **`Java Apps`** after signing in again.
* **Languages added later:** when a new language or platform is added through seed data after the tenant was onboarded, every role of the tenant receives the new language's permissions wherever it holds the permissions of the related existing language (for example Java follows Python), on every organization of the tenant. Existing roles therefore see the new language's applications without manual changes.
* **Security tokens:** **`Generate Security Token`** allows a user to generate their own security tokens, and **`Generate Security Token For Another User`** allows generating tokens for other users and the **`Set Temporary Password`** and **`Reset MFA`** actions under **`Users`**.
### Roles
To view all roles in the system -
1. Navigate to **`Organization`** -> **`Roles`**
2. Click on the role name to edit the permissions assigned to the role
3. Choose the required set of permissions and click on Submit
### Create Role
To create a new role -
1. Navigate to **`Organization`** -> **`Roles`** and click on **`Create Role`**
Choose the required set of permissions
3. Choose the appropriate Organization and Environments (if applicable)
4. Click on Submit
### See Also
* [Organizations](/product-guides/integral-zone/iz-suite/iz-core/organization/organizations.md)
* [Users](/product-guides/integral-zone/iz-suite/iz-core/organization/users.md)
* [Invite User](/product-guides/integral-zone/iz-suite/iz-core/organization/invite-user.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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-core/organization/roles.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.
