Worked examples

The same building blocks cover every case: groups assigned on the asset, Portals as doors, Storefronts for selling. The only difference between the first two examples is whether a group has a price on it. The third is a workspace that filled in both kinds of row.

All names below are invented.

Case 1: assign only

Brightline Studio built an Agent called Pitch Polisher for its own staff and a few outside consultants. No one pays.

1. Under Access > Users & Groups, create two Assigned Groups: Internal Team and External Consultants. Add people to each.
2. Open Pitch Polisher and, on its Assignments tab, add both groups.
3. Create a Portal, Brightline Workbench: set the branding, tick those two groups under Admitted groups, and attach no Storefront.

That is the whole setup. No Storefront exists, nothing about plans or Stripe appears anywhere, and runs are billed to Brightline's own credits. Someone who is not in either group reaches the door and is told they are not admitted.

Case 2: sell only, including $0

Brightline wants to sell Contract Reader to the public, with a free tier.

1. In the plan catalog on Deploy > Storefronts, create Starter at $0 and Pro at a monthly price. Each plan creates its own group.
2. Open Contract Reader and, on Assignments, add Pro. Add Starter too if free users should get the asset under Starter's smaller allowance.
3. Under Deploy > Storefronts, create Brightline Pricing: offer Starter and Pro, make Starter the default. Set Send buyers to the customer Portal below.
4. Create a Portal, Brightline Customers: branding, and Brightline Pricing attached under Self-service, which opens the door to anyone who signs in.

Visitors who open the Portal sign in with their email and start on Starter straight away; the offers are one click away when they want Pro. The same Storefront can also be embedded on brightline.example's products page - buyers there go through Stripe Checkout, land on a thank-you state, get a welcome email, and sign in at Brightline Customers.

Nothing about Assigned Groups is visible in this flow unless the team opens Users & Groups.

Case 3: both, from one asset

Brightline now wants employees to use Contract Reader for free while customers pay.

• Contract Reader's Assignments tab lists four rows: Internal Team, External Consultants, Starter, Pro. One editor, one list.
• Either two doors or one:
  • Two Portals - Brightline Workbench admits Internal Team and External Consultants with no Storefront, so nobody else can even sign in; Brightline Customers has Brightline Pricing attached, so anyone may sign in and pick a plan.
  • One Portal that admits everyone and displays the Storefront. Employees skip the pricing screen because their group already reaches the asset; strangers see the offers.
• A user who is both in Internal Team and on Pro sees the union: everything either group reaches, metered against Pro's allowance while it lasts.

Embedded storefront with a reseller

Brightline lets a partner resell Pro.

• Storefront Brightline Pricing offers Pro, embedded on brightline.example/products, Send buyers to Brightline Customers.
• Storefront Partner Pricing offers the same Pro plan, embedded on the partner's site, Send buyers to the same Portal.
• A buyer on either site joins the Pro group, receives the welcome email, signs in at Brightline Customers, and gets Contract Reader.

Two Storefronts, one door, one plan group, one subscription and one credit pool per buyer.