On rare occasions, you may need to update your Slate domain or subdomain.

This happens most often upon initial set-up where you are using a temporary subdomain (for example, slatetemp.uni.edu → apply.uni.edu), or when you begin incorporating additional populations into Slate and need a more generic subdomain (for example, apply.uni.edu → engage.uni.edu).

Several different parties are involved in this change. Coordinate with them all to ensure a seamless changeover:

• Slate Administrators, who must manage projects and update links throughout Slate

• IT Staff/Network Administrators, who must set up DNS entries and update Single Sign-on settings

• Web/Marketing team, who must update various links throughout the institution's websites

• Third-party Payment Providers, who must update URLs for postbacks and checkout

• Technolutions, who must update SSL certificates and other domain settings

📝 Note: Technolutions manages all SSL certificates for Slate instances and all certificates are automatically renewed every 90 days.

🔔 Important: It is not possible to share the subdomain with other websites or functionality on campus. The DNS entry for Slate should use a CNAME record to redirect all traffic to Slate. It should not use an A record.

Changeover Steps

1. Determine a new subdomain name.

2. Have your IT group create a new DNS entry for the new subdomain. It should point to a CNAME determined by your geographic area:

   • UNITED STATES: apply.university.edu IN CNAME cluster.technolutions.net

   • CANADA: apply.university.edu IN CNAME cluster.ca-central-1.technolutions.net

   • EUROPEAN UNION: apply.university.edu IN CNAME cluster.eu-west-1.technolutions.net

   • ASIA PACIFIC: apply.university.edu IN CNAME cluster.ap-northeast-1.technolutions.net

3. Use an external tool such as https://www.digwebinterface.com/ to confirm the DNS entry is in place.

4. Notify the following four groups of the new subdomain and the planned changes:

   • Slate Administrators to update any links used within Slate such as within ongoing Deliver mailings, decision letter templates, portals, and image references.

   • IT/Network Administrators to update the Single Sign-on settings, specifically new hostnames for metadata, login, logout, validate, and other URLs. In addition, you will use the new subdomain for the entity ID.

   • Third-party Payment Providers, if not using Slate Payments, to notify them of new hostnames for postback, checkout, and other URLs.

   • Web/Marketing to update links on your institutional sites to use the new subdomain.

5. Submit a request to the Domain and SSO Configuration category with the following information:

   • The new subdomain

     • The intended launch date for the new subdomain

   • Technolutions respond to confirm the details and begin the changeover process.

6. Once the new domain is up, you can reach out to the groups from step three and let them know to make the appropriate updates. NOTE: The existing subdomain will remain active for about a month after the change to ensure that existing links will not immediately expire and give you and your campus colleagues time to make the above mentioned changes.

Billing and Contract Contact Information

To make updates to your billing contact information, please reach out to [email protected].

To make updates to your contract contact information, please reach out to [email protected].