Who needs it
The roles Link is built for, and what each one can actually do here.
What a team member can reach in Link is governed by team-access grants and domain/source
scoping — a separate, Account Platform-owned mechanism (host_in_scope, creator_id; see
Boundaries). This page describes what each role does once
they're in, not how the grant is configured.
| Role | Comes here for |
|---|---|
| Workspace owner | Everything — domains, smart links, the landing builder, QR, traffic sources, the Telegram gate |
| Team member with a domain/source scope | Only the domains or traffic sources they've been granted; a denied grant is a 403, an out-of-scope domain is a 404 |
| Multi-page creator | The same domain pool across every page they run — domains aren't siloed per page |
| Platform's AI copilot | A narrow slice of the owner's own surface, called through the same code the panel uses |
Workspace owner
Everything in this product's index is reachable, gated only by plan where a limit applies (extra domains, buy-domain): buying and connecting a domain, rotating a burned one, building the landing page (buttons, profile card, backgrounds, popups), wiring smart links and ad platforms, generating QR codes, writing traffic-source rules, and connecting the Telegram gate bot. A handful of the most security-sensitive actions — connecting or disconnecting the Telegram bot, refreshing its webhook — are additionally gated to the literal workspace owner even when a team member otherwise has full domain access; see Admin endpoints for exactly which routes those are.
Team member with a domain/source scope
A team member's grant can be narrowed to specific domains or traffic sources. Inside that scope they get the same screens an owner does — editing buttons, checking domain health, reading the traffic dashboard — but every domain-scoped call is fenced server-side, not just hidden in the UI: an out-of-scope domain returns 404 (not 403), so a scoped team member can't even confirm a domain outside their grant exists.
Multi-page creator
Domains and traffic sources are account-wide, not per-page. A creator running several pages sees one shared pool of domains and can point any of them at any page's smart links — there's no per-page domain silo to manage separately.
Platform's AI copilot
The in-panel AI agent can act on Link's behalf through the same official handlers a human uses — connect a domain, claim a free slug, suggest a branded domain — never through a direct table write. See Boundaries for the write paths that currently bypass this (Club's free-pool and the AI write-tools layer are two documented, still-open exceptions).
What's next
See Admin endpoints for the full route-by-route reference, or Connections for the cross-product contracts behind these boundaries.