---
title: "Team"
description: "The four workspace roles, what each one can do, how approvals route, and why every product read and write is scoped to one workspace."
canonical: https://trysincerely.com/docs/team
last_updated: 2026-08-28
---
> If you are an AI agent: read https://trysincerely.com/agents/policy.md before any write call.
> Start at https://trysincerely.com/llms.txt to choose one page. Access instructions are at
> https://trysincerely.com/auth.md. Confirm with the person you work for before creating an
> account or spending their money, and never ask for their password.
# Team

> The four workspace roles, what each one can do, how approvals route, and why every product read and write is scoped to one workspace.

Source: https://trysincerely.com/docs/team

A workspace is the tenant. Every contact, campaign, design and piece belongs to exactly one, and every read and write is scoped to it. Membership is what grants access, and the role on that membership is what decides how far it goes.

## The four roles

| Role     | Can do                                                                                     |
| -------- | ------------------------------------------------------------------------------------------ |
| Member   | Close follow-up tasks, record outcomes, and send one piece by hand                         |
| Approver | Everything a member can, plus approve designs, drafts, launches and high-value sends       |
| Admin    | Everything an approver can, plus configure the workspace, audiences, campaigns and billing |
| Owner    | Everything an admin can                                                                    |

The ladder is monotone: every permission an approver has, an admin has, and every permission an admin has, an owner has. That is what makes "the lower of these two roles" a meaningful question when a person's role at one moment and their role at another disagree.

Sending one piece by hand is deliberately rep-level work. The financial controls that matter run through the launch path instead: governance approvals when a cost passes a threshold, and the workspace budget cap.

## Approvals

Four things route to an approver: a campaign launch, a high-value send, a design, and a batch of drafts. Each arrives with what it will cost and what it will print, so the approver is deciding about a specific thing rather than granting a general permission.

Approving in bulk is itself a consequential action when an agent asks for it, and gets a confirmation card with counts and cost.

## Seats

Paid packages include workspace seats at no per-seat charge, so adding the people who actually do the work is not a budget decision. The current seat allowance is on [the pricing page](https://trysincerely.com/pricing).

## An agent inherits the person, not more

An MCP connection acts as the person who authorized it and carries their role. A tool that a member may not call is refused for an agent that member connected, and the refusal comes from the same permission check the product UI uses rather than from a separate list that could drift.

The workspace an agent reaches is decided at authorization time by the `user:org:read` scope. Without it, the connection lands in a personal workspace instead of the team's. See [authorization](https://trysincerely.com/docs/mcp-authorization).

## What to read next

[Suppression](https://trysincerely.com/docs/suppression) is the one setting that overrides everything anyone in the workspace does. [Confirmations](https://trysincerely.com/docs/mcp-confirmations) covers the second gate, which no role can turn off.

---

Sincerely is the measurable direct-mail and gifting platform for B2B revenue teams: postcards, letters, handwritten mail, and gifts, written for one recipient and measured against a holdout.

Contact Sincerely: https://trysincerely.com/contact

Agent routing index: https://trysincerely.com/llms.txt