Building powerful brand experiences also include a branded subdomain name. This FAQ builds on the basic information you find here: Set up custom subdomain access
What types of domains are possible?
A custom subdomain like brand.company.com
A custom root domain like brand.com
A Frontify sub-domain like company.frontify.com
Can we set up the domain by ourselves?
No, it needs the involvement of your IT team, and the Frontify Customer Support team.
Which IP ranges can we use to isolate our environment from external access?
We don’t offer such functionality. Frontify's purpose is to be usable from anywhere.
Can we have the domain pointed to a fixed IP address?
Our IP addresses rotate at irregular intervals. The CNAME record is mandatory, and we can't provide fixed IP addresses due to security considerations.
Why is the CNAME destination address not readable?
For security reasons, we use cryptic names that do not display customer-related information.
Why is the CNAME destination address not accessible?
The CNAME is an alias within our hosted zone, which we use for our load balancers. We do not make this kind of domain available because it is not necessary.
Will the old domain work when the new custom domain is set up?
No, it won’t. We replace the old domain with the new one. However, you can configure a redirect from the old domain to the new domain to preserve access for users with existing bookmarks or links, or you can delete the old domain entirely if it is no longer needed.
How can we switch to a new primary domain in Frontify?
Switching to a new primary domain in Frontify can be done without a full migration, provided both domains belong to the same Frontify account. Content, users, brands, projects, and libraries are shared across domains within the same account.
Follow these steps to switch to a new primary domain:
Internal confirmation: Confirm internally that the new domain should become the primary domain.
Plan the timeline: Choose a transition window during a period of low user activity.
Update SSO access: If using single sign-on (SSO), update your SSO user access lists to ensure all users can sign in through the new domain.
Redirect or delete the old domain: Decide whether to delete the old domain or configure a redirect to maintain access for users with existing links and bookmarks.
Verify landing page settings: Configure the landing page settings for the new domain, as each domain supports only one landing page.
After completing the switch, test the following:
User access and login to the new domain
Functionality of the redirect (if configured)
Landing page behavior and settings