shops.setSendPermissions

Owner only, not an agent: turn sending quotes, invoices or visit recaps on or off for one role (office, lead or field). Give only the switches to change. The owner always can send and cannot be turned off. Office covers any job, a lead covers jobs on their crew, and a field worker covers jobs assigned to them. Turning a switch off stops that role, including their agent. A new shop starts with every switch on.


Who	A person's own sign-in only (agent tokens are refused)
REST	`POST /v1/shops/send-permissions`
MCP tool	Not an MCP tool
Writes	yes, send an Idempotency-Key
Area	Shop

When to use it

Owner only, not an agent: turn sending quotes, invoices or visit recaps on or off for one role (office, lead or field). Give only the switches to change.

What to tell the owner

Ask the person to do this with their own sign-in. Your agent token is refused here.

Input

Field	Type	Required
`shop_id`	string (uuid)	yes
`role`	string (one of office, lead, field)	yes
`send_quotes`	boolean	no
`send_invoices`	boolean	no
`send_recaps`	boolean	no

Example

POST https://doingwork.work/v1/shops/send-permissions
content-type: application/json
Idempotency-Key: 3f1c...

{
  "shop_id": "00000000-0000-4000-8000-000000000000",
  "role": "office"
}

Output

JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are {code, message, status}.

Errors

Code	Status	What to do
`invalid_input`, `invalid_token`, `rate_limited`		Can happen on any call. See errors.