Every team, every member, every role — on the record.
Group teammates into teams. Invite existing Monirum users by Public User ID. Land them in the right workspace role. Keep a record of who joined, who changed roles, and who left.
Most teams don't have an access problem.
They have a clarity problem.
Three roles. One covered workspace.
Owner does the deciding. Co-Admin runs the day-to-day. Member does the work. Together they cover everything — no permission matrix required.
People belong to teams. Teams belong to the work.
Group teammates into named teams — each with a name, description, color, members, and team leads.
One invite. Real surfaces. Zero settings safari.
Admins invite existing Monirum users by Public User ID. The invite lands as an in-app notification — the new teammate accepts, and the workspace_members row is live.
Action → Audit → Searchable. Forever.
Joins, role changes, and removals append a workspace_events row. Visible in the workspace activity log — chronological, paginated, with actor and target.
Every team shows up as its own view.
A team in Monirum carries a name, description, color, members, and leads. KPIs can be assigned to a team. Inbox @mentions can address the whole team.
What the screens actually look like.
Three of the surfaces that ship today — the invite card, the member profile, and the team profile. Same composition, same fields, same buttons.
Three workspace roles. Two flavors of fine-grained access.
Workspace roles stay coarse on purpose. When a team needs finer scoping — by job function or by tool — role labels and tool grants do the work.
Questions teams ask before turning on Members.
Don't see your question? Reach out — every message gets read.
Talk to a human