--- title: "Team" description: "The four workspace roles, what each one can do, which launches need an approver, and why every product read and write is scoped to one workspace." canonical: https://trysincerely.com/docs/team last_updated: 2026-10-27 --- > 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, which launches need an approver, 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 | Owner is the role in a one-person workspace. In a team workspace the top role is admin, and invitations carry admin, approver, or member. 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. ## Per-member controls Three switches on the Team tab narrow or widen one person's reach without changing their role: - **Campaign building** lets a member create and edit designs and campaigns, which members cannot do by default. - **Sending block** removes one-off sending for that person. - **Monthly gift budget** caps what that person can spend on gifts each month. The send pre-flight checks it, and so does the credit reservation. A member can send only an approved design. Sending a draft counts as approving it, so that part stays with approvers. ## Approvals A launch can create an approval request, and the campaign waits until every request on it is approved. A rejection stops the launch. Three things create one: - **Gifts.** Any campaign that sends a gift costing more than $2.50 needs an approver. - **A large gift launch.** The campaign's gifts total more than $1,000, or more than the requesting member's monthly gift budget. - **An event-triggered campaign.** A campaign that enrolls people on its own needs an approver to activate it. The thresholds count gift dollars, not credits, so a campaign of printed or handwritten mail alone creates none of these. Each request carries the amount it is about, so the approver decides about one campaign rather than granting a general permission. Nobody can approve their own large gift launch; another approver or admin has to. In a workspace where nobody else can approve, the launch itself counts. When the person launching can approve, the gift and event-triggered requests are recorded as approved at launch, with the note "Approved by launching". Designs and drafts do not go through this queue. A person with an approver role or above approves them directly, and the campaign's copy approval setting decides whether every draft waits for that review. Approval emails go to admins by default, and to the owner in a one-person workspace. An approver receives them after turning on approval emails in their notification settings. Agent request emails are a separate setting: a person gets one when an agent they connected asks for their approval, and it is on for everyone until they turn it off. Approving in bulk is itself a consequential action when an agent asks for it while the campaign can still print, and gets a confirmation card with counts and cost. Ask before drafting steps, on the Team and approvals tab, decides whether an agent needs a click to import contacts, generate an image, polish copy, or rewrite waiting drafts. It is on by default, and only an owner or admin can change it. Their agent can turn it back on, but turning it off waits for their click. Ask before approvals, beside it, decides whether a connected agent needs a click to approve drafts and designs that would print. It is also on by default, and only an owner or admin can change it, in Settings. No agent can. The assistant in the app always asks. Sending, launching, cancelling and suppression changes wait for a person whatever either switch says. ## 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 for anything that prints, sends, approves or launches. --- Sincerely is personalized direct mail and gifting for B2B revenue teams: postcards, letters, handwritten mail, and gifts, each written for one recipient. Contact Sincerely: https://trysincerely.com/contact Agent routing index: https://trysincerely.com/llms.txt Listings: https://www.g2.com/products/sincerely and https://www.producthunt.com/products/sincerely