Getting started
Getting started in the Settings area (Account) — route /settings/getting-started.
Getting started lives in the Settings area of the dashboard, under Account.
At a glance#
| Dashboard route | /settings/getting-started |
| Area | Settings (settings) |
| Group | Account |
| Platforms | Available for every app platform. |
What it does#
Getting started is an onboarding checklist that reads your workspace's actual state: each step shows as complete or outstanding based on whether the thing has really been done, and links to where to do it.
It is not a static tutorial. A step marked complete is complete because the platform observed it.
When to use it#
On day one, and then whenever you want to know what you have not set up. It is also the right page to send a new team member to — it reflects the current state of the workspace rather than describing a fresh one.
Workflow#
Work top to bottom
The order is dependency order. Later steps are not meaningful before earlier ones — there is no point configuring alerts before data arrives.
Verify rather than assume
A step reads complete when the platform saw it happen, which occasionally differs from what you believed you had configured. Where they disagree, the checklist is right.
Finish the whole list
The steps most often left undone are alerts and symbolication, and those are exactly the two whose absence you only discover during an incident.
Permissions and prerequisites#
Reflects the workspace, so what you can act on depends on your role. Several steps require an administrative role to complete.
Limits and edge cases#
Completion is inferred from observed state. A step needing data to arrive stays outstanding until it does, even if your code is correct.
Workspace-scoped, not per app. Completing a step for one app can mark it done, so check the apps you care about individually.
Finishing the list is a good baseline, not a full configuration. It covers the essentials — it does not cover redaction rules, retention periods, or sampling decisions, all of which deserve their own thought.
Troubleshooting#
A step I completed still shows outstanding. It waits on observed evidence. For SDK steps, that means data arriving in the environment you are looking at.
Everything complete but the dashboard is empty. Check the app and environment selector before anything else.
Where the data comes from#
Each step is marked complete from observed state rather than from a stored flag, which is why an SDK step stays outstanding until data actually arrives.
Served by
Organizations