Change a team member's role
change_member_roleGives a team member (list_members) a new role and scope: manager (everything; with scope "all" also the team and plan), editor (writes and schedules posts, answers comments) or viewer (read only); scope "all" or workspace ids. It can hand out write access, so it first needs a manager's OK in Shager: the call answers needs_confirmation with confirm_url; after they approve, make the same call again. The owner's role never changes, a person can't change their own, and the team always keeps at least one manager with every workspace. Someone who stops being a full manager loses the API keys they created. (Not available in an unclaimed sandbox.)
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"member_id": "<member_id>",
"role": "<role>"
},
"name": "change_member_role"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| role | Yes | ||
| scope | No | "all", or the workspace ids they may open | all |
| member_id | Yes | From list_members | |
| confirmation_token | No | The confirmation_token from needs_confirmation. The call goes through only after your human approved this exact action at confirm_url. |