Watch the overview
About 2 minutes. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00The training organisation wants a reviewer to inspect findings without managing payments. We will separate role permissions, individual overrides and file scope.
- 0:10A role is a set of permissions. Open its details to see what it grants, rather than assuming its display name fully describes its authority.
- 0:19List the actions the person needs: viewing files, reviewing findings, requesting co-sign or final certification. Grant only the capabilities appropriate to that job.
- 0:30A review task does not automatically require billing administration. Keep these responsibilities separate unless the organisation intentionally assigns both.
- 0:40Permission to perform an action and permission to see a file are separate checks. Organisation, partner-company and own-file scope can produce different visible records.
- 0:51A member can have permission adjustments beyond the role. Review those overrides when their effective access differs from other people with the same role.
- 0:59Someone can open a file yet lack permission to certify it. The file's status and separation-of-duties rules can also prevent the action.
- 1:09Review the proposed role or member changes before saving. A broad role update can affect several members, not just the person whose problem you are investigating.
- 1:18Use permission change history and activity records to understand who changed access. Do not rely solely on a screenshot of the current role.
- 1:28Pause here. A training reviewer sees a file but cannot approve it. Check permission, file scope, current status and signer independence in that order.
Give access for a task
The training organisation wants a reviewer to inspect findings without managing payments. We will separate role permissions, individual overrides and file scope. A role is a set of permissions. Open its details to see what it grants, rather than assuming its display name fully describes its authority. List the actions the person needs: viewing files, reviewing findings, requesting co-sign or final certification. Grant only the capabilities appropriate to that job.
Example: reviewer versus billing
A review task does not automatically require billing administration. Keep these responsibilities separate unless the organisation intentionally assigns both. Permission to perform an action and permission to see a file are separate checks. Organisation, partner-company and own-file scope can produce different visible records. A member can have permission adjustments beyond the role. Review those overrides when their effective access differs from other people with the same role.
Example: visible but unavailable
Someone can open a file yet lack permission to certify it. The file's status and separation-of-duties rules can also prevent the action. Review the proposed role or member changes before saving. A broad role update can affect several members, not just the person whose problem you are investigating. Use permission change history and activity records to understand who changed access. Do not rely solely on a screenshot of the current role.
Combine role, scope and independence
A person may be able to view a file without being allowed to certify it. Their role, individual privileges, organisation or partner-company scope and signing independence all matter. Inspect the actual missing permission and current record context before broadening access.
For the training example, selecting an uploader as final certifier can conflict with independence requirements even if the account has broad permissions. Choose an eligible reviewer rather than changing permissions solely to bypass the workflow boundary.
Practise and check your interpretation
Pause here. A training reviewer sees a file but cannot approve it. Check permission, file scope, current status and signer independence in that order.
Check account status and company/file scope first, then the role’s permissions and any individual override. Changing a role can affect every assigned member. Review affected users and the activity history. A role label alone does not establish eligibility for a particular file; the final signer also has independence requirements.
Use the signed-in onboarding library to record viewing progress and return to unfinished lessons. Watching the public article is useful for reference, but does not update your account’s lesson completion record.
Sources and scope
This guide describes the platform workflow; it does not establish a requirement of a TMH manual. Platform review and certification are described in the product documentation.