The objective of this knowledgebase article is to understand how Business Unit functionality can enhance content ownership and restrict visibility and edit rights within an organisation. This facilitates individual business areas managing their content autonomously, ensuring that access to sensitive information can be restricted to Users and/or Positions affiliated to Business Units.

A user must have either of the following permissions to configure Business Units:

• Model Administrator
• Administration

Three main Business Unit Permission types dictate the visibility and editability of content within the organisation's model. These Business Unit Permissions will be applied in addition to the user's current log-on permissions. (Refer to the permission description in Manage Users article)

This article includes the following topics:

1. Understanding Business Unit Permissions
2. Configuring Business Units
3. Assigning Items to Business Units 

Open Viewing and Restricted Editing

Example 1: Internal Recruitment is a Published process that is visible to everyone in the organisation but can only be edited by users within the HR Business Unit.

Example 2: Onboarding is a new Draft process (no previously published version) that is visible to everyone in the organisation but can only be edited by users within the HR Business Unit.

If Ron Weasley is given a direct link to the item, this is what the user will see:

Example 3: Training and Development process is being updated and the status has been changed from Published to Draft status. This process is visible to everyone in the organisation but can only be edited by users within the HR Business Unit.

Restricted Viewing and Restricted Editing

Example 1:  Financial Loan Approval is a new Draft process (no previously published version) that is only accessible to the Finance Business Unit

Example 2:  Payroll Processing is a process that is being updated and the status has been changed from Published to Draft status. This process is only accessible to the Finance Business Unit.

To configure Business Units, go to the People tab and select the Business Units sub-tab

2.1. Click Add New Business Unit 

*Image is for illustrative purposes only. Menu bar options vary based on your permissions or organisation's subscriptions .

2.2 Complete all the relevant sections in the overview.

2.3 Click Save to commit changes.

IMPORTANT: 
Required Permissions:
- Model Administrator (Assign to Positions)
- Administration (Assign to Users and Positions)

3.1. Once a Business Unit is configured,  it can be affiliated to Users and Positions 

3.2. To assign a Business Unit to a Position, open and edit the Position Item.  Within the Organisation Structure section, Select the Reports to Business Unit field as the primary Business Unit. Add any additional Business Units this position is affiliated with using the Add button for the Affiliated Business Units field.  You will need to do this in the event the position needs access to multiple Business Units that have restrictions placed on their related items.

3.3 Click Save to commit the changes.

3.4. To assign a Business Unit to a User you need Administration permission.  Open and edit the User item.   Within the Permissions & Roles section,  Select the Affiliated Business Units field.  Add all additional Business Units this position is affiliated with using the Add button for the Affiliated Business Units field.   You will need to do this in the event the position needs access to multiple Business Units that have restrictions placed on their related items.

3.5 Click Save to commit the changes.

NOTE: Follow the release management workflow to apply the changes

4.1. Once a Business Unit is configured, the following items can be associated with it:

• Process Streams
• Processes
• Work Instructions
• Systems
• Policies
• Regulations
• Obligations
• Controls
• Risks
• Documents
• Users
• Positions

NOTE: Follow the release management workflow to apply the changes