Account
Account in the Settings area (Workspace) — route /account-management.
Account lives in the Settings area of the dashboard, under Workspace.
At a glance#
| Dashboard route | /account-management |
| Area | Settings (settings) |
| Group | Workspace |
| Platforms | Available for every app platform. |
| Note | This entry points outside its area's usual /{area}/{slug} pattern. |
What it does#
Account management is the combined screen for the credentials and environments behind one app: SDK keys with their client key visible on request, the environments they belong to, and the per-app ingestion setup.
It shares its route with SDK keys — the sidebar offers two entries into the same screen because people arrive looking for two different things ("where is my key" and "where do I manage this app"). It is one page, so a change made from either entry is the same change.
When to use it#
During integration, and whenever you need a key. The environment defaulting matters here: the page picks a sensible environment for you, which is convenient and is also the reason to check which one is selected before copying anything.
Workflow#
Check the environment before copying a key
The key you copy belongs to the selected environment. A staging key in a production build reports successfully into the wrong place, and nothing about that looks broken.
Reveal the key only when you need it
Keys are hidden by default. That is not security theatre — it is so a screen-share or a screenshot does not publish one.
Create separate keys per environment
One key per app per environment. Reusing one removes the separation the environments exist for.
Confirm data arrives
Devices populates first. Check there before adding any further instrumentation.
Permissions and prerequisites#
Requires a role that can see SDK keys — developer or above. Key lifecycle events are recorded in the audit log.
Limits and edge cases#
Revocation breaks released builds immediately and cannot be undone. Roll a new key out first.
The default environment is a convenience, not a decision. It is chosen for you; confirm it.
Same screen as the SDK keys entry. Two sidebar paths, one page.
Troubleshooting#
No data after integrating. Confirm the key matches both the app and the environment you are watching.
Data stopped after rotating a key. A released build still has the old one. Rotation does not update apps already in users' hands.
Where the data comes from#
The same screen as the SDK keys entry. The environment is defaulted for you, so confirm which one is selected before copying a key.
From the SDK
Served by
SDK keys
Environments