HR Integrations

A read-only register of your people, synced from an external HR system, so the compliance team can see who works here and tie each person to training, access reviews and reporting.

People are a common source of audit findings: joiners given access before a check is finished, movers who keep access they no longer need, leavers whose accounts outlive their departure. This page gives the compliance function one list of personnel, drawn from your HRIS (the human-resources information system that already holds your staff records — payroll, contracts, joiners and leavers), for use in access reviews, security-awareness tracking and compliance reporting.

This is a sync, not an HR system

Aegis does not manage payroll, contracts or leave, and you cannot add or edit a person by hand here. Records arrive by sync from a registered HR provider and are shown read-only. If no provider has been registered, the page is empty and tells you so — that is the normal starting state, not a fault.

Who uses it

Every role can open /hr, including Viewer: the page is read-only, so it is gated on the permission to read HR records rather than on a minimum role, and the HR entry appears in the left menu for all four roles. A Viewer, Contributor, Manager or Admin can read the counters, filter the synced list by status and read each row — but nobody can edit a record, because the data belongs to the provider.

Registering that provider, authoring offboarding templates and setting the privacy switches are separate jobs on Settings → HR Integrations (/settings/hr), which requires Manager or Admin. Those two roles also see a Manage HR connections button in the header of /hr that takes them there; a Contributor or Viewer does not, which is why it is absent from the screenshot below (captured as a Contributor). Triggering a sync run needs the connector-update permission, which a Manager and an Admin hold; they start it with the Sync now button on the connection, as described further down.

The module must be licensed before the page appears

HR Integrations is gated by HR_INTEGRATIONS. If your plan does not include it, the page shows a short message — "HR integrations are not available on your current plan" — instead of the table, and the sidebar entry may be hidden.

What's on this screen

The page opens with the heading HR Integrations and the line "Manage employee data and HR system integrations." There is no New button in the header — nothing is created here. For a Manager or Admin, the right of the header carries Manage HR connections.

Below the heading sit four counter cards across the width of the page: Total Employees, Active, On Leave and Terminated. The last three are coloured green, amber and red. On the captured screen they read 28, 22, 3 and 3 for the fictional demo company. The counters refresh every time the table reloads, so they stay current after a sync, but they always count everyone — a status filter narrows the table, not the cards. Under the cards is a short filter bar — a Search employees… box, a Search button beside it, and an All Statuses dropdown.

The rest of the page is the employee table, sorted by name and twenty rows to a page with paging beneath. With the default privacy settings it carries six columns: Name, Department, Job Title, Status (a coloured badge), Provider and Last Synced, the date of the sync run that last wrote the row. A seventh column, Email, sits after Name only when Show personal email is turned on in the privacy settings — it is off by default, which is why the captured screen has no email column. Rows are read-only; there is no row menu and no detail page behind them.

  1. The ? button in the top bar opens the help panel: it slides in from the right over the page with help topics for the screen you are on, and a search.
  2. The book icon beside it opens the in-app User Guide at this chapter, in place of the page.
  3. The filter bar sits directly under the counter cards, starting with Search employees…. Of its three controls, only the All Statuses dropdown narrows the table — typing a name and selecting Search leaves the rows as they were.
  4. In the left menu, HR sits in the Administration group, alongside entries such as Workflows and Settings (and, for a Manager or Admin, Connectors). Expand that group to come back here.
The HR Integrations page after a sync, with the four counters above the employee table — /hr.
The HR Integrations page after a sync, with the four counters above the employee table — /hr.

When nothing has synced yet

Before any provider is registered, or before the first sync has run, all four counters read 0 and a guidance panel stands in for the table. It shows a building icon, the heading No employees synced, and the note that connecting an HR provider feeds access reviews, security-awareness tracking and compliance reporting.

Registering an HR provider

