Organizations

An organization owns your instances, your members, your tokens and your billing. You create it the first time you sign in to the dashboard.

Members

Invite people from Settings, Members, by email. Each member has one role. Members cost nothing: add as many as you like.

Roles

A role is a set of permissions, and everyone in a role can do what it allows. Every organization starts with an Admin role and a Member role. You can add roles of your own under Settings, Roles, and change what any role allows.

Three of the permissions cover the data in your instances: Read data, Write data and Manage tables (create and drop them). They match the data:read, data:write and data:manage scopes of an instance’s access tokens. Admin holds all three and Member holds Read data and Write data, so a Member makes read and write tokens and only an Admin makes one that creates and drops tables.

API tokens

An API token lets a script or a CI job manage your organization as you: make instances, stop and start them, and so on. Make one under Settings, Tokens, and tick only what it needs. It can never do more than you can, and it is shown once.

To read and write table data, a client uses one of the instance’s own access tokens instead.

Closing an organization

Closing is three steps: delete every instance, cancel the subscription, then delete the organization. Billing has the details.