# Aisera Platform Roles and Permissions

## Introduction to Aisera Permissions

The Aisera Admin UI enables you to manage administrators, developers, and other team members responsible for configuring and maintaining Aisera Applications. It offers comprehensive tools for creating, managing, and restricting team members using a **Role Based Access Control System (RBAC)**. This ensures that users can only access features and data relevant to their roles, and enforces the principle of least privilege on the Aisera Platform. 

## Core Concepts

### Aisera Platform Permissions

Permissions in the Aisera platform are feature-based, ensuring that user access within the Admin UI is determined by roles. Users are granted various levels of access to features like **Intents**, **Fulfillments**, **Tickets**, and **Data Sources**. Some roles allow users to edit features, some only allow viewing, while others may restrict access entirely.

### User Roles

By default, the Aisera Admin UI includes [predefined roles](/aisera-platform/tenant-setup/aisera-platform-configuration/aisera-platform-roles-and-permissions/built-in-user-roles-and-permissions.md) with specific responsibilities and capabilities, ensuring team members have appropriate access levels. Each role is associated with permissions for different features within the Admin UI, allowing efficient management of the Aisera platform and applications.

If you are seeking more granular control over access and permissions, please refer to our [Managing Roles](/aisera-platform/tenant-setup/aisera-platform-configuration/aisera-platform-roles-and-permissions/managing-user-roles.md) documentation for detailed guidance on creating and customizing roles to suit your specific needs.

### Privilege Levels

Each user role has a **Privilege** level tied to each entity within the Admin UI. These **Privilege** levels are **Write**, **Read**, and **None**.

<table><thead><tr><th width="120">Priviledge</th><th></th></tr></thead><tbody><tr><td><strong>Write</strong></td><td>With <strong>Write</strong> access, users can view all existing data and interact with system features to observe and make necessary modifications or edits.</td></tr><tr><td><strong>Read</strong></td><td>Users with <strong>Read</strong> access can view data but cannot modify it. They must use a related feature for this purpose. For example, a user with <strong>Read</strong> privilege on an <strong>Integration</strong> doesn't grant access to the <strong>Integrations</strong> screen. However, a user with <strong>Write</strong> privileges on <strong>Data Sources</strong> allows viewing the linked <strong>Integration</strong> entity on the <strong>Data Source</strong> Detail page.</td></tr><tr><td><strong>None</strong></td><td>A user with no privileges to a feature will not be able to navigate to windows or view data related to the respective feature.</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.aisera.com/aisera-platform/tenant-setup/aisera-platform-configuration/aisera-platform-roles-and-permissions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.