Watch the overview
About 2 minutes. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00Harbour Roads Training needs an uploader, a reviewer and a final approver. This lesson explains invitations, membership and access without using real names or contact details.
- 0:11The directory shows people, roles and account status. Use the available company or permission views to understand who is meant to do each step.
- 0:20A person labelled reviewer may still lack a required permission or file scope. Check actual capability and the file's signing rules before assigning a handover.
- 0:29An authorised administrator selects the new member’s role and company membership. In training we use fictional role labels and reserved example addresses only.
- 0:40Confirm the intended organisation, role and partner company before an invitation is sent. A wrong company assignment can give the person an unsuitable file scope.
- 0:50Pending invitations are different from active accounts. Use the available resend, change-role or revoke actions to manage an invitation rather than creating unnecessary duplicates.
- 1:00If a colleague cannot act, check whether the invitation was accepted, the account is active, and the required permissions are present. Repeating the invitation may not solve the problem.
- 1:11Changing a role affects capability; changing company membership affects scope. Review both when a person's responsibilities change.
- 1:20Deactivation prevents an account from continuing normal work. Review the person's active responsibilities and hand over records before removing access.
- 1:29Check that the organisation has an eligible final certifier who differs from the uploader and co-signer. Having three accounts is not sufficient without the right permissions.
- 1:39Pause here. Assign the training roles to upload, co-sign and final approval. Identify the checks needed before inviting an external partner.
Build the review team
Harbour Roads Training needs an uploader, a reviewer and a final approver. This lesson explains invitations, membership and access without using real names or contact details. The directory shows people, roles and account status. Use the available company or permission views to understand who is meant to do each step. A person labelled reviewer may still lack a required permission or file scope. Check actual capability and the file's signing rules before assigning a handover.
Invite the right role
An authorised administrator selects the new member’s role and company membership. In training we use fictional role labels and reserved example addresses only. Confirm the intended organisation, role and partner company before an invitation is sent. A wrong company assignment can give the person an unsuitable file scope. Pending invitations are different from active accounts. Use the available resend, change-role or revoke actions to manage an invitation rather than creating unnecessary duplicates.
Example: a missing reviewer
If a colleague cannot act, check whether the invitation was accepted, the account is active, and the required permissions are present. Repeating the invitation may not solve the problem. Changing a role affects capability; changing company membership affects scope. Review both when a person's responsibilities change. Deactivation prevents an account from continuing normal work. Review the person's active responsibilities and hand over records before removing access.
Keep sign-off possible
Check that the organisation has an eligible final certifier who differs from the uploader and co-signer. Having three accounts is not sufficient without the right permissions.
Resolve membership before assigning work
An invitation that has not been accepted is different from an active member with insufficient privileges. Check account state, organisation context and the intended responsibility before changing access. Use the fictional reviewer address only as an illustration; replace it with the correct address through your normal administration process.
Review the least access needed for the person’s work. Invitation, membership and permission changes should be deliberate and traceable. Do not assume that adding somebody to the team makes them eligible to approve every existing file.
Practise and check your interpretation
Pause here. Assign the training roles to upload, co-sign and final approval. Identify the checks needed before inviting an external partner.
Use generic training identities and the reserved example.invalid email domain in demonstrations. An invitation is not an active membership until the recipient completes acceptance. Review the intended role, individual permissions and partner company. Keep the final certification responsibility independent from the uploader and co-signer. Deactivation affects access; it does not rewrite historical authorship.
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.