SettingsAll sections
Settings
Settings holds the project’s details, its API keys and its access list. It is where you find the project id and API address, create and revoke keys, and see who can open the project.
In the console: SettingsUpdated October 12, 2026
Why you need it
Every app that talks to your backend needs a key, and different callers need different powers: a browser should never hold a key that can administer the project. Settings is the one place keys are created, scoped and revoked, next to the identifiers your code needs and the controls for the project as a whole.
For example
- You copy the project id and API base URL into your frontend’s environment variables.
- You create a Client key for the browser and an Admin key for a server-side job.
- A key leaked, so you revoke it. Anything using it stops working immediately.
- Before sharing data with a teammate, you check who can open the project.
How it works
General
The project’s name and description, its id, the API base URL, the region it runs in, and deleting the project.
API keys
Each key has a role: Admin for server-side code only, Write to read and change data, Read only, or Client for frontend apps. Every key for the project is listed here, including keys created for coding agents.
Access
Who can open the project comes from your organization’s members. The Access tab shows them, and you manage members from the organization’s Members page.
Try it
Once your coding agent is connected, ask it:
List my project’s API keys and when each one was last used.Good to know
- A key is shown once, when you create it. Backenly stores only a hash, so a lost key cannot be recovered: create a new one and revoke the old one.
- Revoking a key takes effect immediately, for every app and script using it.
- Deleting a project is permanent.