Org unit security must be enabled within an environment. Once enabled, users must have both row security permissions which grant access to the tables and applications, as well as additional permissions that define the level of access they should have to the org unit records. Org unit permissions can be applied broadly to an environment, or be specific to single org units or tables. For example, you could create permissions that grant access to records: 

  • For a specific org unit in all tables. 
  • For a specific org unit in a specific table. 
  • For all org units in a specific table. 
  • For all org units in all tables. 
  • With no org unit specified in the Org Unit Security Field. For example, if Company is defined as the Org Unit Security Field on a table, any records that an empty or null value in the Company field would be included in this permission. This enables you to grant access to only records with an empty value, while restricting access to the other records in the table. 

Optionally, you can also apply org unit permissions based on the company structure. The company structure is where system administrators create org units and define the hierarchal structure for the organization. This allows you to apply the same permissions granted on one org unit to any org units which fall beneath it in the hierarchy. Learn more in Company structure.

Org unit security is additive, meaning it can further restrict access to records, but can not grant more access than whatever row security permissions a user has to the table. 

Learn more in Org unit security configuration and Example: Table specific org unit security.

Org unit security configuration

Application developers configure org unit security using the Table Definitions, Company Structure, Org Unit Security Setup, Permission Definitions, and Role Definitions applications. Security administrators enable org unit security in their environments using the Tenant Environment Setup application. 

Table Definitions

Org unit security can optionally be applied to tables. Most org unit security is configured without specifying specific tables. Table specific permissions are only required for families or modules with table based org unit security permission requirementsTo configure, in the Table Definitions application, you must:

  • Open the record for each table you want org unit security applied. 
  • On the General Configuration page, select a value in the Org Unit Security Field field. The value is a data item which holds the name of the org unit associated with the table's records. 

Company Structure

In the Company Structure application, you must:

  • Define the hierarchal structure of org units within your company. 
  • If a change is made to the hierarchy, select the Flatten Structure form action. Flattening the company structure rebuilds a flattened view of the relationships between org units. This process must be completed any time a new org unit is added, moved within the tree, or removed. 

Learn more in Company structure.

Org Unit Security Setup 

In the Org Unit Security Setup application, you can batch create all of the roles and permissions needed for companies and org units defined in the company structure from a single location. To create, you must:

  • Define the appropriate product family and product module. 
  • Select the type of roles you want to create. You can create roles of type Duty Role or Org Unit Security Template Role.
  • Specify whether you want to create roles and permissions for all companies, all org units, a single company, or a single company and all associated org units. 
  • Select the appropriate RUID access. 

Once you select the Create Roles and Permissions form action, individual records for each role, permission, and company or org unit combination are created. 

Permission Definitions

In the Permission Definitions application, create any other permissions you need for org units in your org unit security, or edit the records created in the Org Unit Security Setup application. For new permissions, you must: 

  • On the Org Unit Security page, in the Org Unit Security subtable, create a new row and specify the: 
    • Org Unit Permission Type—Determines how to implement org unit security for a given org unit. Options include:
      • All Org Units—Grants access to all org units in all tables, including records with an empty or null value, if no table is defined. If a table is defined, grants access to all org units in the specified table.
      • Specific Org Unit—Grants access to the specified org unit in all tables if no table is selected,. If a table is defined, grants access to the org unit within the specified table. 
      • Empty Org Units—Grants access to all records in all tables which have a null or empty value in the defined Org Unit Security Field. If a table is defined, grants access to all records in the specified table which have a null or empty value. For example, if Company is defined as the Org Field on a table, any records that have an empty or null value in the Company field would be included in this permission. This enables you to grant access to records with an empty value, while restricting access to the other records in the table. 
  • Select the RUID access for the org units or tables you defined. 
  • Optionally, select the Apply Hierarchy checkbox. This grants access to the org unit Org Unit defined in the Org Unit as well as all the child org units defined beneath it in the Company Structure.  

Learn more in Permissions.

Role Definitions

In the Role Definitions application, edit the records created in the Org Unit Security Setup application, or apply the permissions you created to duty roles, then assign them to the appropriate Org Unit Security Template Role in role hierarchies. These roles can then be assigned to user profiles. Learn more in Roles and Role hierarchies.

Enable org unit security in a your environments

In the Tenant Environment Setup application, navigate to the Global Settings application step. Open the detail view of the appropriate environment, then select the Org Unit Security checkbox.

