Deactivate user in Box
Automatically deactivate a departing Box user from a Slack request with Stepwork. Access ends in the admin console while owned content is retained.
- Use case
- Employee offboardingIT
- Best for
- IT Administrator
- Applications used
Box
Slack
- Business outcome
- Risk reduction
The problem
They left. Their Box login still works.
Box offboarding often sits outside the standard checklist. Departed employees keep signing in until someone opens the admin console by hand.
Content is still there, but so is access. The gap shows up when a folder opens for someone who should already be gone.
The outcome
Box access ends. Files stay put.
Stepwork deactivates the user in the Box admin console so sign-in stops while content remains. The run records who asked. When owned folders still need a new owner, use Transfer content ownership in Box.
- The user is deactivated in Box admin.
- Content access for that account ends.
- If the user cannot be found, the run stops.
The process
From Slack request to a deactivated Box user
IT posts the departing user’s email in Slack. Stepwork deactivates them in Box admin.
- Step 1
Request it in Slack
A teammate posts the departing employee’s work email. That message starts the flow, and Stepwork records who asked and when.
- Step 2
Find the user
Stepwork signs in to the Box admin console and locates the user. If nobody matches, the run stops.
- Step 3
Deactivate the account
Stepwork deactivates the user, the same change an admin makes by hand, so access ends while content is retained.
- Step 4
Confirm and reply in Slack
Stepwork checks that the account is deactivated, then posts the result back in Slack.
Why Stepwork
Box offboarding stays on the path you recorded
A deterministic agent runs the deactivate path you recorded. Content access does not linger waiting on a late admin cleanup.
Similar use cases
Similar use cases
Suspend member in DropboxSuspends a departing member in the Dropbox admin console, blocking access while preserving files.
FAQ