# Aisera Platform Permissions ## Permissions Below is a list of each **Permission** accompanied by a description of its corresponding features. ### Aisera GPT A user may create, view the details of, and manage Aisera applications from this window. Select **Settings > AiseraGPT** in the Admin UI to view **AiseraGPT**

### Access Control **Access Attributes** are settings that allow you to dictate which information is used and delivered in interactions with end users. They enable you to establish access controls and restrictions on documents based on user and document attributes ingested into the Aisera Application. A User can manage **Access Attributes** from this window. Select **Settings > Access Control** in the Admin UI to view **Access Control**.

### AI Discovery CMDB The **Configuration Management Database Discover (CMDB)** allows AI to determine and create a list of systems, applications, networks, storage, and business services on your network inventory. Select **AI Discovery - CMDB** on the left navigation pane to navigate to the **AI Discovery - CMDB** window.

### AI Workflows **Workflows** provide your Aisera application to integrate with third party systems, execute business logic, and follow predefined steps to complete tasks. You can create, manage, and edit workflows in the **AI Workflow Studio**. Select **AI Automation > AI Workflow Studio** on the left navigation pane to navigate to the **AI Workflow Studio**

### Audit Changes you make to objects in the Aisera platform are logged as audit logs. Users who have access to the Audit feature can view audit log history. Select **Settings > Audit Trail** in the Admin UI to view the log history.

### Channel Channels are the medium through which end users engage with Aisera Application. Channel configurations are available for users who have access to this feature. Select **Settings > Channels** in the Admin UI to add or manage channels.

### Conversation Message Systems messages that are provided by default for **Message Keys** (scenarios) listed. **Messages** can be customized. Select **Settings > AiseraGPT** and then open or create a new application. Choose **View App Conversation Messages** to see the default messages associated with Aisera platform. Hover over the right-side of a line item and click the **pencil** icon to edit/customize a message.

Conversation Messages for a Specific Application or Bot

### Configurations The **Configurations** window allows you to configure tenants settings. Select **Settings > Configuration** to navigate the **Configuration** window.

### Data Source This feature stores the configuration information for the data source that you are integrating with your application. This is the pass-through information that allows the Aisera platform to access your data source. To set up your data sources, go to **Settings > Data Source**. You can open an existing data source or create a new one. To manage a data source, select it to view or modify its details. Enable editing by clicking the pencil icon at the top.

### Data Type A **Data Type** in Aisera is a custom entity used as a Data Source for **Events** and **Triggers**. It includes select data fields obtained from User and Ticket Learning Jobs Select **Settings > Data Types** on the left navigation pane to view, create, manage, and edit **Data Types** within the Aisera Platform. Users with **Write** permissions can view and edit Data Types. Users with **Read** permissions can view Data Types but not edit them. The **Data Types** window is hidden for users with **None** permissions.

### Direct Escalation Select **AI Workbench > Unresolved** in the left navigation pane. Then select the **Direct Escalation** tab to see the **Direct Escalation** window.

### Email Template Email templates are used with **Campaigns** & **Approvals**. Select **Settings > Email Templates** to view existing templates that are available for your application. You can select the list or document view in the upper-right corner of the window. Choose the **pencil** icon to edit a template.

### Event Trigger The **Event Studio** is a feature that allows you to build AI automations without writing code. Select **AI Automation > Event Studio** from the left navigation panel to view the **Event Studio** window.

### Hyperflow Hyperflows are a form of Workflow where the flow of the conversation and the APIs chosen to fulfill the user's request are determined by the AI. A user with **None** permissions will be unable to view Hyperflows or navigate to the **Hyperflows** window. **A user with Read** permissions will be able to view created Hyperflows and navigate to the **Hyperflows** window. Hyperflows will also be visible from other windows the user has permissions to, such as when displaying connected Hyperflows from the **Workflows** window. A user with **Write** permissions will be able to view and create Hyperflows from the **Hyperflows** window. They will also be able to view the names of connected workflows connected to Hyperflows regardless of their permissions. Navigate to **AI Automation > Hyperflows** to view the **Hyperflows** window.

### Integrations This entity stores the authentication and authorization data for data sources that you connect to Aisera Application. Choose **Settings > Integrations** to see a list of your applications and the integrations associated with each. You can view the integrations as a list or as boxes with icons that show the logo for each integration. From either view, you can click the **pencil** icon to edit your integration data. You can also create a new integration when you create a new application, as part of the **Add Data Source** command.

### Intelligent Alert Select **AI Observability > Intelligent Alerts** in the left navigation panel to navigate to the **Intelligent Alerts** window.

### Intents This feature relates to the data stored for the **Intents** and the associated mapping to **Fulfillments**. **Intents** are topics that the bot can serve. This permission encompasses a number of features within the Aisera Admin UI. These features include **Agent Assist, AI Lens, AI Workbench, Campaigns, Gen AI Learning, Intents, Knowledge,** and **Service Catalog.** Select **Agent Assist** on the left navigation pane to see the **Agent Assist** window.

Select **AI Lens** on the left navigation pane to see the **AI Lens** window.

The **AI Workbench** is a collection of features. To see the associated windows select **AI Workbench** on the left navigation window.

Select **Campaigns** in the left navigation panel to view the **Campaigns** window.

Select **Gen AI Learning** in the left navigation panel to view the **Generative AI Learning** window.

Select **Intents** in the left navigation panel to view the **Intents** window. You can select new Intents from the **Intents Library**, edit existing Intents, or create your own. You can see other objects that are associated with an Intent from the **Intents** window.

