IT OPS

Catch seats assigned to deactivated or departed users

Compares active SSO directory membership against held SaaS seats and flags any seat still assigned to a disabled, suspended, or offboarded identity.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled access-review run
  • ActionList seat holders across SaaS appsCustom MCP server
  • ActionFetch current SSO directory status per userCustom MCP server
  • LogicKeep seats held by disabled or offboarded users
  • ActionOpen urgent Asana reclaim task per orphaned seatAsanaAsana
  • OutputSend urgent Slack alert to IT channelSlack

What it does

This workflow finds the most wasteful and risky seats: licenses still attached to people who no longer have an active identity. It reconciles each SaaS app's seat list against current SSO directory status and surfaces any seat held by a disabled, suspended, or fully offboarded user, treating those as urgent reclaims.

When to use it

Run it when offboarding hygiene is shaky and ex-employees or deactivated contractors may still consume paid seats, or worse, retain access. It is both a cost control and a security-adjacent access-review tool.

How it works

  1. 1A scheduled run begins the check.
  2. 2A custom MCP call lists seat holders across connected SaaS apps.
  3. 3A second custom MCP call retrieves each identity's current SSO directory status.
  4. 4A logic step keeps only seats where the user is disabled, suspended, or offboarded.
  5. 5An action opens an urgent-priority Asana reclaim task for each match.
  6. 6The output sends an immediate Slack alert to the IT channel listing the orphaned seats and affected apps.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Custom MCP serverConnect any MCP-compatible tool you own.
  2. 2
    Connect AsanaTasks, projects, milestones — everywhere.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.