Sharing Within a Team

The Team plan lets members share work so the team builds up a library over time. What you can share, and how widely, depends on the feature. This guide covers what's currently shared, what's not, and the mechanics.

What's currently shared on a Team plan

Custom personas — Toggle "share with team" on the persona's detail page. Team members see it in their persona picker and can use it in their own projects.
Panels — Same toggle pattern as personas.
Quota pool — All interview, discussion, social-scan, and report quotas are pooled across the team. One member's heavy usage doesn't block another.
Team memory — Research done by any member feeds into team-level memory, so AI suggestions across the team benefit from everyone's history.

What's not shared yet (or only partially)

A few features are still rolling out. Before relying on these, check the current release notes.

Research projects — Sharing research projects with the team is on the roadmap. Currently, projects are personal by default.
Sage experts — Team-level Sage (consultable by all members) is on the roadmap. Currently, a Sage expert is owned by one person.
External sharing — No way to share with people outside your team today. Workaround is to export the report (Markdown/PDF/Word) and send it manually.

If you read this and the roadmap has changed, the principle still applies: the platform shares what the creator marks as shareable and nothing else by default.

How persona sharing works

When you create a custom persona, you decide during creation (or anytime later on the detail page) whether it lives in your personal library or the team library.

Personal persona: Only you see and use it. You can promote it to team-shared later.

Team-shared persona: Appears in the persona picker for every team member. Members can use it in their projects but cannot edit or delete it (only the creator can). If the creator leaves the team, edit rights transfer to the admin.

The same pattern applies to Panels.

Permission model in detail

The sharing rules are deliberately simple:

Creator has full control over their shared item (edit, delete, revoke sharing)
Team members can view and use shared items but cannot edit them
Admins can manage who has access to what and can revoke sharing if needed for compliance reasons, but cannot edit the content itself

This means there's no "editor role" for shared personas — if you want someone else to be able to edit your persona, you have to transfer ownership to them, which removes your edit rights.

What shared personas look like in practice

A typical scenario after a few months:

The team has built 30-40 custom personas covering their core user segments
New team members see this library on day one and can start producing research without first building personas from scratch
When someone leaves, their shared personas stay in the team library — no knowledge loss
The team avoids duplicate work (no two people independently building the same "25-35 year-old working mom" persona)

A note on quota pooling

Team quotas being pooled has a real upside and a real downside.

Upside: Nobody hits a personal cap. Heavy users and light users balance out naturally.

Downside: One member's runaway usage can exhaust the team's pool. Most teams don't hit this in practice, but if you're running a campaign of large-scale research, communicate with teammates first.

Admins can see per-member usage in Team Management → Usage Statistics, so you can spot heavy users early.

What "team memory" means in practice

When any team member runs an interview or builds a persona, the insights get attached to the team's shared memory. This means:

AI recommendations to one member can reflect research done by other members
Personas built by one member are visible to AI when assisting other members
New members inherit the team's accumulated knowledge without manual onboarding

The flip side: if someone makes a low-quality contribution, it pollutes the team memory. Treat the team library as curated, not write-only.

Common questions

Can I share a research project with just one teammate, not the whole team? Once research project sharing launches, per-person sharing is the planned default (rather than all-or-nothing). For now, projects are personal.

If I share a persona, can a teammate modify it? No. Only you (the creator) can edit. Teammates use it as-is. To let them modify it, transfer ownership.

What happens to my shared personas if I leave the team? They stay in the team library. Edit rights transfer to the admin. The content doesn't go with you.

Can I see who used my shared persona? Yes — the persona's detail page shows usage count and (in some cases) which projects have used it.

Why can't I share external reports with clients directly? External sharing isn't built yet. Export to PDF or Markdown and send manually. Most teams do this.

Inviting colleagues
Free vs. paid plans