Stepwork logoStepwork logo
How it works

Procedures

  • OverviewHow a Procedure runs the whole process
  • Extractions deep diveRead tables and documents, use them anywhere
Deterministic AgentsMarketplace

By department

  • ITAccounts, access, helpdesk requests
  • Security & ComplianceAccess reviews, evidence, audits
  • Finance & AccountingInvoices, billing, month-end close
  • Sales & RevOpsCRM to ERP, orders, quotes
  • OperationsOrders, deliveries, dispatch
  • HR & PeopleOnboarding and offboarding
See every use case

By industry

  • HealthcareReferrals, eligibility checks, EHR entry
  • 3PL and warehousingPDF orders, WMS entry, client billing
  • Freight and truckingRate confirmations, carrier checks, TMS
  • Fuel and convenience storesStore staff, POS IDs, back office
  • ConstructionJob setup, subcontractor insurance
  • Manufacturing and distributionPO entry, supplier dates, legacy ERPs
  • Accounting firmsMonth-end across every client file
  • Field services and tradesService calls to jobs to invoices
  • MSPsNew users and license true-ups
See every industry
Security
Log inBook a Demo
How it works

Procedures

  • OverviewHow a Procedure runs the whole process
  • Extractions deep diveRead tables and documents, use them anywhere
Deterministic AgentsMarketplace

By department

  • ITAccounts, access, helpdesk requests
  • Security & ComplianceAccess reviews, evidence, audits
  • Finance & AccountingInvoices, billing, month-end close
  • Sales & RevOpsCRM to ERP, orders, quotes
  • OperationsOrders, deliveries, dispatch
  • HR & PeopleOnboarding and offboarding
See every use case

By industry

  • HealthcareReferrals, eligibility checks, EHR entry
  • 3PL and warehousingPDF orders, WMS entry, client billing
  • Freight and truckingRate confirmations, carrier checks, TMS
  • Fuel and convenience storesStore staff, POS IDs, back office
  • ConstructionJob setup, subcontractor insurance
  • Manufacturing and distributionPO entry, supplier dates, legacy ERPs
  • Accounting firmsMonth-end across every client file
  • Field services and tradesService calls to jobs to invoices
  • MSPsNew users and license true-ups
See every industry
Security
Log inBook a Demo
  1. Home
  2. Marketplace
  3. Remove external collaborator in Box

Remove external collaborator in Box

Automatically remove an external Box collaborator from a Slack request with Stepwork, and confirm their folder access has ended.

Shaun MacLellanFounder

Book a DemoSee the process
Use case
Security response & remediationInfoSec & Compliance
Best for
Security Analyst
Applications used
  • Box
  • Slack
Business outcome
Risk reduction

On this page

  1. The problem
  2. The outcome
  3. The process
  4. Why Stepwork
  5. Similar use cases
  6. FAQ
InfoSec & Compliance
  • Box

Remove Box collaborator

One Slack request. Outside access ends on the folders.

Book a Demo

The problem

Outside access waits on folder owners.

When an external collaborator should lose access, security chases folder owners one by one. Some folders get updated; others stay open for days.

The invite is still live while the ticket sits. Exposure depends on who responds first, not on a single confirmed removal.

The outcome

External access ends on request

Stepwork removes the specified external collaborator from folders and confirms access ended. The response is logged without chasing owners. For a departing employee’s own login, use Deactivate user in Box.

Deactivate user in Box
  • The external collaborator is removed from folders.
  • Access for that collaborator ends.
  • If the collaborator cannot be found, the run stops.

The process

From Slack request to a removed Box collaborator

Security posts the collaborator in Slack. Stepwork removes them from folders and confirms access ended.

  1. Step 1

    Request it in Slack

    A teammate posts the external collaborator’s email and the folders in scope. That message starts the flow, and Stepwork records who asked and when.

  2. Step 2

    Find the collaborator

    Stepwork signs in to Box and locates the external collaborator on the named folders. If they cannot be found, the run stops.

  3. Step 3

    Remove access

    Stepwork removes the collaborator from those folders, the same change an admin makes when closing outside access.

  4. Step 4

    Confirm and reply in Slack

    Stepwork checks that access ended, then posts the result back in Slack.

    Removed · external collaborator access ended

Removed · external collaborator access ended

Why Stepwork

Collaborator removal stays on the response path

A deterministic agent runs the removal you recorded. External access does not wait on whoever owns the folder that week.

Deterministic agents
Book a Demo

Similar use cases

Similar use cases

  • Deactivate user in BoxDeactivates a departing user in the Box admin console, blocking access while retaining content.Learn more
  • Revoke shared link in DropboxRevokes a specified shared link and confirms it no longer resolves.Learn more
  • Disable public board link in MiroTurns off the public link for a specified board and confirms it is dead.Learn more

FAQ

Common questions

  • Post their email and the folders in scope in Slack. Stepwork removes them and confirms access ended.
  • No. Deactivating a Box user is a separate offboarding flow for employees, not external collaborators.
    Deactivate user in Box
  • Stepwork confirms access is already gone and replies with that status. It does not fail the run for an already-closed invite.

See it run on a process you already repeat

Bring one. We will show you what it looks like as a flow and what each run records.

Book a Demo
Stepwork

Deterministic agents for work that must run the same way every time.

ProcedureExtractionsContainersDeterministic AgentsMarketplaceUse CasesIndustriesSecurityClaude Co-Work AlternativeStepwork MCPAngelList Case StudyFAQ
Terms and ConditionsPrivacy PolicyData Processing AgreementSubprocessors

2261 Market Street #4481, San Francisco, CA 94114, USA

Loot Discount inc dba Stepwork

© 2026 Stepwork. All rights reserved.