Org Unit Security Setup application

System administrators use the Org Unit Security Setup application to bulk create the permissions and roles needed for an environment that has org unit security enabled.

Select the Type you want to create. You can configure Duty Role or Org Unit Security Template Role. 

Once you've selected your role type, determine whether you want to create roles for:

  • All companies in the company structure
  • All org units in the company structure
  • A single company in the company structure
  • A company and all associated org units in the company structure

Then, select the appropriate RUID access for your permissions. 

Once you select the Create Roles and Permissions form action, individual role and permission records for all of the companies or org units selected are automatically created. There are standard naming formats for the records created. Learn more in Security naming conventions and standards.

Org unit filtering on filtered table lookups

Apply org unit filtering to filtered table lookups in the Table Definitions application. This ensures users can only select org units which they have permission to access. 

Select the Apply Org Unit Filtering checkbox on org unit fields where you want filtering enabled. The table definition does not have to have org unit security applied in order to use org unit filtering. 

Org unit security filtering also applies when a logic block tries to insert a record into the underlying table. If you don't have access to an org unit defined in a record, you cannot insert the record into the table. 

Example: Global org unit security

This topic reviews a hypothetical example of how global org unit security can be applied to a company structure. 

For global org unit security configurations, you must have the company structure configured and org unit security enabled in your environment.

In this example, we are assuming the following configurations are already in place:  

  • Row security permissions that grant RUID access.
  • Org unit security enabled in your environment. 
  • A company structure defined with the following org units and hierarchy: 

>Headquarters
     >Denver Office
          >Denver Distribution Center
     >Kansas Office
          >Kansas Distribution Center

With org unit security enabled and this company structure configured, you could create different types of permissions for different users. The table below reviews some of the possible permissions you could create:

AccessResultConfiguration in the Org Unit Security subtable
Read access to all org units.Grant permission to read all org units in your environment. In the Org Unit Permission Type field, select All Org Units. 
Select the Allow Read checkbox. 

Read and update access to the Denver Office org unit.

Grants read access to the Denver Office org unitIn the Org Unit Permission Type field, select Specific Org Unit.
In the Org Unit field, enter Denver Office. 
Select the Allow Read and Allow Update checkboxes. 
Read and update access to Kansas Office, with Apply Hierarchy selected.Grants read and update access to the Kansas Office and Kansas Distribution Center org units.In the Org Unit field, enter Kansas Office. Select the Apply Hierarchy checkbox. 
In the Org Unit Permission Type field, select Specific Org Unit.
Select the Allow Read and Allow Update checkboxes. 
Read and update access to the Headquarters org unit, with Apply Hierarchy selected.Grants read and update access to all org units in the company structure in Table A and Table C, while retaining RUID access to Table B. In the Org Unit field, enter Headquarters. Select the Apply Hierarchy checkbox.
In the Org Unit Permission Type field, select Specific Org Unit.
Select the Allow Read and Allow Update checkboxes. 
RUID access to any records that do not have an org unit specified.
In the Org Unit Permission Type field, select Empty Org Unit.
Select the Allow Read, Allow Update, Allow Insert and Allow Delete checkboxes. 

Learn more in Org unit security configuration and Org unit security.

Example: Table specific org unit security

This topic reviews a hypothetical example of how table specific org unit security can be applied to a company structure. 

For table specific org unit security, you must have the company structure configured, org unit security enabled in your environment, and have org unit security applied to tables in your environment. Table specific permissions are only required for families or modules with table based org unit security permission requirements.

In this example, we are assuming the following configurations are already in place:  

  • Row security permission that grant RUID access for a security group which contains Table A, Table B, and Table C. 
  • Org unit security enabled in your environment. 
  • Org unit security enabled in Table A and Table C. 
  • A company structure defined with the following org units and hierarchy: 

>Headquarters
     >Denver Office
          >Denver Distribution Center
     >Kansas Office
          >Kansas Distribution Center

With org unit security enabled and this company structure configured, you could create different types of permissions for different users. The table below reviews some of the possible permissions you could create:

AccessResultConfiguration in the Org Unit Security subtable
Read access to all org units in Table A.Grant permission to read all org units in Table A, retains RUID permission for Table B, but grants no access to table C. In the Table Defintion field, enter Table A. 
In the Org Unit Permission Type field, select All Org Units. 
Select the Allow Read checkbox. 

