FriendHRM User Manual
Resolve access, data, and feature-availability issues
Use an evidence-based support request when a page, record, feature, or expected data is unavailable, and keep the request scoped to the exact person, tenant, and task.
Intended audience
- Admin
- HR
- Manager
- Employee
- SuperAdmin
Where to find it
My workspace → Helpdesk, or use the assigned tenant/platform support process.
Before you start
- Availability can depend on role, tenant entitlement, plan, country, provider, assignment, policy, workflow state, and record-level data scope.
Steps
- 1
Capture the exact context
Note the page URL, task, tenant, affected record or period, expected result, visible result, and approximate time of the issue.
- 2
Check the expected boundary
Confirm whether the issue could be caused by your role, feature entitlement, country or provider configuration, workflow stage, or data assignment.
- 3
Submit a useful support request
Use Helpdesk or the designated support route with the safe details above, screenshots that exclude sensitive data where possible, and no passwords, MFA codes, or broad exports.
Expected result
The owner can distinguish a legitimate access boundary, missing configuration, data issue, or product defect and respond without widening permissions unnecessarily.
Open the relevant FriendHRM workspace
These destinations are verified against the current product navigation or route record. They remain subject to sign-in, feature, tenant, role, and data-scope checks.
Common problems
I do not know which owner can resolve the issue.
Start with your tenant Admin or HR contact for tenant work, and the designated SuperAdmin or platform owner for platform work. Include the exact route and expected task in the request.