Tenant and Customer URL Model
Motornauts separates route surfaces by audience and access model.
| Surface | Typical route shape | Access |
|---|---|---|
| Public site | / | Public, no private operational records. |
| Tenant landing | /t/{tenantSlug} | Public tenant information and safe entry points. |
| Tenant staff workspace | /t/{tenantSlug}/admin/... | Staff authentication, tenant membership, and permissions. |
| Customer portal | /t/{tenantSlug}/portal/... | Customer portal session plus customer ownership checks. |
| Capability routes | /t/{tenantSlug}/payment-requests/{id} and /t/{tenantSlug}/feedback/{id} | The path contains a non-secret record ID. The original link supplies its private capability in a URL fragment; Motornauts removes the fragment before calling the API with an authorization header. |
| Fleet workspace | /t/{tenantSlug}/fleet/... | Fleet actor access, fleet account scope, and vehicle assignment rules. |
Custom domains can route customer-facing tenant traffic after domain ownership is verified. Invalid or inactive domains should fail safely without exposing another tenant’s data.
Last updated on