Managing employees, managers, and teams

Perslace represents workforce structure across All Employees, Branches, User Groups, and Org Chart. Review these surfaces together before changing membership or manager relationships.

Who can use this guide

Primary Admins and Administrators can use this guide to validate organisation structure. Finance users and Managers may have read access, but their exact permissions were not verified.

Purpose

Use this guide to review employee records, group and branch membership, and manager-reportee relationships without making unverified production changes.

Prerequisites

An approved organisation-structure list
Safe employee identifiers for comparison
The intended branch, group, and manager for each test employee
Awareness of any group, branch, individual, or team-based scheme assignments
Authority to request or approve structure changes

Review employees, managers, and teams

Open Employees and select All Employees.
For each relevant test record, review the available employee ID, group, scheme, manager, branch, role, and status.
Open Branches and confirm that each test employee appears in the intended business or geographic unit.
Open User Groups and confirm the memberships used for commission-scheme assignment.
Open Org Chart and review each manager’s reportees and the visible reporting hierarchy.
Compare All Employees, Branches, User Groups, and Org Chart. Record any mismatch using safe employee IDs rather than names or email addresses.
Before requesting a membership or manager change, review the employee’s current scheme assignments, effective dates, targets, and manager team-rollup dependencies.
Make changes only after the relevant create, edit, or reassignment workflow and its downstream effects have been verified in the test organisation. Those procedures were not fully exercised during product review.
Recheck all four employee surfaces and any affected scheme or target after an authorised test change.

Expected result

Each reviewed employee has a consistent branch, group, manager relationship, role, and status, and any assignment or target dependencies are understood before a change is approved.

Important notes

Warning: Group, branch, or manager changes may affect scheme eligibility, reporting, and team-rollup targets. Do not make a production change until its effective-date and recalculation impact is understood.

An employee record, a login account, and an access role are separate concepts. Do not assume that changing one automatically changes the others.
Groups are used for commission-scheme assignment; branches can also be assignment targets.
Offboarding, record retention, manager reassignment, deletion, and recovery behaviour remain unverified.
Use synthetic people in screenshots and tests. Never expose personal email addresses, employee IDs, or financial values.

Troubleshooting

An employee is in the directory but not in the organisation chart

Review the employee’s manager relationship and status. Preserve the existing record and ask an authorised Administrator to investigate rather than creating a duplicate.

An employee has no expected scheme

Check whether the scheme is assigned by group, branch, or individual. Confirm the employee’s current membership and the assignment’s effective dates.

A manager’s team total is unexpected

Confirm the reportee list, target type, review period, Metric Definition, and source-data freshness. Do not change the hierarchy solely to alter a calculated total.

Two records appear to represent the same person

Do not merge, deactivate, or delete either record until account ownership, historical calculations, audit evidence, and retention behaviour have been verified.

Last updated: August 2026