1. Choose a local chain folder
Optionally provide the local folder that should receive or reopen this account's chain workspace.
Use the Auth Service to establish and manage your accountable identity.
The Auth Service has two surfaces: Login establishes access, while Identity shows the credentials, sessions, and local chain path connected to the account.
Start by choosing how this account will authenticate.
Open Login from Create your Nexus. The Public Portal does not collect credentials; authentication happens in the dedicated Auth Service.
2. Choose an access method
Use the local email-code flow, or a configured identity provider. User + key access is reserved until account keys are modeled.
3. Complete verification
For local testing, request a code, enter the verification code shown by the service, and select Access.
4. Continue to Identity
Successful authentication stores the browser session token and opens the Identity surface.
Review what is connected to the account.
Identity is the credential-management surface reached after authentication or from the User Portal.
1. Confirm the account
Check the authenticated user and current session before continuing into accountable workflows.
2. Review credential status
See which local or provider-backed methods are connected and which remain unavailable.
3. Manage identity sources
Add or remove supported providers only when their integration is configured and available.
4. Maintain the chain path
Review or update the local chain folder used to continue the account's Nexus workspace.
Current MVP limits
Some controls are instructional or reserved until their integrations are complete.
- User + key login remains reserved until account keys are modeled.
- Provider sign-in depends on configured callbacks and complete token validation.
- The local email code is shown for testing; production email delivery is not yet implemented.
- Authentication establishes account access. Roles, capabilities, and workflow authorization are handled separately.
Ready to continue?