Team roles, invites and project access

Bring the whole team in without counting seats, then decide who manages the organization and which projects each person can see.

Team access in Flawsnap controls who can sign in to your organization and what they can see. There are three roles (owner, admin and member), invites by email or link, and per-member project access so someone can be limited to specific projects. Both plans include unlimited members, because pricing is per organization.

The three roles

RoleCan doCannot do
OwnerEverything, including changing any roleLeave or be demoted if they are the last owner
AdminInvite people, manage projects, see every projectChange an owner or make someone an owner
MemberWork on reports, boards and docs in their projectsManage the team

Inviting people

  1. 1

    Send the invite

    An owner or admin invites by email from the Team page.

  2. 2

    Or share the link

    Each invite can be resent or copied as a link, useful when an email lands in spam.

  3. 3

    Accept within seven days

    Invites are valid for seven days. The invitee can sign up with email and password or with Google.

Limiting a member to certain projects

By default a member can see every project. Switch a member to specific projects instead, and the member sees nothing outside them: no reports, boards, docs or Insights, and no access through API keys, MCP or widget sign-in. Admins always see every project.

New projects are not added to a limited member automatically. When you start a new client project, add the people who need it.

This is how an agency can invite a client contact to review their own site's board without seeing other clients. See agency client feedback.

Team sign-in from the widget

Reporters do not need an account. Customers and clients can report anonymously. But when your own team reports, you usually want their name on it.

Turn on Let team members sign in from the widget and app in the project. The report form then shows "Team member? Sign in". The member approves the site in a portal popup, and their reports carry their name.

  • The site gets a reporter token, not a portal session. It can only send reports to that project, and lasts 30 days.
  • Sign-in is offered on https sites, plus localhost for development.
  • If your site sends Cross-Origin-Opener-Policy: same-origin, the popup cannot connect. Use same-origin-allow-popups or unsafe-none.
  • You can also trigger it from your own button with Flawsnap.signIn(), called from a click.

Signing in to the portal

People sign in with email and password, verified by email, or with Google. The sign-in, sign-up and invite forms are protected by Cloudflare Turnstile. Passwords are hashed with argon2id. There is no SAML single sign-on or SCIM provisioning.

Why there is no seat count

Starter ($9) and Pro ($19) are priced per organization per month, with unlimited members on both. Invite the designer, the support lead and the client without working out who is worth a seat. See pricing.

Questions

Does an AI agent get its own role?
No. An agent acts as the person who connected it, with their project access and the read-only or read-and-write level they chose. Its actions are marked via agent.
What happens to a limited member's access when I add a project?
Nothing. New projects are not added automatically to members limited to specific projects; add them yourself if they need it.
Can reporters on my website see other people's reports?
No. The widget sends reports; it does not show your board. Only signed-in members of your organization can read reports, and only in projects they can access.

Try it on your own site

7-day free trial, then $9 a month for Starter or $19 for Pro, per organization, with unlimited team members.

Updated