Publish a page and check visitor access
Release the reviewed page, then check that its actual address works for the people who should see it.
Publish a page and check visitor access
Release the reviewed page, then check that its actual address works for the people who should see it.
Before you start
Finish the page content, form fields and CRM routing checks. Know whether the page is for everyone or only people with a secure access link, and have permission to publish it.
Publish and open the page
- Open Pages in the correct workroom and reopen the page. Check its name and current state in Overview.
- Open the builder’s Inspector → Publish tab. Review the intended access mode: Public or Protected link. Protected link is described as access for people with a secure access link; choose the mode that matches your audience.
- Review the publishing target. The available actions include Use Workroomly URL, Managed domain and External domain. Use the address supplied by the app. For a custom domain, follow the instructions generated for that exact domain rather than guessing DNS records.
- Review the final page content and route, then use Publish for an unpublished page, or Update Publish when updating an already published page. Wait for the result before doing anything else.
- Return to the Pages list and Overview to check the saved publication state. In the publishing target, use Copy URL or Open to obtain the actual visitor address.
- Open that address as the intended audience. For a public launch, check in a signed-out browser as well; a signed-in preview alone does not show what an anonymous visitor can access.
- Read the visitor-facing title, content, fields and footer. Confirm that they match the released version before testing a submission.
Expected result
The page is published and its supplied address opens the correct content for the intended audience.
Remember: “Published” and reachable are separate checks. If access fails, keep the exact address and visible error for your administrator; do not switch hosts, guess DNS targets or bypass a browser security warning.
Continue learning
In this series: Build enquiry pages — guide 5 of 7.
Turn what you learned into the way the team works.
Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.