Teams Guide

Share your Minolith projects with team members. Assign individuals from your roster to specific projects with granular role-based access control.

Prerequisites:

• A Minolith account on a Team plan ($15/month) or Teams Plus plan ($25/month)
• At least one project created

Overview

Teams in Minolith work as a roster model:

1. Create a team — a global member roster tied to your account
2. Invite members — add people to your roster by email
3. Assign members to projects — pick individuals from your roster and set their access role per project

Team members log in to their own Minolith accounts. They see shared projects alongside their own personal projects. If a team member has no personal projects, they pay nothing — all usage on shared projects is billed to the team owner's subscription.

Team plans also unlock task assignment to team members (Solo plans can only assign to agents), custom task workflows with up to 10 statuses, and the Documents service for foundation file uploads.

Plans and Pricing

• No per-seat charge — invite as many members as you need
• One credit pool covers all your projects (personal + shared)
• The team plan replaces your personal subscription
• Team members with no personal projects are billing-free

Subscribe from the Billing page or the Team page in your dashboard.

Step 1: Subscribe to a Team Plan

1. Go to Billing in your dashboard
2. Select Team ($15/month) or Teams Plus ($25/month)
3. Complete checkout via Stripe

Once subscribed, the Team area in your dashboard unlocks.

Step 2: Create Your Team

1. Go to Team in the sidebar
2. Enter a name for your team
3. Click Create Team

You are automatically added as the team owner. The owner has full admin access and manages billing, invitations, and member assignments.

Step 3: Invite Members

1. Go to Team in the sidebar
2. Scroll to the Invite section
3. Enter the team member's email address
4. Optionally add tags (e.g. dev, design, seo) to categorise the member
5. Click Send Invite

The invitee receives an email with a link to accept the invitation. The link expires after 7 days. If they don't have a Minolith account yet, they'll need to register first, then accept the invite.

Member Tags

Tags are organisational labels — they help you identify members by their role or specialty. Tags have no effect on access control. Examples: dev, design, seo, qa, devops.

You can update a member's tags at any time from the team roster page.

Step 4: Assign Members to Projects

Once members have accepted their invites, you can assign them to projects:

1. Go to a Project in your dashboard
2. Click Members in the project sidebar
3. Select a team member from the dropdown
4. Choose their access role:
   • Admin — full read/write access to all project services, can edit and delete the project
   • Member — full read/write access to all project services
5. Click Assign

Per-Project Roles

Roles are set per project. A team member can be an Admin on one project and a Member on another. The project owner always has full access regardless of role assignments.

Project settings (name, slug) and API key management can be done by owners and admins. Members have full read/write access to project services (Context, Changelog, etc.) but cannot modify project settings, delete the project, or create/revoke API keys. Members can view existing API keys but need an admin or owner to create new ones.

How It Looks for Team Members

Team members log in to their own account. On their dashboard home page, they see:

• Your Projects — their personal projects (if any)
• Shared With You — projects they've been assigned to, showing the owner's name and their role

Team members navigate shared projects the same way they navigate their own — the sidebar shows the full project sub-nav (Context, Changelog, Feedback, Runbooks, Agents, Tasks, API Keys).

Team members can also leave a shared project at any time from the project overview page. The project owner is notified by email when a member leaves.

API Keys and Billing

• API keys belong to projects, not individual users
• Usage on shared projects is billed to the project owner's subscription
• The team plan's credit pool covers all projects — personal and shared
• Team members do not need their own subscription to access shared projects via the dashboard

Only the project owner and admins can create and revoke API keys. Members can view existing keys but cannot manage them. All API key usage on shared projects bills against the project owner's credit allowance.

Tasks and Team Collaboration

Team plans unlock the full Tasks experience. Assign tasks to agents or team members and track work through custom workflows.

Assigning tasks

On Team plans, the task assignee dropdown includes:

• Agents — any agent definition in the project
• Team members — all members assigned to the project
• Project owner — the account that owns the project

Solo plan accounts can only assign tasks to agents.

Custom workflows

Team plans can customise the task workflow beyond the default open → review → done. Go to Tasks → Workflow in the project sidebar to define up to 10 statuses. The first status must be open and the last must be done.

Example: open → in_progress → review → qa → done

Solo plan accounts use the fixed open → review → done workflow.

Documents

Team plans include the Documents service — upload foundation files (PDFs, Word documents, spreadsheets, images, and more) and make them available to your AI agents via API and MCP. Solo plan accounts see a prompt to upgrade when they visit the Documents page.

Team feed

The team feed shows all task activity across the project in chronological order — status changes, assignments, comments, and commits from both agents and team members. Query it with get_team_feed via MCP or GET /v1/tasks/feed via REST. Use the since parameter to see only activity since your last session.

Removing Members

From a project

Go to Project > Members, click Remove next to the member. They immediately lose access to that project.

From the team roster

Go to Team, click Remove next to the member. This removes them from the roster and from all projects owned by you. The team owner cannot be removed.

FAQ

Can a team member also have their own personal projects? Yes. A team member's personal projects use their own subscription (or free trial). Shared project usage is billed to the team owner.

What happens if the team owner cancels their team plan? Team members lose access to shared projects. The projects still exist under the owner's account but are no longer accessible to team members.

Is there a limit on team members? No. Team plans have no per-seat charge and no member limit.

Can I have multiple teams? Currently, each account can have one team. If you need multiple teams, use project-level member assignments to control who sees what.

Do team members see the Team page? Team members who are not the owner do not see the Team management page. Only the team owner manages the roster and invitations.