Portals

A Portal is the front door you hand to end users: one link or embed, your branding, and a decision about who may come in. What a visitor can use behind the door is decided by the groups they belong to - see Users.

The split to keep in mind:

• Suites are content - a curated collection of Flows and Agents. The same Suite can be reached through many Portals.
• Portals are doors - branding, an admission list, and optionally a displayed Storefront.
• Storefronts are where plans are sold - displayed on a Portal or embedded anywhere.

What a visitor sees

The Portal adapts its presentation to what the visitor can reach:

• A single Flow or Agent renders as a standalone app.
• Several loose items render as a menu of products.
• One Suite renders as that Suite.
• Multiple Suites render as a workspace with a switcher.

Visitors sign in with their email and a one-time code - no passwords. A Portal embedded behind your own login can skip the code with signed sign-in. A Portal that displays a Storefront shows its offers before sign-in; a Portal without one is a sign-in-only door. See the end-user experience for the full journey.

How access works

• Assets are assigned to groups, on each asset's Assignments tab. A Portal does not carry a product list.
• The Portal admits groups - only the groups you name, or anyone who signs in when a Storefront is attached (Portals as doors).
• An attached Storefront sells plans - each plan is a group, so buying one is how a stranger becomes someone the door admits. Its default $0 plan is what new sign-ups start on.
• Everyone signs in - there is no anonymous use, and signing in by itself grants nothing.
• Only Portals gate - a direct share link to a Flow or Suite enters no Portal, so it opens without admission or group checks (embedding restrictions still apply). Share a Portal link when access needs to be controlled.

The pieces