Organizations and Projects
Accounts have three levels:
- An organization is your company or team. It has members and one prepaid balance.
- A project is one app or environment inside an organization, like "Production" or "Staging".
- An API key belongs to one project. Requests made with it are charged to the organization.
An organization can have any number of projects, and a project can have any number of keys. All the projects in an organization spend from the same balance and share one rate limit.
Tuna uses WorkOS to manage sign-in, organizations, and API keys.
Team Sign-In
Invite teammates to your organization so each person can sign in with their own account and access the organization's shared projects and balance. Teams can use these features without an enterprise plan or a company single sign-on (SSO) setup.
Roles
Organization members have one of four roles: Owner, Admin, Member, or View-only.
- Each organization has exactly one Owner. The person who creates the organization becomes its Owner, and the Owner is responsible for the organization's billing.
- An organization can have any number of members with the Admin, Member, or View-only role.
| Permission | Owner | Admin | Member | View-only |
|---|---|---|---|---|
| View dashboard | Allowed | Allowed | Allowed | Allowed |
| Use web chat | Allowed | Allowed | Allowed | Not allowed |
| View truncated API key | Allowed | Allowed | Allowed | Allowed |
| Create & delete API keys | Allowed | Allowed | Allowed | Not allowed |
| View billing page | Allowed | Allowed | Allowed | Allowed |
| Manage payment methods | Allowed | Allowed | Not allowed | Not allowed |
| Buy credits & top-up | Allowed | Allowed | Not allowed | Not allowed |
| Edit spend limits | Allowed | Allowed | Not allowed | Not allowed |
| Add/remove members | Allowed | Allowed | Not allowed | Not allowed |
| Add/remove admins | Allowed | Allowed | Not allowed | Not allowed |
| Remove the owner | Not allowed | Not allowed | Not allowed | Not allowed |
Using Projects
Projects keep keys for different apps apart. A common setup is one project per app, or one per environment. If you need to replace a key, only the app that uses it has to change.
Single Sign-On
Single sign-on (SSO) lets members sign in through their company's account system, called an identity provider. Enterprise customers can connect that system to Tuna using SAML, a standard for sending signed confirmations that a member has signed in. This is optional for teams. See Enterprise for an explanation and setup information.