Read access to the Denver Office org unit.

Grants read access to the Denver Office org unit in Tables A and C, while retaining the RUID access for Table B. In the Org Unit field, enter Denver Office. 
Select the Allow Read checkbox. 

RUID access to the Denver Distribution org unit in Table C.

Grants read, update, insert, and delete access for the Denver Distribution org unit in Table C, retains RUID permission for Table B, but grants no access to Table A.In the Table Defintion field, enter Table C. 
In the Org Unit Permission Type field, select Specific Org Unit.
Select the Allow Read,Allow Update, Allow Insert and Allow Delete checkboxes. 
Read and update access to Kansas Office, with Apply Hierarchy selected.Grants read and update access to the Kansas Office and Kansas Distribution Center org units in Table A and Table C, while retaining RUID access to Table B.In the Org Unit field, enter Kansas Office. Select the Apply Hierarchy checkbox. 
In the Org Unit Permission Type field, select Specific Org Unit.
Select the Allow Read and Allow Update checkboxes. 
Read and update access to the Headquarters org unit, with Apply Hierarchy selected.Grants read and update access to all org units in the company structure in Table A and Table C, while retaining RUID access to Table B. In the Org Unit field, enter Headquarters. Select the Apply Hierarchy checkbox.
In the Org Unit Permission Type field, select Specific Org Unit.
Select the Allow Read and Allow Update checkboxes. 
RUID access to any records in Table A that do not have an org unit specified.
In the Table Defintion field, enter Table A.
In the Org Unit Permission Type field, select Empty Org Unit.
Select the Allow Read, Allow Update, Allow Insert and Allow Delete checkboxes. 

Learn more in Org unit security configuration and Org unit security.

Company structure

The company structure enables you to define the hierarchal structure and function of the internal org units within your company. 

To configure a company structure in the Company Structure application, you must first define the different org unit types. Nextworld delivers several options including Company, Balance Sheet and Elimination Company, but you can add additional values into the list lookup if necessary. Once the types are defined, create a record for each org unit in your company. Records include information such as the org unit name, org unit number, contact information, and function. 

Org units are placed within the company structure in a hierarchy. The hierarchy can then be used in other processes such as reporting and org unit security. For example, security administrators can use the company structure to grant permission to records associated with specific org units, as well as the org units which fall beneath them in the hierarchy. Learn more in Org unit security.

Often, org units of the same type are placed at the same level of the hierarchy, though this is not required. 

Example

For example, in the following company structure, divisions are always at level 2 of the tree, departments are at level 3, and cost centers are at level 4:

Company Structure
>Company AA
     >Division 1
          >Department X
          >Department Y
     >Division 2
          >Department Z
               >Cost Center Z1
               >Cost Center Z2
     >Division 3

When transactions are entered, the segments are populated based on the org unit entered for each transaction. Where transactions are associated with departments and cost centers, you could see the following values:

Segment 1Segment 2Segment 3Segment 4
Company AADivision 1Department X
Company AADivision 2Department ZCost Center Z1
Company AADivision 1Department X
Company AADivision 1Department Y
Company AADivision 2Department Z
Company AADivision 3

When in the list form of this application, you could filter for Segment 2 to view all transactions associated with divisions.

In contrast, a company structure that does not require that org units of the same type be at the same level of the tree might have the following structure:

Company Structure
>Company AA
     >Division 1
          >Department X
          >Department Y
     >Area XYZ
          >Division 2
               >Department Z
                    >Cost Center Z1
                    >Cost Center Z2
     >Division 3

This would result in segments populated like the following: 

Segment 1Segment 2Segment 3Segment 4Segment 5
Company AADivision 1Department X

Company AAArea XYZDepartment ZDepartment ZCost Center Z1
Company AADivision 1Department X

Company AADivision 1Department Y

Company AAArea XYZDepartment ZDepartment Z
Company AADivision 3


When filtering for for different divisions, you would need to filter for both Segments 2 and 3 to get the full results. Similarly, you would need to filter for both Segments 3 and 4 to see all department results.

Solution specific org unit security

Solutions may each have unique org unit security implementations and recommendations. 

Review the following topics for solution specific org unit security recommendations: 

  • Directory org unit security recommendations
  • Inventory org unit security recommendations