Appearance
Scopes
You pick the permissions per key.
| Scope | What it grants |
|---|---|
meetings:read | Read meetings, minutes and participants |
meetings:write | Create meetings, which starts a bot — phase 2, no endpoint yet |
transcripts:read | Read transcripts |
action_items:read | Read tasks, per meeting or across meetings |
action_items:write | Edit tasks — phase 2, no endpoint yet |
The two write scopes exist in the data model but have no route behind them. A key that carries one of them can do nothing with it. Which scope an endpoint needs is on the endpoint's own page, next to its address.
What a personal key can carry
A personal key is limited to the three read scopes. Write access stays with an admin's account key: a personal key should hand out data, not start recordings and run up cost.
That the two lists match today is a consequence of there being only read endpoints. It is not a rule — when write endpoints arrive, they arrive for account keys.