Permissions that follow the org, not a global list
Roles in Orchard are permission sets, and they’re scoped per department. That means “Project Manager” in Delivery and “Project Manager” in Finance can be genuinely different roles with different access, despite the same name.
Two tiers exist: key roles, required to designate someone as Head of Department, and standard roles for everyone else. A person can hold several.
Setting up a manager role from scratch means granting access across a long list of resources, which is tedious the first time and worse the fifth. Role templates solve this: build the permission set once, save it, and apply it whenever you create a similar position. If you’re rolling out Orchard across multiple departments, building your templates first is the shortcut worth taking.
Shifts, breaks, and the details that actually hit payroll
Shift scheduling is where most generic tools get thin, because the edge cases are all in the compensation rules.
Orchard handles time zones properly, which matters if your team isn’t in one place. A shift is defined in a specific time zone, and each person sees it converted to their own — a shift starting at 00:00 in UTC+2 shows up as 17:00 for someone at UTC-5. You define it once rather than maintaining a version per region.
Break rules are configurable in the way payroll actually needs:
- Paid or unpaid breaks
- Break duration
- Minimum work time — for unpaid breaks, the hours after which a break becomes mandatory, with unused break time deducted from the total; for paid breaks, the hours someone must work to earn the break at all
You can also choose whether late starts and early finishes are flagged as violations, in which case they surface during time approval rather than being discovered later.
The effect is that approved hours come out the other end already reflecting your actual policy, instead of a manager applying the policy from memory.
Where the hours went
Projects in Orchard carry a budget, a currency, dates, an owning department (or several), and accumulated time spent.
People can track hours without a project assignment, so adoption doesn’t stall on getting the project list perfect. But once work is assigned to projects, the time rolls up — and because rates live in the same system, the gap between “hours logged” and “what this cost us” closes without a spreadsheet join. Projects can also hold participants and candidates, not just staff, which is useful when external people are involved in delivery.