---
artifact: prioritization-brief
version: "1.0"
created: 2026-03-22
status: complete
context: Prioritization brief for adding self-serve team invite controls to a B2B collaboration product
---

# Prioritization Brief: Self-Serve Team Invite Controls

## Context

**Background**
- Workspace admins currently invite teammates one person at a time from the settings page.
- Mid-market customers report that onboarding a new team of 20-50 people is slow and error-prone.
- Sales and support both see repeated requests for CSV upload or email-domain-based bulk invites.

**Goal**
- Reduce admin effort for team onboarding without introducing uncontrolled seat expansion or security gaps.

## Analysis

### Key Findings

- Interview notes from three customer calls show that manual invites are a consistent friction point during implementation week.
- Current product analytics show that 41 percent of invited users join workspaces in batches of five or more, which suggests meaningful demand for multi-user invite flows.
- Enterprise customers want domain restrictions and role defaults to remain enforced during bulk onboarding.

### Risks / Tradeoffs

| Risk or Tradeoff | Why it matters | Mitigation / Decision |
|------------------|----------------|-----------------------|
| Bulk invites could create accidental over-provisioning | Customers may exceed purchased seats or invite the wrong users | Require a review step showing seat impact before confirmation |
| CSV import adds implementation complexity | Parsing and validation logic is heavier than a simple multi-email field | Start with a paste-multiple-emails flow, then add CSV in a later slice if adoption is strong |
| Admins need confidence that roles are applied correctly | Incorrect default roles can create security and support issues | Force role selection before submission and show a per-user preview before send |

## Recommendation

1. Prioritize a phase-one bulk invite flow that accepts multiple email addresses in a single action.
2. Include seat impact messaging, role selection, and domain-policy validation in the first release.
3. Defer CSV upload until after the team measures adoption and support volume for the simpler flow.

## Open Questions

- Should bulk invites be limited to workspace owners in v1, or can admins use the flow too?
- Do we need an audit log event for each invite generated by the bulk action?
- What is the maximum number of email addresses the API can validate in one request without timing out?
