Skip to content

Commit 94c8a4f

Browse files
committed
Clarify token org-scoping & allow unsafe PR checkout
1 parent 9f4a651 commit 94c8a4f

2 files changed

Lines changed: 3 additions & 2 deletions

File tree

‎.github/workflows/build-and-preview-docs.yml‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,7 @@ jobs:
3636
persist-credentials: false
3737
submodules: recursive
3838
fetch-depth: 0
39+
allow-unsafe-pr-checkout: true
3940

4041
- name: Checkout for cleanup
4142
if: github.event.action == 'closed'

‎content/en/cloud/concepts/identity-and-security/tokens.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,9 @@ Layer5 Cloud API tokens are scoped to your user account, not to a specific organ
2424

2525
## Privilege Scoping
2626

27-
API tokens in Layer5 are **identity-scoped**. This means they inherently carry the exact same privileges, roles, and permissions as your user account.
27+
API tokens in Layer5 are **identity-scoped**. This means they inherently carry the exact same privileges, roles, and permissions as your user account within the organization and environment selected by the request context.
2828

29-
Layer5 does not currently support fine-grained, token-specific privilege scopes (for example, generating a strictly "read-only" token if you have "read-write" permissions). The token grants the bearer the same level of access you have across all environments and organizations you are a member of.
29+
Users can have different roles and permissions in different organizations, meaning a token does not grant one uniform privilege set across every organization. However, Layer5 does not currently support fine-grained, token-specific privilege scopes (for example, generating a strictly "read-only" token if you have "read-write" permissions).
3030

3131
## Creating tokens
3232

0 commit comments

Comments
 (0)