Mirrors/unleash.unleash
1
0
Fork 0
mirror of https://github.com/Unleash/unleash.git synced 2025-04-10 01:16:39 +02:00
Code Issues Projects Releases Wiki Activity

docs: add note about client tokens changing with v 4.10

Browse Source
This commit is contained in:
Thomas Heartman 2022-04-19 11:08:02 +02:00
parent 54bfe7323d
commit 9d2ef0c47f
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/docs/reference/api-tokens-and-client-keys.mdx
View File

@ -42,7 +42,7 @@ Support for scoped admin tokens with more fine-grained permissions is currently
- Register applications with the Unleash server
- Send usage metrics
When creating a client token, you can choose which projects it should be able to read data from. You can give it access to a specific list of projects or to all projects (including projects that don't exist yet).
When creating a client token, you can choose which projects it should be able to read data from. You can give it access to a specific list of projects or to all projects (including projects that don't exist yet). Prior to Unleash 4.10, a token could be valid only for a *single project* or *all projects*.
Each client token is only **valid for a single environment**.