Skip to main content

Organization settings

What this is for

Organization settings control things that apply to your whole organization rather than to one project: its name, its web address inside the dashboard, its overall request usage, and the rare “delete everything” request. If a setting is about one project’s keys or data, it lives under that project instead (see Project settings).

Before you start

  • Every member can open and read these sections.
  • Only the organization owner can change the name or URL name.
  • This page covers General, Usage, Legal and Danger zone. Members and Sub-organizations have their own pages (Members, Sub-organizations). Billing has its own page too: Billing.

Open organization settings

1

Open the page

Select Organization settings at the bottom of the sidebar, or open the organization switcher (your organization’s name in the top bar) and choose Organization settings.
2

Pick a section

The page is titled Organization settings with your organization’s name beneath. A menu on the left (above the content on a phone) lists General, Members, Billing, Usage, Legal, Sub-organizations and Danger zone. Sub-organizations only appears if your organization still has some; they have been replaced by projects.

General: rename your organization

1

Open General

Select General in the left menu. The card is headed General.
2

Change the name

Edit Organization name (up to 80 characters). This is the label shown in the switcher and on pages.
3

Change the URL name (optional)

URL name is the short code that appears in the address of every page for this organization, for example acme-health. It is 3 to 48 characters; capital letters become lowercase and anything other than letters, numbers and hyphens becomes a hyphen. Changing it changes the web address of every page, so bookmarks to the old one stop working.
4

Save

Select Save changes (it reads Saving… briefly). A message says Saved. If you changed the URL name, the dashboard moves you to the new address automatically.
Organization ID is read-only. Select the copy button beside it to copy it, for example to quote it to support.

Usage

This section shows your organization’s request usage for the month: how many requests you have made against your plan’s allowance, the split between live and test requests, how many keys are active, and charts for the last 24 hours or 7 days. It is the same view you see in the project’s Usage page, summed across the organization. This section currently reads Coming soon: accept your BAA, Terms and DPA here. Nothing can be accepted or signed from it yet. The legal documents themselves are published in the Legal section of this documentation.

Danger zone

The section has two cards:
  • Delete organization. Deleting removes the organization’s keys, webhooks and settings and cannot be undone. The dashboard does not delete it for you. Select Contact support to delete to open an email to our team, who do it with you so that nothing is lost by accident.
  • Sign out. Select Sign out of this device to end your session on the device you are using. Other devices stay signed in.

What you’ll see

  • For a non-owner, the Organization name and URL name boxes are greyed out and a line reads Only the organization owner can change these settings. instead of a save button.
  • Unlike the data pages, nothing here needs loading or has an empty state: every organization has a name.

Common questions

It is only the piece of the address that identifies your organization inside the dashboard. It does not affect your API keys or your API requests, so renaming it does not break any integration.
The person who created the organization. The owner has every permission, including renaming it. The Members page shows each person’s role.
The Legal section is a placeholder until acceptance is built. The published documents are in the Legal pages of this site.
Not from the dashboard. Deletion is irreversible, so it is done with our team through Contact support to delete.
No. Sign out of this device only ends the session in this browser.

Troubleshooting