mirror of
https://github.com/Unleash/unleash.git
synced 2024-10-28 19:06:12 +01:00
d5fbd0b743
## What This (admittedly massive) PR updates the "physical" documentation structure and fixes url inconsistencies and SEO problems reported by marketing. The main points are: - remove or move directories : advanced, user_guide, deploy, api - move the files contained within to the appropriate one of topics, how-to, tutorials, or reference - update internal doc links and product links to the content - create client-side redirects for all the urls that have changed. A number of the files have been renamed in small ways to better match their url and to make them easier to find. Additionally, the top-level api directory has been moved to /reference/api/legacy/unleash (see the discussion points section for more on this). ## Why When moving our doc structure to diataxis a while back, we left the "physical' files lying where they were, because it didn't matter much to the new structure. However, that did introduce some inconsistencies with where you place docs and how we organize them. There's also the discrepancies in whether urls us underscores or hyphens (which isn't necessarily the same as their file name), which has been annoying me for a while, but now has also been raised by marketing as an issue in terms of SEO. ## Discussion points The old, hand-written API docs have been moved from /api to /reference/api/legacy/unleash. There _is_ a /reference/api/unleash directory, but this is being populated by the OpenAPI plugin, and mixing those could only cause trouble. However, I'm unsure about putting /legacy/ in the title, because the API isn't legacy, the docs are. Maybe we could use another path? Like /old-docs/ or something? I'd appreciate some input on this.
42 lines
1.7 KiB
Plaintext
42 lines
1.7 KiB
Plaintext
---
|
|
title: How to create Personal Access Tokens
|
|
---
|
|
|
|
:::info availability
|
|
|
|
Personal access tokens are planned to be released in **Unleash 4.17**.
|
|
|
|
:::
|
|
|
|
Personal access tokens are a tool to enable a user to use the Admin API as themselves with their own set of permissions, rather than using an admin token. See [_how to use the Admin API_](how-to-use-the-admin-api.md) for more information.
|
|
|
|
## Step 1: Navigate to the personal access tokens page {#step-1}
|
|
|
|
Open the user profile pane in the admin UI and select the _view user profile_ menu item (available at the URL `/profile`).
|
|
|
|
|
|
|
|
Select the "Personal Access Tokens" menu item.
|
|
|
|
|
|
|
|
## Step 2: Navigate to New Token {#step-2}
|
|
|
|
Navigate to "New Token".
|
|
|
|
|
|
|
|
## Step 3: Fill in the create personal API token form and create it {#step-3}
|
|
|
|
Give your token a description and optionally set an expiry date. By default the expiry date is set to 30 days.
|
|
|
|
|
|
|
|
## Step 4: Save your token {#step-4}
|
|
|
|
Once your new token is created, the popup will display the new token details. You must save your token somewhere outside of Unleash, you won't be able to access it again.
|
|
|
|
|
|
|
|
Your personal access token can now be used in place of an [admin token](../reference/api-tokens-and-client-keys#admin-tokens).
|