Account
Manage your account identity, preferences, and sign-in security
Account settings control how Integrity behaves for you across workspaces. They are personal to your signed-in account; workspace administrators manage workspace membership, Teams, Modules, and security policies separately.
What You Can Manage
| Page | Use it for |
|---|---|
| Account Settings | Profile identity, avatar, passkeys, password reset, and sign-in method context |
| Preferences | Account-wide home routing, calendar week start, theme, and Issue workflow defaults |
| Notifications | Inbox, review digest, Issue activity email, and access-request responder preferences |
| Coding Agents | Name each Codex installation, authorize current workspaces in one environment, and review, rename, or revoke OAuth connections |
| Two-Factor Authentication | Required authenticator setup, recovery codes, and 2FA troubleshooting |
Account-Wide Preferences
Preferences follow your account across workspaces. A workspace may still keep contextual memory, such as the last Team Issues page you opened inside that workspace, but the selected preference remains yours.
For example, if your default home view is Team Issues, Integrity uses that account preference first and then chooses the workspace Team from the current accessible Team context.
Sign-In And First Workspace
New accounts complete profile onboarding first. If you are not already a workspace member and are not accepting an invite, Integrity sends you to Create workspace for your first Free workspace. After you continue past workspace details or teammate invites, refreshing or signing in again resumes the next step. Creating a later workspace is a normal session-only form and starts over after refresh. You may create additional Free workspaces without an account-level limit; each workspace keeps its own plan.
Two-factor authentication is optional by default. Integrity only challenges for an authenticator after your account has a verified factor. If you remove or reset MFA, sign-in continues without forcing setup until you verify a new factor.
Security Boundary
Your account settings do not grant access to hidden Teams, restricted Modules, private Issues, or source-library content. Access still comes from workspace membership, Team membership, direct shares, and the underlying permission model.