Organization settings
Create an organization, keep its profile and billing details current, manage members and roles, transfer ownership, and close it.
An organization owns everything else in the console: projects, API keys, credits, invoices and members. You can belong to several organizations and switch between them at any time.
Organization settings are under Settings in the sidebar. The page has seven tabs: Profile, Billing details, Members, SSO, Data policy, Security and Danger zone. This page covers the profile, billing, members and danger zone tabs. The others have their own pages: single sign-on, data policy and security.
Create an organization
Your first organization is made for you. The first time you sign in, the console names it after you (for example "Asha's workspace"), gives it a default project and opens the dashboard. A verification check may appear for a moment, or ask for one click. You can rename it later under Profile. If something goes wrong, Set it up myself opens the form below.
The billing country is not asked then. It sets your currency and the tax on your invoices, so the console asks for it the first time you add credit, register a mandate or change plan (Where are you billed? on the Credits page). You can change it until your first invoice.
To add another organization, choose + Create organisation in the organization switcher. The form there:
- Enter a Name. The Slug is filled in from the name, and you can change it before you create the organization. It takes lowercase letters, digits and dashes, and it becomes part of your console URL.
- Choose the Billing country. It sets your currency and payment rail, shown under the field. India is billed in INR, and the other countries listed are billed in USD.
- Choose the Kind: Personal, Team or Enterprise.
- If the billing country is India, you can enter a GSTIN (optional). A valid GSTIN is printed on your invoices. Leave it empty to continue as unregistered.
- If an Invite code field is shown, enter the code you were sent. Where sign-ups need an invite, the first organization is made with this form too.
- If a verification check is shown, complete it.
- Press Create organisation.
The billing country and currency lock after the first invoice, so choose them with care.
The next steps show the default project your organization starts with, create your first key (the secret is shown once), and offer a test request with Send test request. The last step takes you to Top up now, or you can press Skip for now. See API keys and credits.
Invites and the waitlist
When sign-ups are by invitation, your first organization needs an invite code. If you have none, use No invite? Join the waitlist below the form: say what you will build, add your company if you like, and press Join the waitlist. While your entry is pending you can change it with Update my entry. Once it is approved, the page says so and you can create your organization with no code. If the request is declined, an invite code still works.
Once you belong to an organization, you can create more without a code.
If you sign up on a reseller's own domain, the reseller decides who can join. Its page may ask for an invite code that the reseller sent you, or say that it is not taking new sign-ups. See getting access.
Switch between organizations
The Organisation selector at the left of the top bar lists every organization you belong to. Choose one to switch. The project selector and the live and test switch beside it then apply to that organization.
To add another organization, choose + Create organisation in the same selector.
Profile
The Profile tab shows the organization's Name and Slug, with its plan, kind and status below.
- You can change the name and press Save. This needs the owner or admin role.
- The slug is permanent.
Organization spend cap
Below the profile, Organisation spend cap sets a ceiling across every project and key in the organization. Enter a daily amount, a monthly amount, or both, in US dollars, and press Update spend cap. Leave a field empty for no cap.
With Hard budget ticked, requests are refused once the cap is reached, until the day or month rolls over or you raise the cap. Unticked, requests continue and a budget.threshold webhook is sent. This cap is separate from each project's and each key's own budget; whichever is reached first applies. Changing it needs the owner or admin role, and a change takes up to a minute to apply.
Billing details
The Billing details tab holds what is printed on your invoices. Changing it needs the owner or admin role.
- Legal name: printed on invoices.
- GSTIN (India only): leave it empty if you are unregistered. A valid GSTIN shows its state and place of supply under the field, and sets the tax status to
gst_registered. - Tax status:
unregistered,gst_registered,exportorsez. It is fixed while a valid GSTIN is entered. - PAN (India only): printed on invoices for unregistered recipients.
- Billing email: invoices and pre-debit notices go here.
- Billing time zone: where your billing months start and end. A credit-line invoice, a contract's monthly discount and the usage statement's months run from midnight to midnight in this zone (UTC unless you choose one). It can be changed until the first month is closed; after that, ask support. Tax invoices for payments are dated in India's time, as the GST return is.
- Billing address: two address lines, city, state, postal code and country. For India the state is the GST state code.
Press Save billing details. The button stays disabled while the GSTIN or PAN is malformed. Saved details apply to the next invoice. Invoices already issued never change. To correct one, see invoices.
The billing country and currency are shown at the top of the tab and cannot be edited here. An organization with no billing country yet chooses one on the Credits page.
Members
The Members tab lists everyone in the organization with their role. Changing anything here needs the owner or admin role.
Roles
| Role | What it can do |
|---|---|
| owner | Everything, including transferring ownership, requesting erasure and closing the organization. |
| admin | Everything an owner can, except those three owner-only actions. |
| billing | Read the organization and its usage, and manage credits. |
| member | Create and manage projects, API keys, apps and evals. Read usage, credits, routing policies, webhooks and provider keys. |
| auditor | Read only, plus the activity log. For a compliance or finance reviewer who needs to see who changed what. |
| viewer | Read only. |
Invite someone
- Enter the person's address under Invite by email.
- Choose a Role. Only an owner can invite another owner.
- Press Invite.
An invite works for a person who has signed in to the console at least once. Ask a new colleague to sign in first, then invite them.
Your plan includes a number of seats: pay as you go 5, Team S 10, Team L 50. The line under the form says how many are used. When every seat is taken, Invite is disabled; remove a member or change plan to free one. Changing an existing member's role does not take a seat. The same limit applies to members added by single sign-on and by your directory (SCIM): a person your identity provider signs in past the limit is signed in but not added, and the SSO tab's last test says so. A contract can set a different number.
Change a role
Use the role selector on the member's row. The change is saved as soon as you choose. Only an owner can make someone an owner, and the last owner cannot be demoted.
Set a member's budget
Each person can have a spend cap of their own, counted across every API key they created in the organization. The Spend this month column shows what their keys have spent against it. Press Budget on the member's row, enter a daily amount, a monthly amount or both in US dollars, choose hard or soft, and press Save budget. Remove budget takes the cap away. Owners and admins can do this, and a change reaches the API within a minute.
A hard budget refuses that person's keys once it is reached, with the dimension member_budget_daily or member_budget_monthly; a soft one serves them and sends a budget.threshold webhook that names the member.
Remove a member
Press Remove on the member's row, type the member's email address to confirm, and press Remove member. The last owner cannot be removed.
If your organization uses a directory, members can also be added and removed for you. See single sign-on and SCIM.
Teams
A team is a named group inside the organization that owns projects and has its own budget. Use teams when several groups share one organization and each should have its own ceiling.
- Create a team: on the Teams tab, type a name under New team and press Create team. Owners and admins can do this; an organization can have 200 teams.
- Give it projects and a budget: press Edit on the team's row. Tick the projects it owns, set a daily or monthly budget in dollars, and choose whether the budget is hard (requests are refused once it is reached) or soft (requests are served with a warning). Press Save team. A project belongs to one team, so ticking one takes it from the team it was on.
- Members: tick the people on the team. This is for your own records; it does not change what anyone can do.
- Delete a team: press Delete, type the team's name, and confirm. Its projects stay and belong to no team.
The table shows what each team has spent this month against its monthly budget. A team's spending is counted across every key of every project it owns, starting from when the project joined the team.
A request is refused by whichever ceiling is reached first: the key's, the project's, the team's, the person's who created the key, or the organization's. The refusal names which one, for example team_budget_monthly. A change to a team reaches the API within a minute.
To see spend by team, or by the member who created each key, choose team or member as the group-by on the Usage screen. Those breakdowns use today's assignments: a project moved to another team takes its history with it.
Activity
The Activity tab lists every change made in the organization, newest first: who made it, what was changed, the request id, and the address it came from. A change made with an API key is listed under the key's name.
- Owners, admins and auditors can read it. Other roles see a note saying so.
- Only changes that succeeded are kept. Reading a screen is not recorded, and neither is a change that was refused.
- What shows whether something was added, changed or removed, and the API path it was done on. The path contains the id of the thing changed, so you can find every change to one key or one webhook: type the id, or a word such as
webhooks, into the box and press Find. - Older changes at the foot of the table loads the next page.
- CSV and JSON lines above the table download the whole log (or what the box has found) as one file, for an auditor or a security tool. One file holds at most 200,000 changes; narrow it from the API with
sinceanduntilwhen it would be larger.
The log starts on 8 October 2026; changes made before then are not in it. It records what was changed, not the values before and after. It is also available from the API as GET /v1/activity (format=csv or format=jsonl for the file), to a signed-in session only.
Transfer ownership
Only the owner can do this, on the Danger zone tab.
- Under Transfer ownership, choose the New owner. The person must already be a member.
- Press Transfer.
- Type
transferto confirm, and press Transfer ownership.
The person you chose becomes the owner and you become an admin.
Erase the organization's data
Only the owner can request this, under Data erasure on the Danger zone tab.
Press Request erasure. A 30-day wait starts, and the tab shows the date and the days left. During the wait you can press Cancel erasure. When the wait ends, archived payloads and request logs become unreadable and personal data is removed. You receive a completion receipt through the erasure.completed webhook; see webhooks.
The ledger and invoices are kept, as tax law requires.
To erase the data of one of your own end users instead, see privacy requests.
Close the organization
Only the owner can do this, under Close organisation on the Danger zone tab. Closing revokes every API key immediately.
Closing is blocked while credits remain, unless you ask for the unused balance to be refunded.
- If you have credits left, tick Refund remaining credits to the original payment method. A refund ticket is filed for the finance team.
- Press Close organisation….
- Type the organization's slug to confirm, and press Close organisation.
Once closed, the tab shows when the organization was closed.