IT OPS

Department-Based Access Group Assignment

On a scheduled run, finds newly approved hires and assigns them to the correct access groups and distribution lists for their department.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily scheduled run
  • ActionQuery approved hires without group assignmentPostgreSQLPostgres
  • LogicMatch department to access groups, flag missing fields
  • ActionAdd users to Teams groups and distribution listsMicrosoft Teams
  • ActionWrite membership changes to audit tablePostgreSQLPostgres
  • OutputSend assignment summary to IT operations channelSlack

What it does

Keeps access-group membership in sync with your roster. Each run, it pulls hires marked approved-but-not-yet-grouped, matches their department to a predefined set of security groups and email distribution lists, applies the memberships, and writes an audit record so you can prove who got what and when.

When to use it

Use this when access groups (not individual app accounts) are how you gate permissions, and you need a clean audit trail for compliance reviews. Ideal for organizations where department determines the bulk of someone's access footprint.

How it works

  1. 1A daily schedule kicks off the run.
  2. 2The flow queries Postgres for hires in `approved` state without group assignment.
  3. 3For each hire, it looks up the department-to-group mapping.
  4. 4A filter skips anyone missing a required department field and flags them for review.
  5. 5It adds the user to the matching Microsoft Teams groups and distribution lists.
  6. 6It writes each membership change to an audit table in Postgres.
  7. 7It sends a summary of assignments and skipped records to the IT operations channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect Microsoft TeamsChannels, chats, files.
  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.