User Rights¶
Roles¶
There are different roles available for use in Copilot Studio. Learn more about the Production Copilot User Rights.
| Roles | Description |
|---|---|
mdsp:core:copilotstudio.viewer | Can use Copilot Studio in read-only mode but cannot see skill endpoints or instructions. The default role mdsp:core:StandardUser includes this role automatically and has the same rights. |
mdsp:core:copilotstudio.admin | Can use Copilot Studio and see all configured agents and skills. Can create skills in Visual Flow Creator. The default role mdsp:core:TenantAdmin includes this role automatically and has the same rights. |
Testing¶
For testing an agent, the copilot chat is always using the roles and scopes of the hosting application. In case a skill is using an internal Insights Hub API, the user token is used.
For example, in Insights Hub Monitor, the copilot chat would have the rights to read events, assets, and cases. In Asset Health and Maintenance, the copilot chat would have access to the APIs used there.
In Copilot Studio, the same set of roles and scopes is configured as in Insights Hub Monitor. So if you try to create a skill that creates an asset, it will fail in Copilot Studio because it has no related roles or scopes for it.
In this case, a skill can be created in Visual Flow Creator, where the authentication can be managed by using a http request node and configuring the authentication.