Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.copass.com/llms.txt

Use this file to discover all available pages before exploring further.

Your Copass ID is a public handle — @alice-style — that identifies you across Copass. It’s how other users invite you into their sandboxes and how you invite others into yours. It’s separate from your email, separate from your user_id (which is internal), and separate from your olk_… API keys. The handle is the human-readable name people see in collaboration UIs.

​
What it’s for

  • Collaboration grants — “Invite @alice as editor” — uses your handle as the addressable identity.
  • Agent shares — public-facing invoke / delegate keys reference handles in their audit trail.
  • Public surfaces — anything Copass shows another user about you (a connection list, a shared agent’s owner) renders the handle.

​
Handle rules

A handle is @<name> where <name> is:
  • Lowercase, 3–30 characters
  • [a-z0-9._-] — alphanumeric plus dot, underscore, dash
  • Starts and ends with alphanumeric (no leading or trailing punctuation)
  • No two consecutive special characters (a..b and a__b are invalid)
  • Globally unique across all Copass accounts
Once claimed, a handle is yours. You can have one at a time.

​
Claiming a handle

The fastest path is the web UI on first sign-in — Copass prompts for an available handle as part of onboarding. If you skipped that step or want to change it, ask the Concierge:
“Show me my Copass ID.” “Claim the handle alice.”
The Concierge verifies availability, validates the format, and writes the handle to your account.

​
Using someone else’s handle

You don’t need to know anyone’s user_id to invite them. Anywhere a Copass surface accepts an identity:
“Invite @alice as editor on this sandbox.” “Mint an invoke key for the support agent for @bob.”
The system resolves the handle to the underlying user at call time. If the handle doesn’t exist, you get a clear “Unknown copass_id” error — you can’t enumerate the handle space by guessing.

​
Common patterns

Onboarding a teammate

They claim their handle on first sign-in; you invite them by @<handle> from your own account. See Collaboration.

Audit trail

Every grant, key mint, and connection ledger entry records the handle that performed it. Renders as @alice in lists, never as raw user ids.

One handle, many roles

Your handle is fixed; your role on each sandbox you’re invited to is per-sandbox. Same @you can be editor on one sandbox and viewer on another.

Lost access

Lost your handle through an account issue? Support can re-bind it; the handle namespace is preserved across recovery flows.

​
Next steps