Changing a Spokes name and URL
Changing a spokes name and URL
Using the Enterprise Administration Panel (EAP), Enterprise administrators can toggle the name and URL of an existing workplace in the Networked Enterprise.
Note: If changing the URL, you must update the DNS record or the spoke will not function. If your organization uses an Igloo owned domain (ex. .igloodigitalworkplace.com), you must contact the Igloo Support Team to have the DNS record updated for the spoke. If your organization uses its own custom domain, you must contact your internal IT Team to have the DNS record updated for the spoke.
How to change a spokes name and URL
- While signed into a digital workplace that is part of the Networked Enterprise, click the Control Panel button to open the Control Panel.
- Select EAP from under the Resources section of the Control Panel to navigate to the EAP.
- On the Communities tab, click the digital workplace that you want to edit. This will open the workplace's configuration options.
- Select the Overview tab to view what options are available.
- Enter the new name of the spoke in the Title field.
- Enter the new domain in the Domain field. Typically, organizations have a single domain name and only the subdomain changes. For example, https://www.{spoke subdomain}.{domain}. This URL should be in a valid format, unique, owned by your organization, and be covered by an SSL certificate.
- Click the Save button to apply these changes.
- If you have updated the URL, update the DNS record for the spoke.
- If your organization uses an Igloo owned domain (ex. .igloodigitalworkplace.com), you must contact the Igloo Support Team to have the DNS record updated for the spoke.
- If your organization uses its own custom domain, you must contact your internal IT Team to have the DNS record updated for the spoke.
- 336 views
- 3 previews
- 7 versions
- 0 comments
- 1 follower
Labels:
- Updated By:
- Jesse Langstaff
- January 15, 2020
- Posted By:
- Jesse Langstaff
- September 27, 2019
- Versions:
- v.7
Viewed 336 times
0 Comments