Skip to main content

Deactivate a user

Tool: oppex.admin.deboardUser

Deactivates a person's account across your whole organization, in every workspace, for example when they leave the company. Their sessions end, including any assistant connections of their own. To remove someone from one workspace only, use Remove a user from a workspace.

What you provide​

InputRequiredDescription
PersonYesThe person to deactivate. The assistant finds them with List users.

Example prompts​

  • "Lando Calrissian has left the company. Deactivate their account."
  • "Offboard han.solo@rebellion.example.com."
  • "Deactivate Sam Carter, and tell me first what they're still on call for."

The assistant confirms the person with you before it deactivates them.

Who can use it​

Your roleYou can deactivate
Account OwnerAnyone except yourself
Account AdminAnyone except an Account Owner and yourself
Any other roleNo one

Limits and errors​

MessageMeaning
Linked to an escalation policyThe person is still on one or more escalation policies. The message names them.
Linked to a scheduleThe person is still on one or more schedules. The message names them.
Linked to unresolved incidentsIncidents are still assigned to the person. The message lists them.
"Global admin cannot delete owner"You are an Account Admin and the person is an Account Owner.
"User not found for this client"The person is not in your organization.
Acting on your own accountYou cannot deactivate yourself.
Clear their on-call duties first

Oppex will not deactivate someone who could still be paged or who still owns open incidents. Take them off the named escalation policies and schedules, and reassign their incidents, then try again. Ask the assistant to run A person's on-call assignments to see what is left.

FAQ

Is deactivation the same as removing someone from a workspace?

No. Deactivation applies to every workspace and ends the person's sessions. Removing someone from a workspace only affects that workspace.

What happens to the person's sessions?

They are signed out everywhere, and their own assistant connections stop working.

Why was the deactivation refused?

The person is still on an escalation policy or schedule, or has unresolved incidents. The error names each one, so you know what to change.

In this article

FAQ

Is deactivation the same as removing someone from a workspace?

No. Deactivation applies to every workspace and ends the person's sessions. Removing someone from a workspace only affects that workspace.

What happens to the person's sessions?

They are signed out everywhere, and their own assistant connections stop working.

Why was the deactivation refused?

The person is still on an escalation policy or schedule, or has unresolved incidents. The error names each one, so you know what to change.