Concept · Set of pages
Who can run what: organisations, grants and the fifteen-minute token
A subscription is an organisation's. Access is a person's.
Page 1 of 4
By Ilse Vandenberg · Platform controls · 15 July 2026 · 7 min read
Access here is three separate facts, and most confusion about permissions comes from treating them as one.
A subscription belongs to an organisation. Your organisation subscribes to an application, and is provisioned its own instance of it — its own configuration, its own place to keep results, its own tenancy.
A grant belongs to a person. Somebody in your organisation is given access to that instance, at a level: owner, editor or viewer. A person with no grant cannot open the application even though their organisation subscribes to it.
An organisation role — owner, admin, member — is a different vocabulary again, and it decides who can invite people, subscribe to new applications and pay. It is deliberately not the same word list as a grant: the person who signs the invoice is frequently not the person who runs the analysis.
The two-hop call
A call to an application proves it was allowed in two hops, and neither hop is a long-lived key sitting in a config file.
First, the control plane authenticates a person or a client and issues a session. Second, that session asks for a dispatch token for one specific application instance. What comes back is a short-lived credential — fifteen minutes — bound to the organisation, the application and the instance it was issued for, plus the URL of the application to call.
The application then verifies that token locally and scopes everything it does from the identity inside it. It does not mint credentials of its own, and it does not ask the control plane whether you are allowed; the token already says so, and it says so in a way the application can check without a network call.