What is in the People app - Pacten Guides
People holds everything about employing somebody — who they are, when they work, what they are paid, and how they are doing. It is broad, so it helps to know which screen answers which question before you go looking.
THE SCREENS
What each one is for
Grouped by the question you are asking.
- Home and Hub — the way in, and where company-wide memos and tasks are published.
- Directory — everybody, searchable. The screen most of your team will use.
- Organisation — departments, roles and open seats.
- Time & Leave, Roster, Attendance — when people work, when they are off, and when they actually clocked in.
- Payroll and Advances — what they are paid, and money advanced against it.
- Performance — goals, feedback and reviews.
- Intelligence — headcount and trends across all of it.
- Activity and Settings — the record of what happened, and the configuration behind everything above.
WHO SEES WHAT
Not one gate
People is deliberately uneven.
Some of People is for everybody and some of it is not, and the difference is intentional. Directory, Performance and Intelligence are visible down to viewer level, because knowing who your colleagues are is not privileged information. Settings is owner and admin only.
Between those, individual sections gate on their own permission. A workspace can hand somebody the ability to manage approval chains without also handing them attendance policy, or payroll rules, or the access matrix.
Tip
If somebody can see People but not a particular section, that is the design rather than a fault. The fix is granting that one permission, not raising their role — raising the role gives them far more than they asked for.
BEFORE ANYTHING ELSE
Two things worth setting up first
Both are prerequisites for things further on.
1
Your departments and roles
Organisation. Almost everything else — approvals, payroll grouping, performance reporting — is easier once this exists, and one approval type does not work at all without it.
2
What you hold about people
Settings → Self-service, where the sections of the employment record and any custom fields are defined. Adding fields later is fine; deciding early means you are not re-entering data.
Start with the structure
Departments, roles, and the two settings behind department approvals.