HR & RECRUITING

Route New-Hire Access Requests to IT by Department

On a new HRIS record, this decides which systems and groups the hire needs from their department and seniority.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerevent
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew employee row inserted in HRIS tablePostgreSQLPostgres
  • LogicMap department and seniority to least-privilege access profile
  • ActionOpen Linear access-provisioning issue with per-grant checklistLinearLinear
  • OutputEmail the hiring manager the issue link for approvalGmailGmail

What it does

Reads a new employee record and produces a precise access request for IT. Instead of a vague "set up the new person" ticket, it expands the hire's department and level into the concrete list of SaaS apps, repo access, mailing lists, and security groups they should receive, then files a single structured Linear issue with that list as a checklist.

When to use it

Use it when access creep and inconsistent grants are a problem and you want least-privilege provisioning driven by role rather than by whoever sets up the account. Good for teams that already run IT work through Linear.

How it works

  1. 1A new row in the HRIS table (Postgres) triggers the flow with department, title, and manager.
  2. 2A logic step maps department plus seniority to an access profile — the apps, groups, and repos that role gets by default.
  3. 3It builds a Linear issue titled for the hire, with each grant as a checkbox sub-item and the manager named as approver.
  4. 4The issue is assigned to the IT provisioning team with a due date before the start date.
  5. 5A confirmation with the issue URL is sent to the hiring manager for sign-off.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  3. 3
    Connect GmailRead, draft, send, label.
  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.