A custom address for your organization

By default, your organization gets a random identifier assigned when it's created. It works fine everywhere, but it isn't meant to be typed or remembered. Setting a custom slug replaces it with something short and readable, like "acme".

Once your platform operator has set up the subdomain for your deployment, visiting your custom address while signed in automatically switches your active organization, the same way picking it from the organization switcher does. You can always reach it directly, whether or not signing in takes you there automatically.

From your organization's page in the client dashboard, find the "Organization slug" field (visible to the organization owner and anyone with the settings permission) and enter the identifier you want, then save.

This is the same identifier used for the SSO sign-in flow if your organization has single sign-on configured, so changing it also changes what your employees type at login.

A slug must be 3 to 40 characters, lowercase letters, digits, and hyphens only, and can't start or end with a hyphen. It also has to be unique across the whole platform, and a handful of names reserved for core infrastructure (admin, api, mail, www, and similar) can't be used.