When using Dive in multi-department operations, it is important to configure "which SOPs can be viewed by people in each department". This page provides a guide on how to perform this configuration.

Initial Setup Flow

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

Apply Organizational Hierarchy

The SOPs that a user can access depend on the Access restriction settings of the folder where the SOP is stored. This Access restriction applies as follows: "Users belonging under the configured Groups can access it".

Here is a reference for your configuration. As an efficient configuration flow, we recommend the following:

The number of Groups created and the levels of sub-groups vary by Plan. Free and Lite Plans cannot create Groups. For details, refer to Managing Multiple Companies and Factories (Administrator Regular Tasks and Permission Design).

1. First, define the organizational hierarchy in Dive
2. Then, bulk apply Group Affiliation for each user via Excel import

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

Apply Access restriction to each folder. Folders can be structured in a tree hierarchy. The tip is to configure them in the following flow:

1. The Owner or Team Administrator user first creates top-level folders based on the organizational hierarchy (e.g., for XXX Business Division).
2. Configure Access restriction for each folder created. For the configuration method itself, refer here.
3. Subsequently, the Group Administrator creates lower-level folders based on organizational hierarchy or purpose.
   * In some cases, the Owner or Team Administrator user may also perform this step.

4. The Owner or Team Administrator user creates a company-wide folder at the top level. Do not apply Access restriction settings to this folder.

Note: When Access restriction is set on both parent and child folders, only users belonging to both Groups can access. If you specify a branch at the parent level and a section at the child level, users who belong to the section but are not in the branch Group cannot view it. Apply restrictions only at the necessary levels.

Notes for Operations

SOP Creation to Delivery Policy

When creating and issuing an SOP, you need to specify a folder to store it in. The folders available for storage are limited to those that the creating user can access. With the above configuration in place, you can encourage appropriate folder storage.
* Note: Since Owner and Team Administrator can access all folders, please be aware of this when they are also creating SOPs.

Operations During Revision

After issue, users other than the original creator can also revise the SOP if they can access it (meaning they can access the folder). However, if "Groups that can also edit" is specified in the folder Access restriction, only Group Administrators and created users in that Group can revise (Owner and Team Administrator can always revise). When the creator changes, continuous operations are possible if the new user is appropriately configured in the Group settings.
Note: Even if the new creator has no target videos in materials, they can access the materials to be uploaded from the revision edit.

Related Information

• Divide the visibility range of SOPs according to department hierarchy
• Managing Multiple Companies and Factories (Administrator Regular Tasks and Permission Design)
• Benefits and Drawbacks When Consolidating Multiple Companies or Organizations into One Team (contract unit)
• Folder Access restriction settings