Overview
Invite collaborators to help run your MemberPass projects with fine-grained permissions — available on Growth, Enterprise, and Custom plans.
When your membership business grows beyond one person, you'll want to bring other people in — a designer to update banners, a community manager to handle members, an accountant to reconcile payments — without handing over your password. That's what Teams are for.
Teams is an agency-level feature available on the Growth, Enterprise, and Custom plans. If you're on the Free or Starter plan, you'll see a toast reminding you to upgrade when you try to use team features. See Activate your subscription.
The building blocks
MemberPass teams are made of four concepts that work together:
Teams
A team is a container of people you collaborate with. You can create more than one — useful for separating, say, a chess coaching team from a photography club.
Members
People invited by email into a team. Each member is assigned a role when they accept.
Roles
A bundle of permissions (like "Community Manager" or "Billing Admin"). You pick which role each member gets.
Groups
A second way to slice permissions. Groups let you assemble a set of members and grant them permissions as a unit — handy when someone needs one-off access without creating a whole new role.
Abilities
The 35 individual permissions you can grant. Combine them freely into roles and groups.
How it fits together
Here's the mental model to keep:
- You (the account owner) create a team.
- You invite people by email into that team. Each invitation comes with a role you pick at invite time.
- Inside the team, you define roles — named bundles of permissions, like "Editor" or "Finance".
- Optionally, you define groups — ad-hoc collections of members + permissions, useful when role boundaries aren't the right fit.
- When a member accepts their invitation, they can sign in to MemberPass with their own account and see your projects through the lens of the permissions you granted.
Team members sign in with their own MemberPass credentials, not yours. They register separately via Telegram (the normal path — see Creating an account), and your team invitation then links their account to yours.
Where it lives in the dashboard
All team management is inside Settings:
| Page | URL | What you do there |
|---|---|---|
| Teams | /settings/teams | Create, rename, or delete teams |
| Members | /settings/teams/{team}/members | Invite people, see pending invitations, remove members |
| Roles | /settings/roles | Create roles and assign permissions to them |
| Groups | /settings/groups | Create groups and attach members + permissions |
Who can do what?
- You, the team owner, can always do everything — create, invite, define, delete.
- Team members can only perform actions their assigned role (or membership of a group) permits.
- Roles can only be deleted by the person who created them or by the team owner — this prevents collaborators from accidentally removing critical shared roles.
- Groups can only be deleted by the team owner.
When to use teams vs. sharing your login
Never share your account password. Teams exist precisely so you don't have to. Even if it feels like overkill for a two-person collaboration, a proper team setup:
- Gives each person their own sign-in history so you can audit who did what.
- Lets you revoke access instantly when someone leaves — no password rotation required.
- Respects MemberPass's security features (2FA, passkeys) per person, not shared.
Related
- Create a team — the first step.
- Invite members — email-based invitations.
- Roles — build reusable permission bundles.
- Groups — ad-hoc permission slices.
- Ability reference — the full list of 35 permissions.