Select **SOR > Knowledge Documents** to navigate to the **Knowledge Documents** window. Intents only provides **Read** permissions to the user.

Select **SOR > Service Catalog** to view the **Service Catalog Items** window.

### Intents Review Select **AI Workbench > Review** and select the **Intents Review** tab to view the **Intents Review** window.

### Job Execution This entity stores the information about system and user jobs that have been run from your application, like **Knowledge Generation**, **Ticket Learning**, and **Knowledge Learning**. The data stored includes the name of the job, the pipeline status, user who ran the job, the start time, and the job duration. **Jobs** are triggered automatically and provide a view only access to the jobs. Select **Settings > Jobs** to see the list of jobs that have been run from your application. To run a job, you need to go to the related windows: * **Content Generation > Knowledge Generation** * **Gen AI Learning > Ticket Learning** * **Gen AI Learning > Knowledge Learning**

In the **Name** pull-down list at the top left of the **Jobs** window, you can search for jobs that have `Knowledge Generation` in the name. ![](https://3281977978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvBFXjH9S1CAy9f5hzg5Q%2Fuploads%2F4JR2yoYKWtfYDkmAWhlx%2Funknown.png?alt=media\&token=87511dfd-a639-4141-8787-e1025883a0db)
### Knowledge This entity stores the information from **Knowledge Articles** that are ingested into your application. Ingested content is also referred to as the **Source of Record (SOR)** in the Aisera platform. Select **SOR > Knowledge** to see a list of the Knowledge Base articles that have been ingested into your application. You can edit the data or apply templates to the data, if you have write privileges to this entity.

### LLM Prompts System This permission allows a user to view, create, and manage **System Prompts** in the **Prompt Studio**. This permission requires that a user have at least **Read** privileges for [**Prompt Studio**](#prompt-studio). Select **LLMs > Prompt Studio** to view the **Prompts Studio** window. ### LLM Prompts User This permission allows a user to view, create, and manage **System Prompts** in the **Prompt Studio**. This permission requires that a user have at least **Read** privileges for [**Prompt Studio**](#prompt-studio). Select **LLMs > Prompt Studio** to view the **Prompts Studio** window. ### Possible Issues (previously Major Incidents) Allows users to view, create, and manage **Possible Issues**. It also determines the visibility of the **AI Observability** navigation option on the left navigation panel. Navigate to **AI Observability > Possible Issues** to view the **Possible Issues** window.

### Model Users with read permissions can view system jobs, while users with write permissions can execute jobs. ### Model Job A user with write permissions will be able to edit job configurations. ### Ontology This permission allows a user to control access to the **Ontology** window. This permission does not allow users to edit **Ontologies**. Select **LLMs > Ontologies** on the left navigation panel to see the **Ontologies** window.

### Ontology Entity This permission allows a user edit, create, and manage ontologies. This permission requires that a user has at least **Read** permissions for [**Ontology**](#ontology). Select **LLMs > Ontologies** on the left navigation panel to see the **Ontologies** window. #### Publish to SOR This permission allows a user to publish a Knowledge Base Article generated from a single ticket to the system of record (SOR). Select **Content Generation > Knowledge Generation individual Ticket** to see Knowledge Base Artilces generated from a single ticket and related actions.

Knowledge Generation Individual Ticket Window

### Prompt Studio This permission allows a user to view the **Prompt Studios** screen. Select **LLMs > Prompt Studio** to view the **Prompts Studio** window.

### Privacy Access This permission manages the visibility of Personally Identifiable Information (PII) in the Aisera Admin UI. Users with **Read** permissions can view PII such as names or emails, whereas this infomation will be obscured for users with **None** permissions. This will also affect data extracted from the platform. When a user with **None** permissions in **Privacy Access** downloads information, such as campaign reports, any Personally Identifiable Information (PII) will be obfuscated or removed.

### Request This entity holds the request history. Select **Requests** to see a list of the Requests that customers have entered into your application. If you have **Write** permission to the **Requests** entity, you can choose from different visualizations for the **Requests Over Time** metric in the **Requests** window. The lower part of the Requests window contains a list of your requests that you can customize by adding or removing columns. You can also export the list to a CSV file.

### System Trigger This entity stores the data f**or System Triggers**, which are triggers used within **Workflows**. Select **Settings > System Triggers** to add or modify a schedule-based or event-based **System Trigger** to kick off a **Workflow**. This involves creating a **Trigger** in the **System Triggers** window, applying it to a **Workflow**, and then setting **Scheduled** or **Event** to start the trigger.

### Tickets This entity holds the data for the tickets that have been ingested into your application. Select **SOR > Tickets** to see a list of the **Tickets** that have been ingested into your application. If you have **Write** permission to the **Ticket** entity, you can choose from different visualization charts for the **Tickets Over Time** metric in the **Tickets** window. The lower part of the **Tickets** window contains the list of your tickets that you can customize by adding or removing columns. You can also export the list to a CSV file.

### Users This object stores the user data ingested to the application from your **System of Record (SOR)**. This data must be ingested, and therefore, it is not editable. Select **Users** to see the list of users that have been ingested into your application. You can add or remove columns from the list, or export the list as a CSV file, but you cannot edit the user list, since it must be ingested.

### User Accounts Allows a user to view, create, and manage **User** accounts and roles on the Aisera platform. Navigate to **Settings > User Accounts** to view the **User Accounts** window.