Access keys
This behaviour is changing. As of: 2026-09-02. Current commercial details: uely.ch/preise.
An access key is a long-lived password for machines. You create it yourself and give it to a script of your own — a report that pulls figures from your area every night, say.
Settings → Access keys → Create token.
Key or program?
Section titled “Key or program?”| Access key | Connected program | |
|---|---|---|
| For | your own scripts | someone else’s programs and assistants |
| Granted | by you directly | by you on a consent screen |
| Expires | after 90 days | access ends when you disconnect |
In short: if you wrote the script, use a key. If someone else’s program wants your area, let it take the consent route — there you see what it may do, and can disconnect it on its own.
The key is shown once
Section titled “The key is shown once”You see it exactly once, when you create it. We do not store it in the clear and cannot show it to you again. Copy it straight to wherever your script reads it from.
If you lose it, create a new one and remove the old. That is normal and costs nothing.
Treat it like a password
Section titled “Treat it like a password”- Not in an email, not in a chat, not in a shared document
- Not checked into a repository
- Not handed to someone who needs it “just quickly” — create a second key you can remove on its own instead
Whoever holds the key can do what you can do in your area.
Removing
Section titled “Removing”Settings → Access keys → remove. The key stops working on the next request. If you suspect it has ended up somewhere it should not be: remove it and create a new one. That is the right reaction and it costs you nothing but a line of configuration.