How it works
Your team, step by step
Their own link, not yours
Revoking a seat revokes that link only. Nobody has to change anything else.
Roles that mean something
Reading, approving, publishing and billing are separate. The person who moderates the queue does not have to be the person with the card.
Two seats on Starter, more on Pro
Pro adds seats at $5 a month each, as a line on the subscription.
Safe by design
The rule that makes it safe to have
Clear boundaries
What it will not do
Every capability page ends with this list. It is the part that says what you are actually buying.
- A seat cannot delete the project.
- A seat cannot add a paid extra.
- A seat's link never becomes the owner's link.
Where it lives in the code: lib/seats.ts · lib/access.ts · app/dashboard/[token]/team/page.tsx
Questions
Asked about this
From Help, where every answer is written from the product as it runs.
Can you read my testimonials?
An operator can open a dashboard, and the privacy page says so in plain words: we can, we do it to answer a request you made or a fault you reported, and not otherwise.
Is my customer's email address ever public?
No. An author's email address is in no public answer, from any endpoint, on any plan.
Can I give somebody access without giving them my link?
Yes — a seat has its own link and its own permissions, and revoking it revokes only that one. A seat cannot delete the project or add a paid extra to your subscription.
Does the widget track my visitors?
It counts views, plays and clicks per widget so you can tell whether anybody is reading them. There is no visitor profile and no cross-site identifier. Your page's visitors are not our product.
This is running now
Open a project and use it. Nothing on this page is a roadmap.