User settings
Business Summary: User settings centralize who you are, which organization you are working in, how much AI work costs, and (soon) security controls — one place for context that applies across every workstream and agent.
Workspace settings centralize your profile, organization context, usage and billing, and (planned) security controls — everything that applies across workstreams and agents.
Some navigation labels say Workspace settings; the page title is Settings in Settings.
How this fits in Nimbus
Settings sit above individual workstreams. Profile confirms your identity. Workspace shows org context. Usage & Billing tracks NTU consumption. Security (planned) will govern SSO and programmatic access.
flowchart TB
User[Signed-in user]
Settings[Settings]
Profile[Profile tab]
Workspace[Workspace tab]
Usage[Usage and Billing tab]
Security[Security tab - planned]
User --> Settings
Settings --> Profile
Settings --> Workspace
Settings --> Usage
Settings --> Security
Workstreams[Workstreams and agents]
Settings --> Workstreams
Day-to-day agent work happens inside workstreams; settings define the org-wide context that workstreams inherit.
What you'll learn here
You will learn what each settings tab contains, how profile and workspace details relate to org membership, where Usage & Billing lives, and how to find settings from elsewhere in the app.
Start here {#start-here}
| Goal | Guide |
|---|---|
| Confirm signed-in account | Profile and identity |
| Create a separate workspace | Creating a workspace |
| Open Usage & Billing | Finding settings |
| Invite teammates | Inviting teammates — invite management lives under Governance because access and roles are governed there |
| Review NTU consumption | Billing and usage |
Articles in this section
| Article | Description |
|---|---|
| Creating a workspace | Add a blank-canvas environment inside your org |
| Workspace settings overview | Tabs and what each controls |
| Profile and identity | Name, email, signed-in user |
| Workspace details | Organization name and workspace ID |
| Security settings | SSO, API keys, sessions (roadmap) |
| Finding settings | Sidebar, user menu, deep links |
Settings tabs
| Tab | Label | Status |
|---|---|---|
| Profile | Profile | live |
| Workspace | Workspace | live |
| Usage | Usage & Billing | partial (sample billing data in demo) |
| Security | Security | planned |
Default tab when opening Settings without a specific tab selected: Profile.
Example scenario
Before approving a Critical checkpoint on a shared machine, an analyst opens Settings → Profile to confirm she is signed in as herself — not a colleague who forgot to log out. She then clicks the header NTU meter to check remaining included usage before confirming a large Plan run. Settings gave identity and spend context in two clicks without leaving the approval flow.
Related sections
- NTUs and billing — deep dive on metering and invoices
- Team and commit management — roles, invites, plans
- Governance — policies separate from settings tabs
FAQs {#faqs}
Q: Are settings per user or per organization? A: Profile is per user. Workspace, Usage & Billing, and Security apply to the active organization context.
Q: Why is billing under settings? A: Usage & Billing is org-scoped consumption and payment — admins manage it alongside workspace identity.
Q: Can Viewers open settings? A: Viewers may have limited access; billing and invite actions require Admin.
Q: Where is team management? A: Dedicated team UI in settings is planned. See Workstream teams and access and Inviting teammates.
Q: How do I jump straight to billing? A: Use Settings → Usage & Billing or click the header NTU meter. See Finding settings.
Q: Do settings control agent approvals? A: No. HITL checkpoints and governance policies live on workstreams and the Governance page. Settings cover identity, org context, billing, and future security policy.
When admins vs members use Settings
| Task | Tab | Typical role |
|---|---|---|
| Confirm signed-in account before approval | Profile | Any member |
| Copy tenant ID for support | Workspace | Admin or operator |
| Review NTU consumption vs plan | Usage & Billing | Admin, finance delegate |
| Plan SSO rollout | Security (roadmap) | Admin |
Members use Profile daily; admins spend more time on Usage & Billing during pilot and production rollouts. Governance policies — HITL presets, connector export rules — remain on the Governance page, not under Settings tabs.
Settings vs other admin surfaces
| Concern | Where to configure |
|---|---|
| Who approves Critical writes | Workstream HITL + Governance |
| OAuth connectors | Connectors sidebar |
| NTU plan and invoices | Settings → Usage & Billing |
| Org invites and tiers | Inviting teammates, workspace admin flows |
| SSO and API keys (planned) | Settings → Security roadmap — see Security settings |
During pilot rollouts, assign one workspace admin to own Usage & Billing reviews each Monday and one security lead to track the Security roadmap. Operators should bookmark Finding settings so they can jump to billing from the header NTU meter without hunting through Profile tabs first.
If your organization uses shared machines in a war room or board prep suite, post a reminder to check Profile before any Critical approval — the two-click habit prevents Activity from attributing sign-offs to the wrong teammate and keeps audit trails trustworthy for compliance review. Finance delegates often pair Profile checks with the header NTU meter before approving large Plan runs.