From 2dc7c1d39f97540b38c5139ff2b53a76aa941f7e Mon Sep 17 00:00:00 2001 From: mlsmaycon Date: Tue, 1 Sep 2026 12:36:33 +0000 Subject: [PATCH] Follow the self-service endpoint rename to agent-config The management PR renamed GET /api/agent-network/me/setup to /api/agent-network/agent-config before merging; point both mentions at the shipped path. --- src/pages/agent-network/index.mdx | 2 +- src/pages/manage/team/user-roles.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/agent-network/index.mdx b/src/pages/agent-network/index.mdx index 20994db7..a57cc4da 100644 --- a/src/pages/agent-network/index.mdx +++ b/src/pages/agent-network/index.mdx @@ -92,7 +92,7 @@ Managing Agent Network does not require full account admin rights. Two dedicated - **Agent Network Admin** fully manages providers, policies, guardrails, budgets, usage, access logs, and Agent Network settings, with read-only visibility into peers and team members (needed to build policies) and no access to the rest of the account. - **Usage Viewer** sees the usage and cost overview, with read-only access to the resources its filters resolve against (users, groups, peers, the provider list) - for finance and team leads tracking LLM spend. -Every user, with any role, can read the connection details their policies allow (endpoint, providers, models) through the self-service API (`/api/agent-network/me/setup`), and their own usage and requests through the regular usage and access-log endpoints, which answer with the caller's own data when the role has no account-wide access. See [User Roles](/manage/team/user-roles) for the full permission matrix. +Every user, with any role, can read the connection details their policies allow (endpoint, providers, models) through the self-service API (`/api/agent-network/agent-config`), and their own usage and requests through the regular usage and access-log endpoints, which answer with the caller's own data when the role has no account-wide access. See [User Roles](/manage/team/user-roles) for the full permission matrix. ## Next steps diff --git a/src/pages/manage/team/user-roles.mdx b/src/pages/manage/team/user-roles.mdx index 19076091..bcf7ac51 100644 --- a/src/pages/manage/team/user-roles.mdx +++ b/src/pages/manage/team/user-roles.mdx @@ -58,7 +58,7 @@ A `Billing Admin` manages billing only. They can access `Settings` → `Plans & An `Auditor` can read every configuration in the account but can't modify anything. ## User -A `User` has limited access: they can view the peers they own and other peers they're allowed to connect to. Every user can also read the Agent Network connection details their access policies allow via the self-service endpoint (`GET /api/agent-network/me/setup`) and their own usage and requests through the regular usage and access-log endpoints, which answer with the caller's own data when the role has no account-wide access - no role change or admin involvement needed. +A `User` has limited access: they can view the peers they own and other peers they're allowed to connect to. Every user can also read the Agent Network connection details their access policies allow via the self-service endpoint (`GET /api/agent-network/agent-config`) and their own usage and requests through the regular usage and access-log endpoints, which answer with the caller's own data when the role has no account-wide access - no role change or admin involvement needed. ## Roles and the API Roles apply the same way whether a user works in the dashboard or through the [NetBird management API](/api) - a user's permissions over API resources match their role. Every role except `User` can create a personal access token that carries the same permissions as that user's role, so they can interact with the API programmatically.