Team & roles
Invite teammates and control what they can do with role-based access.
ChirpBack has four roles per project: Owner, Admin, Member, and Read-only.
| Role | What they can do |
|---|---|
| Owner | Everything. Manages billing, owns the project, can transfer ownership. |
| Admin | Full access — can invite teammates and manage roles. |
| Member | Read + write project content (feedback, surveys, announcements, backlog). |
| Read-only | View-only access. |
Member is the default role for new invites.
Where to manage them
Project Settings → Members. The Settings sidebar also includes Overview, Workflow, Developer, Custom Domain, Brand, Feedback Widget, AI & Credits, and Danger Zone.
Inviting members
- Project Settings → Members → "+ Invite User"
- Enter their email and pick a role
- They appear under the Invited Users tab until they accept
Changing a role
In the Members table, click the … action menu on any member's row → Change role → pick Admin / Member / Read-only.
Removing a member
In the same … menu → Remove user. They lose access immediately. Removed users show with a "Removed" badge and can be re-invited from the row to restore access.
Seats and billing
Billing is account-level, not per-project. Each member added to any project counts as one seat across the account — adding the same person to a second project does not consume an extra seat.
Plan limits:
| Plan | Team members |
|---|---|
| Starter | 2 (1 admin + 1 collaborator) |
| Growth | Up to 5 |
| Enterprise | Unlimited |
SSO (Enterprise)
On the Enterprise plan, you can require SSO for all members of your account via SAML — Google Workspace, Okta, Azure AD, or any SAML 2.0 provider.
Audit log (Enterprise)
Track who did what — member additions, role changes, integration updates.