Checking sign-in status
Cocode Docs / Teams and organizations

Teams and organizations

An organization shares membership, permissions, subscription context, and usage views. The individual account remains the owner of identity and personal API keys.

  1. Create an organization and confirm the owner.
  2. Invite members.
  3. Assign roles by responsibility.
  4. Create a separate API key identity for automation or service accounts.
  5. Review usage and audit events regularly.

Organizations support invitation, revocation, member add/remove, role changes, and ownership transfer. High-risk changes may require recent reauthentication. Concurrent writes use version checks; reread and retry after a conflict. Audit events can be viewed and exported.

Personal API keys belong to their creator; they are not plaintext organization-wide shared secrets. Use separate identities, least-privilege scopes, and regular rotation for automation.