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.
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.
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.
-
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. - The book icon beside it opens the in-app User Guide at this chapter, in place of the page.
-
The filter bar sits directly under the counter cards, starting with
Search employees…. Of its three controls, only theAll Statusesdropdown narrows the table — typing a name and selectingSearchleaves the rows as they were. -
In the left menu,
HRsits in theAdministrationgroup, alongside entries such asWorkflowsandSettings(and, for a Manager or Admin,Connectors). Expand that group to come back here.
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.
-
A Manager or
Admin also sees an
Add HR connectionbutton in the panel. It opensSettings → HR Integrations, the one screen where a connection is registered. - A Contributor or Viewer sees the panel without that button — ask a Manager or Admin to set the connection up.
-
The
Learn more about this featurelink at the foot of the panel opens the help panel on the HR article.
Registering an HR provider
Nothing appears on /hr until a connection exists. This is a
Manager or
Admin task, done once.
-
Open
Settings → HR Integrations— from theManage HR connectionsbutton on/hr, theAdd HR connectionbutton in the empty state, or the Settings menu. The page carries the breadcrumbSettings / HR Integrationsand three stacked panels. The first isHR connections— "Register an HRIS provider so Aegis can sync your employee directory." Until you add one it readsNo HR connections yet. -
Select
Add connection. A short form opens in place with four fields:Provider,Subdomain,API keyandDisplay name (optional). -
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. -
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 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.
-
Sync nowstarts an employee sync for that connection, as described above. -
Editreopens the form with the subdomain and display name filled in. TheAPI keyfield opens empty, because a stored key is never shown back: leave it blank to keep the current key, or paste a new one when the provider has rotated it. The provider cannot be changed.Saveconfirms with "HR connection updated". -
Removeasks for confirmation, then deletes the connection and its stored API key. Employees already synced stay in the HR register.
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.
-
Start with the
All Statusesdropdown rather than the search box: a name typed intoSearch employees…followed bySearchreturns the same rows as before. -
Open the
All Statusesdropdown and pickActive,On LeaveorTerminated. 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. -
Read across a row: the person, their department and job title, the coloured
Statusbadge and theProviderthe record came from. Where the source system holds no department or job title, the cell shows an em dash. -
Check
Last Syncedbefore 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:
-
Each
Show …switch that is off removes that column from the table, and the field is blanked before the records leave the server — it is not hidden only on screen. - A terminated employee whose end date lies further back than the retention window drops out of the table and the counters, and is deleted from Aegis after the next sync run. A leaver with no end date in the HR system cannot be aged and is kept.
-
Anonymize records on offboardingis applied by the offboarding process described below: the leaver's record keeps its row but its name becomesFormer employeeand the email, department and job title are cleared.
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.
-
Author a template: select
New Templateand a form opens withName, an optionalDescription, aStepsbox that takes one step per line, and anActive (applied on offboarding)tick box. SelectCreateand Aegis confirms "Template created", listing it with its step count, anActiveorInactivemarker, andEditandDeletebeside it. Only active templates are used. - 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.
-
If the leaver has an email address and your plan includes GDPR automation,
Aegis opens an erasure DSR (data subject
request) in
PENDINGon 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. - 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.
-
If
Anonymize records on offboardingis on, the HR record is anonymised as described above, and the name and email copied into required-reader history are blanked too.
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
-
There is no create, edit, import or delete control on
/hr, and no CSV import. Records change only when the sync runs, so a correction is made in the HR system and picked up on the next run. -
One control is present but incomplete today: the
Search employees…box and itsSearchbutton do not narrow the table. Filter by status instead. - Employees do not need Aegis logins. This register is separate from user accounts — most people appear here without ever signing in.
- Rows do not open. There is no per-person detail page, and so no training record, policy-acknowledgement log, background-check history or document store behind a name. Earlier planning material described those; they are not shipped. Read the page as a directory, not a personnel file.
- Leavers stay in the list for the retention window, so an auditor asking about someone who left recently can still see they were in scope. Set the window to match your own retention policy — once it passes, the record is gone from Aegis.
- BambooHR is the only provider in the dropdown today. If your HRIS is something else, raise it with your Aegis contact.
-
All four counters showing
0means either no connection or no completed sync. CheckSettings → HR Integrationsto tell the two apart.
Where this connects
The synced list feeds several other parts of Aegis:
- GDPR — a data-subject lookup searches these records by email and reports the employee record it finds, so every row is personal data you hold; offboarding opens an erasure DSR there, as described above.
- Security awareness — a training campaign can be assigned to a department, and Aegis resolves that department to people through this list, matched to Aegis accounts by email.
- Policies and Procedures — an HR department can be chosen as an audience of required readers.
- Entra ID — the leaver-access monitor compares terminated employees here with Entra ID accounts that are still enabled.
- Workflows — the HR-offboarding trigger starts a workflow when a sync detects a leaver.
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.