Difference between revisions of "Tenant Subdomains"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==About Tenant Subdomains== | ==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 <tt>yourService.com</tt>, and the ABC company is a tenant, then ABC's applications can be accessed at <tt>ABC.yourService.com</tt>. | 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 <tt>yourService.com</tt>, and the ABC company is a tenant, then ABC's applications can be accessed at <tt>ABC.yourService.com</tt>. (The subdomain chosen by the tenant will typically the name or an abbreviation of their company, product, service, or division.) | ||
(The subdomain chosen by the tenant will typically the name of their company, product, service, or division | |||
Tenant subdomains are recommended for most platform installations: | Tenant subdomains are recommended for most platform installations: | ||
:* They provide a recognizable URL for each tenant's customers. | :* They provide a recognizable URL for each tenant's customers. | ||
:* They allow duplicate usernames in different subdomains. | :* They allow duplicate usernames in different subdomains. | ||
:: That is especially helpful for [[LDAP Configuration|LDAP]] authentication because it means that usernames only need to be unique within each subdomain. They do not have to be unique across the entire platform. | |||
:* | :* Each tenant can have their own ServiceDesk [[Service Portal]], with customer case tracking, community forums, and a searchable knowledge base. | ||
:* It also allows for multiple [[Marketplace]]s in which to list installable packages. | |||
: | |||
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== | ==Enabling Tenant Subdomains== | ||
Tenant subdomains are enabled in the [[Service Configuration#Tenant Configuration]] settings. | Tenant subdomains are enabled in the [[Service Configuration#Tenant Configuration]] settings. | ||
This setting adds a '''Sub-Domain''' field to the registration page a new client sees when creating an account. | |||
:''Learn more: [[Setting up Your Cloud Account]] | |||
Latest revision as of 22:19, 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.
- That is especially helpful for LDAP authentication because it means that usernames only need to be unique within each subdomain. They do not have to be unique across the entire platform.
- Each tenant can have their own ServiceDesk Service Portal, with customer case tracking, community forums, and a searchable knowledge base.
- It also allows for multiple Marketplaces in which to list installable packages.
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.
This setting adds a Sub-Domain field to the registration page a new client sees when creating an account.
- Learn more: Setting up Your Cloud Account