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 works with a fictional external survey company. We will create the company grouping and explain how membership affects access.
- 0:08This page manages external companies working inside your organisation. A company groups members; it does not create a reporting hierarchy or replace a role.
- 0:19An authorised administrator supplies the company name and code. Use a recognisable code because activity records can refer to it later.
- 0:27Our fictional partner is Training Survey Partner, code DEMO PARTNER. Its records and members are examples, with no real customer identity attached.
- 0:37Invite or update the relevant member in Team members and assign their partner company. Review the person's role and individual permissions as well.
- 0:46Company membership helps define which files a member can see. Roles and individual permissions determine actions; neither should be considered alone.
- 0:55Moving a person to another partner company does not move every file they uploaded earlier. Files retain the company recorded at upload.
- 1:04A partner company with assigned users must have those users reassigned before deletion. Check ongoing work and historical context before changing the grouping.
- 1:14Pause here. Explain which parts of access come from company membership and which come from role permissions. Describe what happens to earlier uploads when a member moves.
Bring in a survey partner
Harbour Roads Training works with a fictional external survey company. We will create the company grouping and explain how membership affects access. This page manages external companies working inside your organisation. A company groups members; it does not create a reporting hierarchy or replace a role.
Create a clear grouping
An authorised administrator supplies the company name and code. Use a recognisable code because activity records can refer to it later. Our fictional partner is Training Survey Partner, code DEMO PARTNER. Its records and members are examples, with no real customer identity attached.
Assign people through Team
Invite or update the relevant member in Team members and assign their partner company. Review the person's role and individual permissions as well. Company membership helps define which files a member can see. Roles and individual permissions determine actions; neither should be considered alone.
Example: moving a member
Moving a person to another partner company does not move every file they uploaded earlier. Files retain the company recorded at upload. A partner company with assigned users must have those users reassigned before deletion. Check ongoing work and historical context before changing the grouping.
Membership does not rewrite history
The company associated with an earlier upload is part of that record’s context. Moving a person into another company grouping does not move all their historical files with them. Review both current membership and the company recorded on each relevant submission.
Before removing a grouping, reassign its users through the supported workflow and consider ongoing work. Company membership helps establish record visibility; roles and individual privileges still govern actions. Neither should be treated as a complete access model on its own.
Practise and check your interpretation
Pause here. Explain which parts of access come from company membership and which come from role permissions. Describe what happens to earlier uploads when a member moves.
Company membership groups external users and helps define which records they can see. Roles and individual permissions govern actions. Moving a member does not move historical uploads into the new company. Reassign users before deleting a company grouping, and retain the context of ongoing work.
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.