# Permissions in the Agentic RAG connector

> info **PREREQUISITES**: You can use this capability in Sitefinity Cloud as of version Sitefinity CMS 15.4.8628.

This article applies to AI capabilities powered by the Progress® Agentic RAG - such as AI Search, AI Assistant widgets, and Hybrid backend search.

When Sitefinity content is indexed in Progress Agentic RAG, the connector maps Sitefinity's permission model to the `access_groups` security mechanism in Progress Agentic RAG. This ensures that AI-powered search results respect the same access rules that govern content visibility in Sitefinity CMS.

For a general overview of how permissions work in Sitefinity CMS, see [Permissions](https://www.progress.com/documentation/sitefinity-cms/overview-permissions).

> important **IMPORTANT**: When making third-party calls to the knowledge box, make sure the `security` field in the request body is populated with an access group. This ensures that the security lookup phase is performed, and content permissions are respected.

## How permissions are mapped

The Agentic RAG connector respects only the permissions for general CRUD operations defined in Sitefinity CMS:

| Sitefinity permission | Respected by Agentic RAG connector |
| --------------------- | ---------------------------------- |
| View                  | Yes                                |
| Create                | Yes                                |
| Modify                | Yes                                |
| Delete                | Yes                                |
| Change owner          | **No**                             |
| Change permissions    | **No**                             |
| Unlock                | **No**                             |

In the NucliaDB API, permissions are represented through the `security.access_groups` property of each resource. The principal IDs in Sitefinity CMS (users and roles) are mapped to access group identifiers sent to Progress Agentic RAG.

## Publicly visible items

When a content item has no access restrictions, that is, at least one of the CRUD permissions is granted to *Everyone*, the connector sends an empty `access_groups` array to Progress Agentic RAG. This signals that the resource is publicly accessible and is returned to all users in search queries.

> important **IMPORTANT**: If any single CRUD permission is set to *Everyone*, the item is considered publicly visible, even if the other CRUD permissions are restricted to specific roles such as *Administrator* only.

## Role-based access groups

When a content item has permissions restricted to specific roles, the connector collects the principal IDs of all roles that have any CRUD permission granted and sends them to Progress Agentic RAG as `access_groups`.

> success **EXAMPLE**: If the *View* permission on an item is granted to both the *Backend users* role and the *Administrators* role, the Agentic RAG connector sends both role identifiers as access groups for that resource.

Progress Agentic RAG powered search and ask API calls support a `security` parameter that accepts the `access_groups` of the currently authenticated user, allowing the Agentic RAG connector to filter results so that only resources matching the specified groups are returned.

## Permission synchronization

Permissions are synchronized to the Agentic RAG connector automatically through scheduled tasks. You do not need to manually trigger an update.

## Permission inheritance

**Child items** inherit permissions from their parent by default. When you change permissions on a parent item, child items that are set to **inherit** are also updated automatically. Child items with manually overridden permissions are not affected by parent permission changes.

## Search filtering by permissions

All search operations powered by Progress Agentic RAG are always filtered by the *View* permission.

Search results only include resources that the current user is authorized to view, based on the access groups sent with the search request.

## Module Builder field-level permissions

If you use *Allow permissions per field* in Module Builder and any field-level view restrictions are active, the item is treated as not publicly visible, even if the item-level *View* permission includes *Everyone*.

In this case, the connector sends the applicable access groups to Progress Agentic RAG. Users who do not belong to the required access groups will not see the item in the search results.

## Known limitations

The following behaviors and limitations apply to the Progress Agentic RAG permissions integration:

### Administrators always see all items

Administrator users always have access to all indexed content in Progress Agentic RAG search results, regardless of the access groups configured on individual resources.

### Deny permissions

As of Sitefinity CMS 15.4.8635, Progress Agentic RAG-powered search enforces explicit *Deny* permissions assigned to users and roles in Sitefinity CMS.

> info **NOTE**: In Sitefinity CMS 15.4.8628 through 15.4.8634, explicit *Deny* permissions are not enforced. These versions only use *Allow* permissions when constructing access groups. Do not rely on *Deny* permissions to restrict content visibility.

> important **IMPORTANT**: If you upgrade from a version earlier than 15.4.8635 and have explicit *Deny* permissions set on existing items, you must resend those items to the Progress Agentic RAG knowledge box for the *Deny* permissions to be taken into account. To do this, either republish each affected item individually, or resend the entire connection to the knowledge box. Resending the connection sends all items, not only the ones that need an update.

### Owner role is ignored

The *Owner* role in Sitefinity is not taken into account in Agentic RAG connector. Content ownership does not grant any special search visibility.

### Suggestions do not support permission filtering

Suggestions do not support permission filtering. Do not rely on AI suggestions as a secure content discovery mechanism when strict permission enforcement is required.

### Change owner, Change permissions, and Unlock are not respected

Only the *View*, *Create*, *Modify*, and *Delete* permission types are mapped to access groups. Actions such as *Change owner*, *Change permissions*, and *Unlock* have no effect on what is indexed or visible in Agentic RAG connector.

## Additional resources

* [Permissions](https://www.progress.com/documentation/sitefinity-cms/overview-permissions)
* [Permissions by section](https://www.progress.com/documentation/sitefinity-cms/administration-global-and-section-permissions)
* [Permissions of individual items](https://www.progress.com/documentation/sitefinity-cms/administration-permissions-of-individual-items)
* [Progress Agentic RAG Search API](https://docs.rag.progress.cloud/docs/api/#tag/Search)
