Accounts and sign-in

Your Usable account identifies you across the dashboard, workspaces, organizations, and connected applications. After you sign in, your account gains access through workspace memberships, public subscriptions, organization membership, and any permissions granted to integrations you create.

An account alone does not grant access to every workspace. It establishes your identity; each workspace or organization then applies its own roles and permissions.

Sign up and sign in

Open Usable and choose Sign up or Sign in. Usable redirects browser authentication through its identity provider and then returns you to the application with a signed-in browser session.

For a first-time account:

1. Complete the sign-up or sign-in flow.
2. Accept the terms and privacy policy if Usable prompts you.
3. Open the dashboard.
4. Create a workspace, accept a recognized invitation, or discover a public workspace.

The public lifecycle routes include /signup, /login, and /accept-terms. The dashboard begins at /dashboard.

Browser sessions

The dashboard uses a browser session stored in secure cookies. It handles authentication automatically while you navigate the web interface, so you should not copy session values into scripts or API clients.

If the session expires, an authenticated page or embedded Usable surface may ask you to sign in again. Refresh once, confirm that you are using the intended account, and repeat the sign-in flow if necessary.

Signing out ends the current browser session. On a shared computer, sign out when you finish and close the browser rather than relying only on closing a tab.

Profile and account settings

Open /account to view the account settings available to you. Profile information commonly includes your name, email address, and profile image. Some identity fields may be controlled by the sign-in provider rather than directly editable in Usable.

Your account is distinct from your access roles:

• an account can own one workspace and only view another;
• an organization role does not replace workspace-specific access checks;
• subscribing to a public workspace grants read-style access, not editing rights;
• a personal access token can have fewer permissions than your signed-in account.

When expected content is missing, verify the account shown in the dashboard before asking an owner to change permissions.

Invitations and first access

Workspace and organization invitations appear in the dashboard notification experience and may also arrive by email. Accept only invitations you recognize. If an invitation opens under the wrong account, sign out and authenticate with the invited email address before trying again.

An accepted workspace invitation adds the role selected by the inviter. An accepted organization invitation adds an organization role, which is separate from roles inside individual workspaces.

Read Workspace members and invitations for the complete workspace flow.

Browser sessions and personal access tokens

Browser sessions are intended for interactive use in the dashboard. Personal access tokens are bearer credentials for scripts, REST clients, and legacy integrations that require them. Do not extract a browser token for long-running automation.

For remote MCP clients that support OAuth 2.1, prefer the browser authorization flow provided by Connect MCP. Create a personal access token only when an integration specifically needs one.

See Personal access tokens for scope and safety guidance.

Security practices

• Use only the official Usable sign-in flow.
• Do not share cookies, authorization headers, invitation payloads, or personal access tokens.
• Review an invitation's workspace or organization name before accepting it.
• Sign out of shared devices.
• Revoke integration credentials that are no longer used.
• If access looks unexpected, verify both your account and your effective workspace role.

Usable's released public documentation does not define a universal password-reset or multi-factor-authentication workflow inside the dashboard. Follow the options shown by the configured identity provider rather than relying on undocumented routes.

Troubleshooting

I can sign in but cannot see a workspace

Check dashboard notifications for a pending invitation. If the workspace is public, search Workspaces → Discover and subscribe. Otherwise, ask an owner or collaborator to confirm the invited email and membership state.

I can open a workspace but cannot edit

You may be a Viewer or Subscriber. Read Workspace roles and permissions and ask an owner for a stronger role only when your responsibilities require it.

An invitation action fails

Refresh once, confirm the signed-in account matches the invited address, and ask the inviter to resend a pending invitation if it has expired or was revoked.

Continue

Next, learn how Workspace members and invitations grant people access to a workspace.