Skip to main content

Why this happens

Citadel namespaces — both users (your personal `@you`) and organizations (`@your-company`) — share one global pool of slugs. The slug is the identifier that appears in your URLs, your git remote, and on every consent screen and audit-log row. So they have to be unique: one slug, one owner, no overlap.

When you saw E-slug_taken, someone else registered that exact slug — possibly seconds before you tried — or it was already in use by a long-standing namespace.

What to try

  • Pick a variation. If acme is taken, try acme-corp, acmehq, or your domain root (acme-io).
  • Check the slug rules. Slugs are 3–39 characters, letters / digits / hyphens only, must start with a letter, must end with a letter or digit. The signup form will refuse anything that doesn't fit before it ever hits the server.
  • Reserved names are rejected separately. Words like admin, api, help, etc. are blocked even if no one has them. You'll see E-reserved instead, not this code.

If you're trying to claim a slug owned by your team or company

v1 has no self-service org transfer or trademark dispute flow. If a slug you believe should be yours is held by someone else, reach out via the contact form with the slug and a brief explanation; an operator will review.

Renaming after the fact

Renaming a namespace's slug after creation is on the roadmap (with a 30-day URL forwarder so existing git remotes keep working). Until that ships, the slug you pick at registration is permanent — so pick one you'd be happy with for a while.