Skip to main content

​
Projects

​
What this is for

A project is a self-contained workspace for one application or environment. Its API keys, and the practice records those keys create, belong to that project and are invisible to your other projects. (Webhooks, Logs, Realtime and Usage are opened from inside a project, but they show activity for the whole organization; each of those pages says so.) The Projects page is the home of an organization: one card for each project, so you can find the right one quickly and see at a glance whether it is healthy. A good rule of thumb: make one project per application you are building, or one for development and one for production, so a leaked development key can never touch production.

​
Before you start

  • Any member can see the list.
  • Only organization owners and admins see New project. See Create a project.
  • Only an owner can delete or restore a project.

​
Find and open a project

1

Open the list

Select Projects at the top of the sidebar, or choose All projects from the project switcher in the top bar. The page is titled Projects, followed by “Projects in (your organization).”
2

Search if you have many

Type in Search for a project. It matches part of the name or the project reference.
3

Open it

Select a card. You land on the project’s Overview.

​
What you’ll see

Each card shows: Empty states: with no projects the page reads No projects yet: “Every key, webhook and record belongs to a project.” (with a Create a project button for owners and admins). If your search matches nothing: No projects match your search: “Try a different name or reference.”

​
Status labels

​
Deleted projects

Only an owner can delete a project (from Project settings). Deleting revokes all of its keys at once. Its sandbox data is kept for 7 days. Deleted projects no longer appear in the list or the switcher. If someone opens a deleted project’s address, instead of the page they see “(name) was deleted”. It explains that the keys were revoked, that the data is kept for 7 days, and how many days are left. Owners get a Restore project button (it reads Restoring… briefly, then Project restored). Restoring does not bring the revoked keys back; create new ones on Access. Other roles see Only an owner of the organization can restore it. After 7 days the page says “The 7-day restore window has closed, so this project cannot be restored.” An All projects button leads back to the list.

​
Suspended projects

A suspended project shows a red banner across the top: Billing for this project has stopped. “Every key answers with a payment-required error until the open invoice is paid. Nothing is deleted.” Owners and admins get an Open billing link; other members are told to ask an owner or admin to open billing. Creating new keys is refused while suspended.

​
Common questions

Each organization starts with one project, named Default project. You can use it as it is, or rename it in Project settings.
Several is safer: for example my-app-dev and my-app-prod. Keys never cross between projects, so a mistake in development cannot reach production.
The status does not come from your own settings. The dashboard checks that the practice environment is answering right now and says so honestly when it is not. Wait a minute and refresh.
No. Keys belong to the project they were created in. Create a new key in the other project.
Within 7 days, yes, if you are an owner. See “Deleted projects” above. The revoked keys stay revoked.

​
Troubleshooting