Ownership, assignment, and status across the team's work.
When your week disappears into "who's working on what" chat threads, the answer should be "the workspace tells me." m18t's team layer makes ownership and status visible at the level that matters, across features, content, releases and events, in every brand the team owns.
Multi-user is live. Custom roles aren't yet.
m18t is multi-user today: invite teammates, give them roles from the system set, scope members to specific brands, assign work with assigned-to fields, and mention people to notify them. Nothing to migrate; existing accounts got these features in place.
What isn't built yet: creating and editing your own roles (today you pick from the fixed set), richer ownership views, SSO, and audit logs. If your team needs hand-crafted permission matrices, that part isn't built. Tell us at contact what your team needs and we'll say honestly whether m18t covers it today.
The surfaces that change when the team shows up.
PD workspace with ownership
Every feature, model, controller and event has an owner. The team lead sees their own queue, the team's queue, and what's stalled, without asking. Ownership views filter by person and by brand.
Content + assigned-to
The editorial queue with owners and due dates. Writer → editor → publisher handoff is clear. Marketing leads see what's in each lane.
Whiteboards for team rituals
Planning sessions, retros and project kickoffs, with the actual team's entities on the canvas. Boards stay relevant because they reference real entities the team owns.
Status by team or brand
Same opinionated status set, seen across the work the team owns. Mine / theirs / stalled / due-this-week filters reflect actual ownership, not just project labels.
Per-brand role assignment
For agencies and multi-brand teams: which team members work on which brand, with brand-scoped permissions. No accidental cross-client edits.
Stop recovering state in 1:1s.
Today, most team leads spend mornings recovering state: checking the task tracker, scrolling chat, asking the engineers what they're actually working on. The 1:1 becomes a status-update meeting because the workspace doesn't give a clean answer to "what does each person own and where is it?"
m18t's team layer makes that answer visible, with the same brand-switcher and the same status set the team already uses. PD entities show owners. Content pieces show editors. Release artifacts show authors. The team lead opens m18t and sees the picture without asking.
1:1s go back to being about people, not state.
Frequently Asked Questions
Bring your team into the workspace.
Sign up, invite your teammates, and see the picture without asking. Or contact the founder if your team has specific needs we should hear about.