Team Members & Roles

Multi-Person Stores Aren't an Afterthought#

Most chat tools have one user account per store. Kwiro lets you invite teammates so your support lead, content writer, or part-time staff can read conversations and contribute, without touching billing or settings.

Plan Limits#

Plan	Team seats
Free	1 (just you)
Pro	1
Growth	3
Scale	10

Two Roles#

Owner#

The single owner of the account. Always you (whoever signed up). Can do everything:

• Read all data (conversations, sales, memory, gaps)
• Edit / pin / delete memory
• Resolve knowledge gaps
• Edit widget config + AI personality + custom prompts
• Manage billing (upgrade, downgrade, cancel, view invoices)
• Invite, remove, and change roles for members
• Generate / regenerate API keys

There can only be one Owner per store. To transfer ownership, contact [email protected].

Member#

Read-only by default. Members can:

• ✅ Read all conversations, transcripts, sales, gaps, memory, products
• ✅ See dashboards, KPIs, charts
• ✅ Mark a conversation with a private note (visible to the team, not shoppers)
• ❌ Cannot edit / pin / delete memory
• ❌ Cannot resolve knowledge gaps
• ❌ Cannot edit widget config or AI personality
• ❌ Cannot manage billing or see invoices
• ❌ Cannot generate or revoke API keys

The Subscription / Billing pages and Memory / Knowledge Gaps editing surfaces are hidden for Members — they can read the data but the action buttons aren't there.

How to Invite#

1. Dashboard → Team.
2. Enter the teammate's email + role (Member is the only option for now).
3. Click Send invite.
4. They receive a magic-link email. Click it, they're in.

Pending invites show in the team list with a status pill. Cancel them any time before acceptance.

Why Read-Only for Members#

We deliberately scope Members tightly. Shape-changing actions (memory edits, knowledge gap resolutions, custom prompts) affect every shopper conversation forever. Routing those through one person keeps the AI's voice consistent.

If you want a teammate to suggest changes, the workflow is: they comment / Slack you with the proposed change, you (Owner) make it.

Future: Admin Role#

A middle role between Owner and Member — can edit memory + resolve gaps, can't touch billing — is on the roadmap. Email [email protected] if you'd find it useful, helps us prioritise.

Removing a Member#

Team page → click member → Remove. They lose access immediately. Their past activity (notes, etc.) stays in the audit log.

What Members See in the Subscription Page#

A small "Read-only — billing changes route through the Owner" banner. They see the current plan and usage but no Cancel / Upgrade / Manage buttons.