When operating Dive across multiple departments, it is important to configure "which department members can view which SOPs". This page provides guidance on how to perform this setup.

Initial Setup Flow

1. Reflect organizational hierarchy (performed by Owner/Team Administrator)
2. Create folders for company-wide, multi-department, and individual department use

Reflect Organizational Hierarchy

The SOPs a user can access depend on the access restrictions configured on the folder where that SOP is stored. This access restriction means "users who belong under the configured groups can access".

Here is a reference for configuration. We recommend the following efficient setup flow:

The number of groups that can be created and the number of sub-group levels vary by plan. You cannot create groups in Free or Lite plans. For details, please refer to Operating with multiple companies/factories (Administrator regular tasks and permission design).

1. First define the organizational hierarchy in Dive
2. Then use Excel import to reflect group affiliation for each user in bulk

Create Folders for Company-Wide, Multi-Department, and Individual Department Use

Configure access restrictions for each folder. Folders can have a tree structure. Below is the recommended flow for configuration:

1. Owner/Team Administrator users first create top-level folders based on organizational hierarchy (e.g., "XXX Business Division").
2. Configure access restrictions for each created folder. For the configuration method itself, please refer to here.
3. Thereafter, Group Administrators create lower-level folders based on organizational hierarchy or purpose.
   *In some cases, Owner/Team Administrator users may also perform this step.

4. Owner/Team Administrator users create a company-wide folder at the top level. Do not configure access restrictions for this folder.

Note: When access restrictions are configured on both parent and child folders, only users who belong to both groups can access. If you specify a location at the parent level and a department at the child level, users who belong to the department but not to the location group will not be able to view. Configure restrictions only at the levels where necessary.

Notes on Operations

Policy on SOP Creation and Distribution

When creating SOPs and issuing them, you need to store them in a folder. You can only store SOPs in folders that the creating user can access. If the above configuration has been completed, you can encourage storage in the appropriate folder.
*Note: Owner and Team Administrator users can access all folders, so please be aware of this if creation will also take place.

Operations During Revision

After issue, users other than the user who initially created it can also revise it if they can access the SOP (i.e., can access the folder). However, if "Groups that can also edit" is specified in the folder's access restrictions, only Group Administrators and creating users in that group can revise (Owner and Team Administrators can always revise). Even if the creating user changes, continuous operations are possible if the relevant user is appropriately set up in the group.
Note: After the change, even if the new creating user does not have target videos in materials, they can access materials that are upload targets from the revision editing screen.

Related Information

• Operating with multiple companies/factories (Administrator regular tasks and permission design)
• Benefits/disadvantages of consolidating multiple companies/organizations into one team (contract unit)
• Folder access restriction settings