Teams
Group the people who handle the same work so alerts, tasks and approvals reach the whole group, and give the group a role in one step.
A team groups the people who handle the same work, for example Finance or Front desk. Once a team exists, anywhere Muin asks “who gets this” you can pick the team instead of naming people one by one. You manage teams at Settings → People & Access → Teams.
Create a team
- Open Settings → Teams and choose Create team.
- Give it a name people will recognize, and pick a type:
- Hand-picked: you choose the members. Available on every plan.
- Rule-based: members follow a rule, like everyone in a department. Rule-based teams need the Growth plan.
- Muin opens the new team. For a hand-picked team, choose Add members. Only people with a login can join a team. Anyone who could not be added is listed with the reason.
You can also add people to hand-picked teams from other places:
- When you invite them. Pick teams under Teams (optional) in the invite window or in Bulk Invite. The person joins those teams when they accept. Rule-based teams and teams filled by directory sync aren’t offered. See Inviting members.
- From their member page. The Teams section adds them to a hand-picked team or removes them from one. Teams filled by directory sync or by a rule are shown there read-only.
To change who is on a rule-based team, open the team and choose Edit. Change the rule; Muin shows how many people the new rule matches before you save. When you save, members are recomputed: people the rule no longer matches leave the team and lose its roles, and people it now matches join. A rule on whether people receive assistance can only be changed by someone with the aid permission.
Give a team a role
Under Roles this team gives, pick a role. Every member of the team holds that role while they are on the team.
- On a member’s page, a role that comes from a team shows the team as its source.
- Removing someone from the team takes back any role they hold only through it. Roles assigned to them directly stay.
- Owner and Admin are access levels, not roles. A team can’t give them; set them on the person.
Teams or direct roles?
- Use a team when several people do the same job. Give the team its roles once and pick the team for alerts, approvals and tasks. A new person joins one team and gets all of it.
- Give a role directly for a one-off: one person who needs something their team does not.
- Owner and admin are access levels. Set them on the person. A team can’t give them.
- With directory sync on, your identity provider decides who is on a synced team. Change membership there.
- To see why someone has a role, open their member page. Each role says where it comes from.
In short: same job for several people? Use a team. One person’s exception? Give the role directly. The ? at the top of Settings → Members, Teams, Roles & Permissions, Directory sync and Notifications opens the same guidance with a diagram of how teams, roles, members, access levels and directory groups fit together.
Send alerts, tasks and approvals to a team
Pick the team in Settings → Notifications → Who gets what, or in any other “who gets this” field. Whoever is on the team at the time gets it, so adding or removing a member updates every place the team is used.
If nobody is picked, an alert goes to the workspace owners and admins.
A team member who cannot see the area an alert is about is skipped, and the picker says so, for example “2 of 5 can’t see Finance”. If you can manage roles, the picker offers a one-click fix: Give the team the suggested role.
Where teams are used
| Where | What happens |
|---|---|
| Settings → Notifications → Who gets what | The alert goes to everyone on the team who can see that area. See Notification Settings. |
| A form’s Response alerts | Each response is sent to the team instead of to every admin. |
| Team tasks | The task shows in every member’s inbox until one of them chooses Claim. It then leaves the others’ lists. Release sends it back to the team. If two people claim at once, the second is told “Already claimed by” and the name. |
| Sharing a document | Pick the team when you share. New members get access and removed members lose it. |
| Discussions | Type @ and the team name in a record’s discussion. Team members who can see the record are notified. |
| Escalations and approvals | A support escalation, an SLA escalation or an approval step can go to a team. See Approvals and Spending Policies. |
| Directory sync | A directory group can fill a team. See Directory Sync (SCIM). |
Teams are managed only here. They do not appear in Audiences.
Delete a team
Deleting a team removes it for good and takes back every role it gave. Roles assigned to people directly stay. If the team is still picked somewhere, Muin lists those places so you can pick someone else there first.