corestack_ team_ member_ update
Edit a team member.
When to use it
Change a team member's name, position, role or notification preferences, or ask them to change their sign-in email
address. Anything you leave out stays as it is. A new role replaces only the role you may give; other roles they hold
stay. This is the Control Panel's user edit and POST /api/user/{id}/update.
Only the member can change their own sign-in email address, on their Profile page, where the new address is confirmed
before it is used. A new email for somebody else is never saved: the member is emailed at the address they have now,
saying who asked and for which address (with no link), and the rest of the call still saves. The result's email_change
says so, with the words the Control Panel and the API use; it is null when the call asked nothing of the member. Nothing
is sent to the new address, and the answer does not say whether that address is already in use. Repeating the same call
within an hour answers the same and sends nothing more; a different address is a new notice, so the tool is not
idempotent. If that email cannot be sent, email_change says so (notice_not_sent) and the call does not count
towards the limit below, so you can try again later.
Somebody who was invited and has not accepted yet has no Profile page: a new email for them is refused. To invite them
at another address, remove them with corestack_team_member_remove (that cancels the invitation, and its link stops
working), then invite them again at the right address with corestack_team_member_invite.
Corefinity staff cannot use this tool. They change a customer's address from the Control Panel or the API, and the old address is always told.
An agent never raises the permissions of the person it acts for: changing that person's own role to one that would give
them a permission or an owner role they do not hold now is refused own_permissions_upward (the person can make that
change in the Control Panel). Lowering their own access follows the Control Panel's rules.
Making anybody an owner, the person you act for included, is for an owner of the company (or Corefinity staff): a
person who only holds the edit users permission is refused owner_grant, here as in the Control Panel and the API.
Any other role is given only by someone who holds every permission it carries (for a standard role, an owner of the
company or Corefinity staff are exempt; a custom role binds everyone): a Member (Full Access) cannot give anybody, themself included, the Accounts & Billing role, and is
refused permission_grant, here as in the Control Panel and the API.
Ask for it
Using the Corefinity MCP server, call corestack_team_member_update with user_id 1042, position Lead developer, notifications {"subscribe_to_newsletters":false}. (Edit a team member.) Tell me what it returned.Inputs
A well-formed address. For another member it is never saved: they are emailed that you asked (see above). The address of the person you act for is never changed here either: they change it on their Profile page, where the new address is confirmed first. Up to 254 characters.
Up to 255 characters.
Any of email_notifications, alerts_notifications, maintenance_window_notifications, subscribe_to_deployment_alerts, subscribe_to_newsletters, each true or false. subscribe_to_newsletters is product news, which is the member's own consent: you may switch it off for them, never on (CPPB-2112).
Fields
Up to 255 characters.
A role's slug you may give them. Up to 255 characters.
The team member's id (corestack_team_members_list). At least 1.
Example call
{
"name": "corestack_team_member_update",
"arguments": {
"user_id": 1042,
"position": "Lead developer",
"notifications": {
"subscribe_to_newsletters": false
}
}
}If it is refused
| Reason | What to do |
|---|---|
privileged_target | The account is not yours to change. Only a super administrator may change a super administrator's account. A company owner's name, email, position and roles are changed only by themself, another owner of the same company or Corefinity staff, and the company's primary user's only by themself or staff. |
forbidden | You may not edit people (an owner, or the edit users permission, may). |
owner_grant | Only an owner of the company, or Corefinity staff, may make someone an owner (agency-owner or client-owner); holding the edit users or invite users permission is not enough. Message: "Only an owner or Corefinity staff can make someone an owner." |
permission_grant | The role carries a permission you do not hold (a custom role always; a standard role unless you are an owner of the company or Corefinity staff). Message: "You can only give someone a role if you hold all of its permissions yourself." |
last_owner | The change would leave the company without an owner. |
own_permissions_upward | The change would give the person you act for more access; ask them to make it in the Control Panel. |
invalid_arguments | On email, role or a preference, with the Control Panel's message. subscribe_to_newsletters set to true for another member is refused on that field, and only that field: "Only {name} can sign up for newsletters. You can turn them off for a team member." Switch it off for them, or ask them to switch it on themselves. A new email for the person you act for is refused on email: "Change your own email address on your Profile page, where the new address is confirmed before it is used." Asking the same member for a new address more than 3 times in an hour or 6 in a day is refused on email, and nothing from the call is saved: "You have asked this member to change their email address too many times. Try again later." A new email for somebody invited who has not accepted is refused on email, nothing from the call is saved and nobody is emailed: "They have not accepted their invitation yet, so its address cannot be changed. Remove them from the team to cancel the invitation, then invite them again at the right address." |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |
Result
The member as corestack_team_member_get answers them, and email_change: null, or, when the call named a new address
for another member,
{
"status": "member_asked",
"requested_email": "[email protected]",
"message": "Only the member can change their sign-in email address, on their Profile page. We have emailed them to say you asked."
}or, when that email could not be sent (the rest of the call still saved, and nothing about the address was written),
{
"status": "notice_not_sent",
"requested_email": "[email protected]",
"message": "Only the member can change their sign-in email address, on their Profile page. We could not email them to say you asked, so try again later."
}The member's email in the result is still their current address.