> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/aiseragpt/how-to-set-up-an-aiseragpt-bot/add-application-access-attributes.md).

# Add Application Access Attributes

{% hint style="info" %}
**NOTE:** application-level (AiseraGPT Details) permissions take precedence over tenant-level permissions. As a result, if you have read-only access defined at the application level, it may override tenant-level read/write permissions and prevent actions such as adding or removing tags on Requests.\
 

#### Recommended Workaround

1. Navigate to Settings → AiseraGPT with an Admin login
2. Open the application where the issue is observed.
3. Scroll to the bottom of the page and review the Access Attributes section.
4. Remove any application-level read-only access attributes:
   * Click Assign Access Attributes
   * Delete the relevant record by clicking the X icon
   * Click OK to save the changes

It is a best practice to validate this behavior in your staging tenant first and, once confirmed, apply the changes to your production tenants.
{% endhint %}

### To Assign Access Attributes to your Virtual Assistant: <a href="#pdf-page-teny1gndmmru7bngzxak-to-assign-access-attributes-to-your-virtual-assistant" id="pdf-page-teny1gndmmru7bngzxak-to-assign-access-attributes-to-your-virtual-assistant"></a>

1. Choose **Settings > AiseraGPT**, and then choose your bot from the virtual assistants shown on the page.<br>

   <div align="left"><figure><img src="/files/MuYM4U5cz3EUEjIsOrHr" alt="" width="438"><figcaption><p>Assign Access Attributes Button</p></figcaption></figure></div>
2. Click the **Add Access Attribute** link within the Assign Access Attributes window to add a new attribute.<br>

   <div align="left"><figure><img src="/files/n25U3RDHlfQmuMQ4UGQh" alt="" width="563"><figcaption><p>Assign Access Attributes Window</p></figcaption></figure></div>
3. Select an attribute **Name** and **Privilege** and then add an appropriate value.

## **Assign Application Access for PII by Role**

You can create a custom role and then give that role access to Personal Identifiable Information (PII), by choosing the piis attribute for your new role.

![](https://docs.aisera.com/~gitbook/image?url=https%3A%2F%2F2983236984-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiZkLJr3EjXkd2tHYiQJP%252Fuploads%252FANMpscRlZ8WA4lJv7VTZ%252Funknown.png%3Falt%3Dmedia%26token%3Deb9d3960-1461-4715-8afd-9c32a76f3e33\&width=300\&dpr=4\&quality=100\&sign=1c1f3a88\&sv=2)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aisera.com/aiseragpt/how-to-set-up-an-aiseragpt-bot/add-application-access-attributes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.