Create a Copilot Studio Dataverse custom role.
Before you begin
Role required: User Security role
Procedure
-
Navigate to
-
Select New role and give it a name like SGC-Copilot Discovery (Read only).
Note: Start empty rather than copying, so you don't inherit stray privileges.
-
In the role editor, find each of the three tables and set only the Read privilege.
Three tables:
- Bot— The agents/copilots themselves.
- Botcomponent— Topics, entities, and other authored components.
- Conversationtranscript— The transcript records; the transcript body lives in the Content column, which comes back with the row's Read privilege (no separate file/attachment privilege needed for this table).
-
Set the Read access level to the scope your discovery needs.
For tenant/environment‑wide cataloging via a service principal, set Read to Organization (the filled full circle) on all three tables. Anything lower (User/BU) will silently hide records the app
user doesn't "own".
-
Select Save.