Organization managers can create and manage more than one website, change its Activity Messenger subdomain, connect custom domains, and protect an entire website with a shared password.
A user with website-editing permission can open the builder and edit page content. Manage websites, domain assignment, access settings, and other organization-level actions require organization-management permission.
Ask an organization manager to complete domain or website administration when the corresponding actions are not visible. Do not share an administrator account merely to make the controls appear.
Open Website, then select Manage websites. The management screen identifies the primary website and provides actions such as:
The primary website cannot be deleted. If the management screen offers a workflow to make another website primary, use that explicit action and review its impact before confirming.
Use an additional website when an organization needs a distinct experience for clients, staff, a facility, a program, or a campaign that should not share all pages and global design with the primary site.
The subdomain must be available and unique. Each website has its own pages and site settings, so creating a second website does not automatically copy the primary website's content.
Open the website's Edit action. The name helps administrators distinguish sites. The subdomain is part of the public address.
Changing the subdomain releases the old value. Existing bookmarks, messages, QR codes, social posts, and external links can stop working. Before saving a change:
Do not assume the old subdomain will remain reserved or redirect automatically.
In the website's edit settings, enable password protection and enter at least eight characters. Save the settings, then test the website in a signed-out browser.
Password protection applies to visitors across that website. Signed-in administrators can still access the editor. Disable the setting and save when the shared password is no longer required.
A website password is a shared gate, not an individual client account:
Use individual account and permission features for client- or staff-specific information.
Open Domains for the intended website. Add the exact hostname visitors will use, such as an apex domain (example.org) or a subdomain (programs.example.org). Add each hostname separately if both the root and a www or other subdomain must be supported.
Assign the hostname to the correct website. If it is already assigned elsewhere, review the reassignment carefully: moving it changes which website responds at that address.
The domain screen provides the DNS records required for:
Copy the displayed record names and values exactly into the DNS provider. The required record can differ for an apex domain and a subdomain, so follow the on-screen instructions for that hostname rather than a generic example.
DNS updates can take time to propagate. Return to the domain screen and retry verification after the records are publicly available.
After successful verification, Activity Messenger provisions and renews HTTPS automatically. Keep the SSL-verification CNAME record in DNS. Removing it can prevent future certificate renewal even if the website continues to load temporarily.
When verification fails:
Coordinate with the domain owner before changing DNS. Email and other services can share the same domain and must not be disturbed.
The primary website cannot be deleted. A secondary website has a delete action with confirmation. Treat deletion as destructive:
If the intention is only to keep visitors out temporarily, use draft pages or password protection instead of deleting the website.
Before announcing a new address:
www, and other hostnames that were deliberately configured;