Understand access to leave information¶
Leave involves personal records, organization policy and decisions made by authorized people. Access to WorkOS, permission to administer leave and responsibility for a particular approval are separate matters. A job title or a manager shown on a profile does not establish all three.
The intended screens are ahead of the connected frontend. This guide explains the inspected rules and the decisions an organization needs to make; it does not certify that the current demonstration enforces them. Complete access verification remains a rollout dependency.
Personal requests and administrative work¶
| Work | What to understand |
|---|---|
| Request your own leave | The service identifies the requester from the signed-in staff account. A policy must apply to that person for the requested start; selecting a policy name alone does not establish eligibility. |
| See your assigned policies and requests | These personal views use the signed-in staff account. Policy assignments can apply directly or through a position and can have an effective period. |
| Withdraw your own request | The action checks that the request belongs to the current staff member, then applies the captured policy and current request-state rules. See review or withdraw leave. |
| Maintain policies, assignments or balances | The inspected rules require leave-administration permission. Full policy details and balances also require that administrative permission. Ordinary staff access to the intended personal detail and balance experience still needs to be completed and verified. |
| Make a direct decision or change approved leave | Leave-administration permission and the specific action's rules apply. Direct decisions and the inspected manager interruption actions reject managing one's own request. This is not a universal rule for every administrative operation. |
| Review workflow approvals | Follow the configured workflow's assigned work and decision rules. A direct leave decision is not a substitute for the workflow route. |
A manual balance correction does not have the same rule preventing administrators from changing their own balance. Organizations that require independent review of those corrections need that rule explicitly agreed and verified; it must not be assumed from the self-approval restrictions.
Decide who may see and review records¶
The management list includes more than requests waiting for approval. Approved, ongoing, suspended and certain exception cases can appear. It is not established as a list limited to work assigned to the current reviewer. Use the saved state and approval route to understand what attention a record needs.
Privacy for request lists and details still needs verification. The current implementation does not establish that only the employee concerned and assigned reviewers can see a request. The organization must agree and verify the intended visibility before rollout; records shown in a demonstration do not establish that policy.
Before rollout, the organization owner should identify who needs personal access, who may administer leave, who handles direct decisions, who receives workflow work, and who investigates exceptions. Verify those responsibilities with representative accounts in the connected application. A broad administration permission should not be used as an assumed solution for ordinary staff viewing their own balances.
When access is unavailable¶
Confirm the organization and staff account you intended to use. For a missing policy, ask the policy owner to check its assignment period and any applicable position. For an unavailable balance or detail view, support should distinguish permission, missing staff identity, missing data and an unfinished connected screen.
Give support the action, approximate time, organization and relevant request reference. Use the organization's approved private support channel for personnel information. Do not share sign-in credentials or upload-finalization details. Repeated submission will not resolve an access problem and can complicate an uncertain save.
Responsibilities during rollout¶
Managers need an agreed review responsibility; tenant administrators need verified permission assignments; support needs a limited route for investigating specific records. Executives and process owners should require evidence that those boundaries work before treating a successful demonstration as operational acceptance. Account, organization and permission changes can affect later access even when a request was previously visible.
Continue with the leave task guide, policy administration or balance corrections.