Move a member to a permission group
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /reference/permission-groups/v1-group-change-user-group.md. Index of every page and the rules for every call: /llms.txt. Guides and concepts in one file: /llms-full.txt. OpenAPI: /openapi.json.
PATCH/
Puts a team member in this permission group, taking them out of their current one, and returns the member with their group.
The path id is the group; user_id is the member. The new permissions apply at once.
Business rules
user_idmust be a member of this team.
Side effects
- The member's permissions change at once.
- Tells the team's open web app sessions about the change.
Path parameters
Your team slug, shown as Team ID next to your API key in Profile.
- Example
your-team
- Example
The permission group's
id: a hash id from an earlier answer. Only hash ids work here; anything else answers 404page_not_found.- Example
aaNZmyj0mvmWLU
- Example
Request body
application/json, required.
The member's id, from List team members.
Response
200Successful response.
Child fields (8)
The member's permission group.
avatar_urlstring | nulllast_login_atstring (date-time) | nulltimezonestring | null
Errors
401The API key is missing or wrong (
unauthenticated).- When
- The API key is missing or wrong.
- Fix
- Send your personal API key as
Authorization: Bearer YOUR_API_KEY.
403You are not allowed to do this.
api_access_not_in_plan: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only{"message": "Insufficient Permission"}. Other refusals use the error envelope, withunauthorizedoruser_is_not_authorized.- When
- Your permission group lacks Manage Settings. This 403 has a short body,
{"message": "Insufficient Permission"}, withoutsuccessorerror. - Fix
- Ask the team owner to give your permission group Manage Settings.
404Not found.
page_not_found: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's.code: null, with a message that starts "No query results for": there is no record with that id.- When
- No such group, or
user_idis not a member of this team. - Fix
- Use ids from List permission groups and List team members.
422The request was refused and changed nothing.
validation_failedlists what to fix inerror.fields; other codes name a business rule, explained inerror.message. A few checks answer with only{"message": "..."}. An operation that calls another service (a payment provider, a carrier, an accounting app) can answerconnect_timeout("Please retry again") when that service does not answer in time: the change may or may not have happened there, so read the record back before you retry.- When
user_idis missing or is not a hash id.error.codeisvalidation_failed, anderror.fieldsnames each field with its messages.- Fix
- Fix the fields listed in
error.fieldsand send the request again.
Related
- GETList permission groups
/v1/ api/ store/ {team_slug}/ setting/ group - GETList team members
/v1/ api/ store/ {team_slug}/ setting/ user
