← API keys

API Key Create

auth / security · features · API keys
One issuance dialog for all entry points. The mechanic is in API keys.
Wireframe

Self-issuance. A key for yourself, from your own profile.

form
Create API key 1
Name
My laptop script optional 2
Access
read-only writing via the key isn't available 3
Sources
all available or choose manually
Expiry
90 days
30 / 90 / 365 days / never 4
key created
Key created
The full value is shown once — copy it and store it somewhere safe. 5
ach_7f2k9xQ…vD3w
  1. 1 Dialog title. Self-issuance — from your own profile, no user field.
  2. 2 Name — an optional human-readable label ("My laptop script", "CI server") so the key is recognizable in the list beyond its prefix. Empty is fine; the owner can rename it later from the profile.
  3. 3 Key scope: "Access" (read-only) and "Sources" (all available by default, narrowed manually). The permissions cap is in API keys.
  4. 4 Expiry — a preset or never.
  5. 5 The value is shown once — it can only be copied here.

Issuance — Owner / Admin. A key for an employee, from the key list or the user card. The finish — the same one-time value display.

form · issuance to a user
Create API key
User
Soko
Dmitry Sokolov dmitry@company.com Olga Sokolovskaya olga.s@company.com
1
Name
Data export bot optional · the owner can rename it 2
Access
read-only no wider than the employee's permissions 3
Sources
all available Jira Slack or choose manually
Expiry
90 days
  1. 1 Choosing a user — typeahead by name or email. The suggestion mechanic is in API keys.
  2. 2 Name — a starting label; optional. It belongs to the owner, who is free to rename the key later from their profile.
  3. 3 Scope — the employee's permissions, not the administrator's; a key can't be issued wider than their role.