Skip to main content

Creating a Portal Template

Learn how to create, customize, preview, and publish a portal template for a consistent client experience based on event type.

Written by Naomi Sherman

Choose the event type, add the sections clients need, and preview the portal before using the template.

Why this matters

A portal template is a reusable starting point for an event type. The event portal is the view for one client. Build the repeatable experience once, then check a sample event to see what the client will actually receive.

Before you start

Check the event type and who should see the portal. An account role with portal editing access may be required.

In Releventful

  1. Click Automations & Operations > Manage Portal Templates and click Create workflow for a new event type or Edit workflow for an existing one.

  2. Choose Start new, enter the event type name and click Create draft, or choose Draft changes for the existing type.

  3. Click Add workflow > Create with Rae, describe the tasks, forms, messages and booking steps, then click Build draft with Rae.

  4. Select each timeline item to correct it; click Save draft > Review saved draft > Try the client portal > Review event impact and publish.

How to make the most of this step

Choose the event type before adding the client experience. Create with Rae is the quickest way to create a draft for sales, booking, and planning together. Build manually is available for a specific item. Review the draft's messages, forms, tasks, and booking settings, then test the sample client portal and publish when the team agrees it is ready.

A useful decision

Build the reusable journey around the event type: inquiry, booking, then client planning. Rae can draft the whole flow; select every item afterward to correct wording, visibility, due dates, and which items are on.

Check the result

Preview the client's portal and verify access. A template edit may need to be applied to an existing event separately.

Important to know

Saving a template does not automatically prove an existing client's portal changed. Review event impact, open the event portal, and inspect the client view before sharing it.

Did this answer your question?