Creating a Portal

Create it

1. From the sidebar, go to Deploy > Portals.
2. Click New portal and give it a name (end users can see it, so name it for them, not for your team).
3. The Portal detail page opens, with its pages (Access, Self-Service, Branding, Onboarding, Webhooks) in the sidebar.

Decide what it shows

A Portal has no product list. What a visitor can use is decided by the groups they belong to, so before the door is useful, at least one group must be assigned to an asset. Three cases:

• Private door (employees, consultants, invited customers) - create an Assigned Group under Assign > Groups (Users & Groups), add the people, assign the group to the assets. Nothing about plans is needed.
• Selling - create plans under Sell > Plans & Credits (Self-Service Plans), assign them to the assets, and put them on a Storefront.
• Both - do both; the Assignments tab lists both kinds of row side by side.

Set admission

On the Access page:

• Admitted groups - the groups this door is for. Plans count as groups. Without a Storefront attached, only members of an admitted group can sign in, and an empty list admits nobody.
• Plans from the storefront - a read-only list of the plans offered by the attached Storefront. Anyone who picks one can sign in. Attaching the Storefront happens on the Self-Service page (below).

Sign-in is always required. A visitor verifies their email with a one-time code (or arrives through HighLevel single sign-on) before anything renders, and signing in by itself grants nothing.

Sign-in is always passwordless. Identities are created on first sign-in (or provisioned via the API). See Portals as doors for the full picture.

Pick a Storefront

On the Self-Service page, optionally turn on Enable Self-Service and pick a Storefront. The sign-in screen then offers a Sign up button to it, and a signed-in visitor with no plan is pointed at its offers. New sign-ups start on the Storefront's default $0 plan when it has one. Leave it empty for a private door.

Share it

The Share button in the Portal's header gives you:

• A direct link - the /d/... entry URL, unique to this Portal.
• An embed snippet - an iframe you can drop into your own site.

The same entry surface serves both. Anyone landing there gets the Portal's branding, its admission rule, and its attached Storefront.

Next steps

• Brand it - logo, colors, and email sender.
• Wire up webhooks - get notified when someone signs up.
• Understand what your end users see.