Reserved subdomains
Names tenants cannot claim and why.
Names tenants cannot claim as their subdomain.
Why some names are reserved
Some words are used by the Shelfwise platform itself:
- admin, api, www — platform infrastructure
- billing, support, help — would conflict with platform features
- dashboard, docs, status — common platform routes
If a tenant claimed these, they'd break or shadow platform features.
Full list of reserved subdomains
- admin
- api
- app, apps
- auth
- billing
- blog
- cdn
- dashboard
- docs
- help
- platform
- shelfwise
- staging
- status
- super-admin
- support
- system
- www
Adding to the list
The list is hardcoded in src/lib/tenant.ts and src/app/super-admin/libraries/actions.ts. To add new reserved names, deploy a code change.
Working around it
If a tenant wants a reserved name (e.g., "help" because their org is named "Help Center"), suggest:
- A variation: help-center, hopehelp, helpinglibrary
- A custom domain instead
Already-claimed subdomains
If a tenant is on a subdomain that becomes reserved later (rare), they're grandfathered in and can keep using it.
Still stuck? Email hello@tryshelfwise.comand we'll get back within one business day.