Profile and identity
Business Summary: The Profile tab confirms who is signed in — name and email from live authentication — so you never approve a Critical checkpoint or export a report under the wrong account.
You will learn what appears on the Profile settings tab, how it relates to your Nimbus sign-in, and what you cannot change from this screen today.
The Profile tab shows who is signed in — your display name and email — using live authentication data.
How this fits in Nimbus
Your user identity is separate from organization membership. Profile shows the person; Workspace shows the org; roles and approvals link the two during governed work.
flowchart LR
User[Your user identity]
Profile[Profile tab]
Membership[Org membership]
Approvals[Approvals and Activity]
User --> Profile
User --> Membership
Membership --> Approvals
When Activity records an approver, it uses your membership identity — Profile helps you confirm that identity matches who is at the keyboard.
Confirm identity before approval
- Before signing off on a Critical checkpoint, open Settings → Profile.
- Read Name and Email — confirm they match the person at the keyboard.
- If wrong, sign out from the user menu and sign in with your own account.
- Return to the workstream HITL review rail and complete approval.
- Optional: ask a teammate to verify Profile on shared machines at the start of each shift.
Opening Profile
- Go to Settings
- Select the Profile tab (default if no specific tab is selected)
- Or open Settings → Profile directly
What appears
| Field | Source |
|---|---|
| Name | Display name from your authentication profile |
| Primary email on your account |
The card subtitle reads Signed-in user (live data) — distinguishing Profile from sample billing sections.
What Profile is for
Use Profile to confirm you are not signed into the wrong account before approving Critical checkpoints, share your email with an admin when requesting workstream team access, and verify identity after accepting an invite.
Profile does not show organization role, team memberships, or NTU usage — those live under Workspace, team admin flows, and Usage & Billing.
Changing name or email
Self-serve profile editing in this tab is limited today — fields are read-only display. Name and email changes may flow through your identity provider (Google, Microsoft) or admin provisioning depending on deployment. SSO-managed attributes will sync when Security settings mature. See Security settings.
Relation to org membership
Your user identity links to organization membership records (admin, member, etc.) separately from Profile display. Admins assign roles during invites.
Example scenario
Two analysts share a conference-room machine. Before signing off on a Critical external write, the second analyst opens Settings → Profile, sees the first analyst's email still active, signs out, and signs in with her own account. Profile prevented an approval attributed to the wrong person.
What you'll see
Settings → Profile opens a card titled Profile with subtitle Signed-in user (live data). Fields:
| UI label | Typical value |
|---|---|
| Name | Display name from Google, Microsoft, or email sign-in |
| Primary account email (read-only today) |
Missing values show an em dash (—). Avatar upload is planned; the user menu may show initials elsewhere.
FAQs {#faqs}
Q: Why is my name blank? A: Your identity provider may not supply a display name yet. Email should still appear if sign-in succeeded.
Q: Can I upload an avatar here? A: Avatar in Profile is planned. User menu may show initials elsewhere.
Q: Does Profile show my job title? A: Not today. Extended profile fields are roadmap.
Q: Is my email visible to other workspace members? A: Teammates may see your name on approvals and Activity; email visibility follows org policy.
Q: Multiple organizations — which profile? A: Profile is your user record globally; org context switches under Workspace when multi-org is supported.
Q: Does Profile affect NTU billing? A: No. Billing is org-scoped under Usage & Billing. Profile is personal identity only.