Slug rules and reserved names
Slugs are the URL-safe names for your organisation and your entities. They appear in every in-product URL, so they are worth choosing deliberately.
The rules#
acme-group valid
berlin-gmbh valid
unit-7 valid
Acme-Group rejected, uppercase
-acme rejected, leading hyphen
ac rejected, shorter than 3 characters
docs rejected, reservedThe setup wizard derives a slug from the name you type, lowercasing it and collapsing anything that is not a letter or digit into single hyphens. Once you edit the slug field yourself it stops following the name.
Uniqueness#
An entity slug collision inside one organisation returns ENTITY_SLUG_TAKEN with HTTP 409.
Reserved names#
Some names are refused because they would collide with an application route, and others because they could be used to impersonate Governax itself. The current list:
accept-invite account admin api
app assets acme auth
billing blog clouvylabs console
dashboard decisions docs entities
entity false forgot-password governax
help invite login logout
mail me members null
oauth-test onboarding org organization
organizations orgs register reset-password
settings signin signup static
status support team teams
true undefined user users
verify-email www you _nextChanging a slug#
There is no interface for renaming an organisation or entity slug. Every in-product URL is built from the slug, and existing links, bookmarks and saved queries would break. If you need a change, contact support.
Slugs are cosmetic in one important respect: nothing in the ledger references them. Governance events are keyed to internal identifiers, so a slug change would not disturb any recorded history. See Anatomy of a governance event.