Settings
Everything under the console’s Settings page, one section per tab: the workspace itself, its API keys, the organization and its members, and the shared views that leave it.
A Rius workspace is where your traces live. Every trace your SDK or collector sends belongs to exactly one workspace, determined by the API key it authenticates with. The workspace switcher sits at the top of the sidebar; everything you see in the console (traces, agents, keys, settings) is scoped to the selected workspace.
Workspace
Settings → Workspace shows the workspace’s name and ID, and lets admins rename or delete it:

API keys
API keys authenticate ingest, requests to
https://ingest.eu.console.rius-glassflow.com (the SDK’s default
endpoint). Each key belongs to one workspace: traces sent with it appear
there and nowhere else. Create keys from Settings → API keys or from
the Get started page:

A key is shown in full exactly once, when it is created; afterwards the console keeps only its name and prefix, and the server stores only a hash. Lose a key and the path is revoke and reissue, there is no recovery. Revoke takes effect immediately: in-flight traffic with a revoked key starts failing authentication right away, so rotate by creating the new key first, moving your agents over, then revoking the old one.
Organization and members
Workspaces, members, and invitations belong to the organization; it spans every workspace you are a member of. Settings → Organization shows the organization’s name, your role, and the member list:

Inviting a teammate creates a one-time invitation link that you share yourself, no email is sent. Links expire after 7 days; accepted and revoked invitations leave the pending list.
Shared views
A shared view is a public link to a frozen window of traces, created with Share from the trace list. Anyone with the link sees metadata and rollups until it expires or you revoke it in Settings → Shared views. Links themselves are shown only at creation, the same rule as API keys:

Next steps
- Installation and configuration: where the API key goes in the SDK.
- Exploring traces: the view a shared link freezes.