Skip to content

Commit d1aee51

Browse files
committed
chore(agentic ai): elaborated on the org-scoped role requirement for nrai
1 parent 96b2e7c commit d1aee51

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

src/content/docs/agentic-ai/agentic-integration/introduction-agentic-ai.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,8 @@ New Relic's agentic integration provides an AI-driven solution to help automate
2121
Our integration partners will manage client applications and maintain user tokens when you or any of your users authenticate to New Relic through the partner's integration. The third party partner will have the same level of access to New Relic as the user who authenticated for the amount of time configured in the user settings, as the tokens are used on their behalf. This arrangement helps to provide seamless integration and functionality. For more information, you can refer to the partner's documentation which details their token usage and management practices.
2222

2323
### Role based access control (RBAC)
24+
New Relic's agentic integration capabilities are granted via organization-scoped roles within New Relic's RBAC system. Users gain access by belonging to a group with an assigned organizational role that includes these capabilities. Individual accounts do not require direct configuration.
25+
2426
Currently, RBAC can be accessed through API interfaces. If you are interested in utilizing RBAC via API, feel free to contact us at [email protected]. For detailed guidance on setting up RBAC, refer to our [account user management tutorial](/docs/accounts/accounts-billing/new-relic-one-user-management/account-user-mgmt-tutorial).
2527

2628
## Current integrations [#integrations]

0 commit comments

Comments
 (0)