Skip to content

People directory

One employee record for people, systems, and AI agents

Configure employee data, organization structure, and group membership once, then use that record across payroll, performance, documents, and your AI agents.

Request early access

The people directory is shown in list view, with columns for employee name, job title, reporting manager (manager avatar and name), and group membership (member-avatar stacks and group names). The header includes search, a primary "New hire" action, and tabs for List, Org chart, and Grid.

Maya Bennett

London, UK · Senior Engineer · L5

Positions

L5 · Senior Engineer

Apr 1, 2025 to present

L4 · Engineer II

Mar 16, 2024 to Mar 31, 2025

Compensation Visible to you

£85,000 base

Raise takes effect Apr 1, 2025

Documents
Employment contract (UK) Probation record

A detailed employee profile for Maya Bennett, a Senior Engineer at L5 in London. The profile shows team, employment type, location, and Active status; a positions timeline retaining her current role and previous Engineer II role for tenure history; a compensation timeline with base salary and a lock icon for field-level permissions; and documents for her UK employment contract and probation record, plus an add-document control.

Configurable employee records

Capture what you need; show each role only what it should see

Create the fields your team needs without waiting for a vendor release.

Create your own typed fields — strings, dates, enums, lookups, and references — without waiting for a vendor release.

Record promotions, transfers, raises, and bonuses with effective dates and a complete changelog, keeping tenure, reporting lines, and compensation history queryable at any point.

Set field-level permissions by role and group so compensation and sensitive PII appear only where appropriate; every search and lookup follows those rules.

Directory capabilities included

Org chart, groups, search, and audit in one place

An org chart for real structures

Model reporting lines, dotted lines, secondary connections, and matrix structures from the same employee record — without a second tool or source of truth.

Employee groups that fit

Organize the company by team, location, jurisdiction, or function, then use those groups to drive time-off policies, document templates, and review cycles.

Every directory change, recorded

Capture every edit, permission change, and group reassignment in the activity log.

Alex Morgan

Co-founder & CEO

Ryan Foster

Engineering Manager

Nina Patel

People Ops

Maya Bennett

Senior Engineer

Reports to Reports to Collaborates Coached by

A four-person org chart arranged in a diamond. Alex Morgan (Co-founder & CEO) is at the top center, linked by a solid "reports to" line down-left to Ryan Foster (Engineering Manager) at middle-left, then linked by a solid "reports to" line down-right to Maya Bennett (Senior Engineer) at bottom center. Nina Patel (People Ops) is at middle-right, connected by dashed lines to Alex ("collaborates") and to Maya ("coached by"), showing dotted-line and secondary relationships beside the primary reporting chain.

Operational outcomes

From scattered to dependable

P / 1

Keep sensitive employee data away from the wrong people.

Gate compensation, home addresses, performance notes, and every sensitive custom field by role, group, and field. A manager can see their team's salaries while other teams see nothing. Access stays open where appropriate and restricted where required, without shadow spreadsheets for sensitive data.

P / 2

Start every payroll cycle with a complete change history.

Record pay raises, role moves, working-pattern changes, and bonuses with effective dates as they happen. Each payroll cycle exports a time-bounded changelog in your provider's format, carrying retroactive adjustments, prorations, and pay-element changes through without manual reconciliation or last-minute Slack threads.

P / 3

Plan and enact reorgs from the same live employee records.

Model a new structure against live records, share it only with the people who should see it, and enact it on an effective date. Reporting lines, group memberships, and their permissions update together, leaving nothing connected to the old organization after the announcement.

Directory stack comparison

Current setup vs. Locaxion

Typical setup Locaxion
Employee system of record Headcount sits in a spreadsheet, the org chart in another tool, and every other field in a separate database. Maintain one employee record that every connected system can read.
Field configuration Use only the fields the vendor chose to provide. Create typed fields yourself — including dates, numbers, and links — without waiting for a vendor release.
Organization structure Manually redraw the org chart in Lucid after each reorg; it is out of date within a week. Update the org chart automatically whenever reporting lines change.
Protected employee data Expose salaries to everyone who can open the directory. Restrict individual fields such as pay and home address according to role.
Career and pay history Keep promotions and raises in someone's memory until the next compensation review. Record each promotion, raise, and transfer with its effective date.
Directory search Look up a person, their team, and their manager across three separate tools. Search people, teams, roles, and locations together while honoring every viewer's permissions.

Connected by default

Explore connected workflows

  • Time-off and attendance

    Time-off and attendance

    Handle Slack-based requests and regional policies, then produce pre-payroll reports your provider can ingest.

  • Documents and eSignatures

    Documents and eSignatures

    Generate contracts from templates, sign them in Locaxion, and file them on the employee record.

  • Performance

    Performance

    Launch review cycles automatically and draft them from signals your team already creates.