Nothing appears on /hr until a connection exists. This is a Manager or Admin task, done once.

  1. Open Settings → HR Integrations — from the Manage HR connections button on /hr, the Add HR connection button in the empty state, or the Settings menu. The page carries the breadcrumb Settings / HR Integrations and three stacked panels. The first is HR connections — "Register an HRIS provider so Aegis can sync your employee directory." Until you add one it reads No HR connections yet.
  2. Select Add connection. A short form opens in place with four fields: Provider, Subdomain, API key and Display name (optional).
  3. Choose the provider — BambooHR is the only one supported today, and the single entry in the dropdown. Enter your company slug in Subdomain (the part that appears in your provider's URL) and paste the API key the provider issued you. Provider, subdomain and API key are all required; the form says so if one is missing.
  4. Select Save. Aegis confirms with "HR connection registered" and lists the connection. The API key is encrypted before storage and is never shown back to you. A second connection for the same provider and subdomain is refused.
Registering a connection does not fetch anybody

Registering the connection stores the credentials only. The employee sync is an on-demand background job with no scheduled run: select Sync now on the connection's row to start it. Aegis confirms with "Employee sync started", or tells you a sync is already queued for that connection. Then reopen /hr: the four counters moving off 0 and a fresh date in Last Synced are the visible signs that the run landed.

Changing or removing a connection

Each row in the HR connections panel carries three buttons for a Manager or Admin.

Reading the synced list

Once the first sync has run, the counters fill in and the table lists each person, as in the screenshot above.

  1. Start with the All Statuses dropdown rather than the search box: a name typed into Search employees… followed by Search returns the same rows as before.
  2. Open the All Statuses dropdown and pick Active, On Leave or Terminated. The table narrows to that lifecycle state and the count beneath it updates. The four counters above stay at their full totals — they count everyone, not the filtered view.
  3. Read across a row: the person, their department and job title, the coloured Status badge and the Provider the record came from. Where the source system holds no department or job title, the cell shows an em dash.
  4. Check Last Synced before you rely on the list. It shows the date of the run that last wrote each row; between runs the list can be missing recent joiners and still showing recent leavers as active. If the date is old, ask for a fresh sync before you use the list for an access review or a training population.
Status Badge colour What it means
Active Green A current employee or engagement.
On Leave Amber Temporarily away — parental leave, long-term sickness, a sabbatical.
Terminated Red The person has left. The record stays in the list until the retention window set in the privacy settings has passed.

These three values are the whole vocabulary — there are no custom statuses, and a record whose status is anything else is shown as Active.

Privacy settings

The third panel on Settings → HR Integrations is Privacy & data retention — "Control how HR personal data is displayed and retained." It holds Retain terminated-employee records (days) plus four switches: Show personal email, Show department, Show job title and Anonymize records on offboarding. Change them and select Save; Aegis confirms with "Privacy settings saved". Until someone saves, Aegis uses conservative defaults: personal email hidden, department and job title shown, terminated records kept for 365 days, and anonymisation off.

These settings take effect on /hr and on the stored data:

What happens when someone leaves

When a sync run sees a person move to Terminated who was not terminated before, Aegis starts its offboarding handling on its own. The Offboarding templates panel — "Reusable offboarding checklist templates." — on Settings → HR Integrations decides the checklist that goes with it.

  1. Author a template: select New Template and a form opens with Name, an optional Description, a Steps box that takes one step per line, and an Active (applied on offboarding) tick box. Select Create and Aegis confirms "Template created", listing it with its step count, an Active or Inactive marker, and Edit and Delete beside it. Only active templates are used.
  2. When the sync detects the departure, Aegis fires the HR-offboarding trigger, so any workflow built on it runs — even for a leaver with no email address.
  3. If the leaver has an email address and your plan includes GDPR automation, Aegis opens an erasure DSR (data subject request) in PENDING on the GDPR screen, with the steps of every active offboarding template embedded as its checklist. It does not open a second one while an erasure request for the same person is still in progress.
  4. Where AI is enabled for your organisation, Aegis also queues a data-subject lookup across your connected systems to show where that person's data sits.
  5. If Anonymize records on offboarding is on, the HR record is anonymised as described above, and the name and email copied into required-reader history are blanked too.
The erasure request still goes through people

Apart from the opt-in anonymisation, nothing is deleted at this point. The erasure DSR follows your normal review and approval flow on the GDPR screen, and a person works through the checklist and decides what is erased. Access removal in your other systems remains a task for your existing process.

Tips and limits

Where this connects

The synced list feeds several other parts of Aegis:

Other inbound integrations are set up in Connectors, and the three panels above live under Settings. Changes to the connection and the privacy settings are written to the Audit log, the menu group holding this page is covered in The left menu, an end-to-end walk through a joiner and a leaver is in the HR scenario, and access is set out in What each role can do.