A live community changes its public address through Bevy Support. You create the DNS record Support sends you. Bevy manages the certificate.
Note: If your community is not live yet, domain setup is part of implementation. Contact your Bevy implementation contact. This page is for a community that is already live.
Note: The community address is changed through Bevy Support. On Admin Dashboard → Settings → General you set the site title and where the homepage redirects. Those steps are in General settings.
Checklist before you request the change
Work through this list before you ask Bevy Support to change the address. Include your answers in the Support request.
- New address. Have the domain or subdomain you want.
- Redirect. Decide whether the old address should redirect to the new one. A redirect sends people who still use the old address, including links in ticket emails, to the new address.
- Email sending domain. Decide whether the domain that community email is sent from should change too. That can happen separately from the site address, and it usually needs your networking team.
- Single sign-on. If members sign in with single sign-on, the new domain and URL must already be allowed in your identity provider so people can still sign in.
- Downtime. The site can be down for up to an hour while the change is made. Tell members and partners the new address a week or two before the change.
- Links you control. Plan to update links on your other websites, and how people will find the new address.
Request the change
- Open a request with Bevy Support. See Contact Bevy Support.
- Include the new domain or subdomain, whether you want a redirect, and whether the email sending domain should change.
- If you use single sign-on, include confirmation that the new domain and URL are already allowed in your identity provider.
Create the DNS record
Support tells you the target. Your networking team creates one record for the new address.
| New address | Record to create |
|---|---|
A subdomain, such as community.example.com | A CNAME record. Point it at the hostname Support gives you. |
A root domain, such as example.com | An A record. Point it at the target Support gives you. |
Important: Create the DNS record only after Support sends you the target. Changing DNS before that can interrupt the site.
Certificate
Bevy obtains and renews the certificate for the new address. You do not upload a certificate or choose the certificate authority. See SSL certificates.
After the DNS record is in place and Support has the details from the checklist, Bevy makes the change.