Slug

A slug is the unique identifier for a workspace, for example, devrev in app.devrev.ai/devrev. It appears in URLs and is used across integrations, so changes are controlled carefully to prevent abuse and URL squatting.

📝 Note: Only workspace admins can update the slug.

Update your workspace slug

Go to Settings > General, locate the Org URL field, enter the new slug, and save your changes.

📝 Note: Certain slugs are reserved and cannot be used. Reserved words include common system terms such as login, signup, computer, agent, and onboarding-companion. If you attempt to use a reserved slug, the update is rejected with an error.

Policies

Cooldown period

A workspace can only update its slug once within the cooldown period. Attempting to update sooner results in an error that includes the exact remaining wait time.

The cooldown period time is 1 hour.

Old slug reservation

After a slug is changed, the previously used slug is reserved and cannot be claimed by any other workspace until the reservation window expires.

The old slug is reserved for 7 days.

During the reservation window, visitors who navigate to the old slug URL are automatically redirected to the new slug URL.

What happens after a slug change

The cooldown period and the old slug reservation serve different purposes and have different durations.

The 7-day reservation window protects against external workspaces claiming a recently vacated slug. The shorter 1-hour cooldown allows the original workspace to perform another slug update relatively quickly if needed.

Release a previously held slug early

If your workspace needs to free up a slug it previously held, update your slug to a temporary value after the 1-hour cooldown. This overwrites the stored old slug reference and releases the reservation, making the target slug available for any workspace to claim.

📝 Note: You may experience inconsistencies, such as being redirected to the old DevOrg, for up to an hour after reusing an older slug.

Downstream impact of a slug change

Changing your workspace slug affects several areas.

• URLs break after the reservation window: All existing URLs that contain the old slug stop working once the reservation period expires. During the reservation window, visitors are redirected, but after it expires the old URLs no longer resolve.

• Bookmarks and shared links: Any bookmarked or shared links that reference the old slug must be updated manually.

• Integrations and webhooks: Integrations or webhooks that reference your workspace by slug may stop functioning. Review and update any configured callback URLs or workspace references.

• SSO configurations: If your SSO provider references the workspace slug, update the SSO configuration to reflect the new slug.

Troubleshooting

• Issue: Dev Slug updated recently. Please try after X minutes.

  Solution: Wait until the cooldown period has elapsed. The error message includes the exact number of minutes remaining before you can retry.

• Issue: Input DevSlug for creating DevOrg is reserved.

  Solution: The old slug cannot be reclaimed until the 7-day reservation window expires. If your own workspace previously held this slug, update your slug to a temporary value after the 1-hour cooldown to release the reservation early, then update again to the desired slug.

• Issue: Input DevSlug for creating DevOrg already exists.

  Solution: Another workspace is already using this slug. Choose a different slug.