Change responsibilities or remove a company member

Coordinate handover, role changes, and access review when someone’s job changes.

Review a person’s access when they move departments, change responsibility, or leave the company. Use their member record in Team and confirm the active organization before making changes.

Prepare the handover

Identify active tasks, projects, recurring work, and connected services that depend on the person. Agree on replacement owners and record the handover in the relevant work. Reassignment must follow the project’s permissions and assignment policy.

For company integrations, check which provider account or credential is being used. Removing a Node Cluster membership is not a provider-account transfer and does not rotate external credentials.

Change the organization role

Select the member and choose an available role in the role selector. An Owner can choose privileged roles; an Admin’s selector offers Member and Viewer changes. The interface prevents changing your own role and protects the last Owner from demotion.

Review scopes after changing the role. The role-change flow resets scoped permissions to the defaults for the new role. Do not assume tailored Operations scopes or the prior Space-access mode remain unchanged. Check the saved configuration, area access, and effective resource results after the change.

A role change is not a substitute for a department transfer. Update the primary department and creation exceptions separately, and review old Space memberships, project grants, blocks, and shared overviews.

Remove a member who should leave

1. Finish the agreed handover and confirm who will own ongoing work.
2. In Team, open the person’s member record.
3. Use Remove from workspace when that action is available.
4. Read the confirmation, complete the removal, and check that the member no longer appears as active in the directory.
5. Review access to important resources and handle the company’s external accounts through their own administration procedures.

The member inspector does not offer the remove action for an Owner. Use an authorized Owner to establish another Owner and make the necessary role change first. You cannot remove yourself through this control.

Know what removal covers

The action removes membership in the selected workspace. It is not an account-deletion procedure, an automatic reassignment of all tasks, or deletion of the person’s work. Do not assume that stored sharing exceptions and external credentials have all been erased.

If someone is later invited back, review their access before relying on the new invitation’s role alone. A returning colleague should be checked as carefully as someone starting a new responsibility.