Difference between revisions of "Tenant Subdomains"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 10: | Line 10: | ||
:* For [[Marketplace]] ... | :* For [[Marketplace]] ... | ||
:* '''AA:''' Each tenant can have their own [[Service Portal]], with customer case tracking, community forums, and a searchable knowledge base. | :* '''AA:''' Each tenant can have their own ServiceDesk [[Service Portal]], with customer case tracking, community forums, and a searchable knowledge base. | ||
Tenant subdomains should not be enabled: | Tenant subdomains should not be enabled: | ||
Revision as of 20:37, 3 April 2014
About Tenant Subdomains
A subdomain is a tenant-specific prefix that is added to the URL at which the platform is hosted. So if the platform is hosted at yourService.com, and the ABC company is a tenant, then ABC's applications can be accessed at ABC.yourService.com.
(The subdomain chosen by the tenant will typically the name or an abbreviation of their company, product, service, or division.)
Tenant subdomains are recommended for most platform installations:
- They provide a recognizable URL for each tenant's customers.
- They allow duplicate usernames in different subdomains.
(Usernames must be unique within each tenant, but do not have to be unique across the entire platform.) - For LDAP authentication, ...
- For Marketplace ...
- AA: Each tenant can have their own ServiceDesk Service Portal, with customer case tracking, community forums, and a searchable knowledge base.
Tenant subdomains should not be enabled:
- For an enterprise installation that is accessed using an ISP address.
- In an other circumstances where only a single domain is permitted.
Enabling Tenant Subdomains
Tenant subdomains are enabled in the Service Configuration#Tenant Configuration settings.
Once enabled,
- --the __TBD: link to registration dialog__ has a __TBD: field__, with which to specify their desired subdomain