members.setPermissions

Owner only, not an agent: turn a worker's permissions on or off. Give only the flags to change (see_prices, see_costs, take_money, delete, manage_schedule). They narrow what the worker's role allows and apply to the worker's own agents too; they never give more than the role. A role change starts again from the defaults (all on).


Who	A person's own sign-in only (agent tokens are refused)
REST	`POST /v1/members/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 a worker's permissions on or off. Give only the flags to change (see_prices, see_costs, take_money, delete, manage_schedule).

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
`person_id`	string (uuid)	yes
`see_prices`	boolean	no
`see_costs`	boolean	no
`take_money`	boolean	no
`delete`	boolean	no
`manage_schedule`	boolean	no

Example

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

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

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.