Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions concepts/policies/delegated-access-overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ This avoids temporarily granting the Delegated User root access — see [Caution
**Limitations:**
- You can’t assume the delegated user or its policies already exist. Before referencing it, you’ll need to call `fetchOrCreateP256ApiKeyUser` and `fetchOrCreatePolicies` to ensure the user and permissions are properly set up.

For a detailed step-by-step guide see [Client-side Delegated Access setup](concepts/policies/delegated-access-frontend).
For a detailed step-by-step guide see [Client-side Delegated Access setup](/concepts/policies/delegated-access-frontend).

### 2. Backend

Expand All @@ -56,7 +56,7 @@ If you adopt this approach, implement strict validation to confirm that:

For most end-user applications, it’s recommended to perform delegated access setup client-side, where all actions are explicitly initiated and approved by the user.

For a detailed step-by-step guide see [Server-side Delegated Access setup](concepts/policies/delegated-access-backend).
For a detailed step-by-step guide see [Server-side Delegated Access setup](/concepts/policies/delegated-access-backend).

## Frequently Asked Questions

Expand Down