Role Based Access Controls Overview
Learn about permissions and roles within the Aisera Admin U
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 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 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.
Write
With Write access, users can view all existing data and interact with system features to observe and make necessary modifications or edits.
Read
Users with Read access can view data but cannot modify it. They must use a related entity for this purpose. For example, a user with Read privilege on an Integration doesn't grant access to the Integrations screen. However, a user with Write privileges on Data Sources allows viewing the linked Integration entity on the Data Source Detail page.
None
A user with no privileges to a feature will not be able to navigate to windows or view data related to the respective feature.
Last updated
Was this helpful?