• Workspaces only — Each workspace supports a single role and a single organization hierarchy.
• Workspaces with multi-hierarchy — Allows users to have multiple roles, switchable from the System > User Role menu.
• Disabled — Do not use. Users belong to a single workspace with a single organization hierarchy.

Format of the Excel worksheet downloadable from the Users screen.

• Automatic — Uses Single column when Workspace mode is Disabled; otherwise, uses One column per role.
• Single column — Includes the account fields and lists all permissions for a permission context in a single column (one column per permission context). Permissions for additional roles are not included.
• One column per role — Includes the account fields and all the available roles and permissions: one permission column per role and permission context.

Permission-by-segment allows user account permissions to be assigned to segments, in addition to user and unit groups. When disabled, permissions can only be assigned to units and unit groups.

This button lists all accounts with access to more than one unit group.

Switching from disabled to enabled changes the data a user can see from the union to the intersection of records. Use the list to assess how a user's data access will change. You might need to make other changes to ensure the users see the correct data after enabling permission-by-segment.

Controls how Unit Groups values are stored with the survey record.

• Enabled (recommended) — Persistent; Unit Group values never change after the record is created.
• Disabled — Dynamic; Unit Group values change to match those currently defined for the company.

When a survey record is created, the Unit Group values associated with the Unit are stored with the survey record. When org hierarchy filtering is enabled, these values never change. Disabling org hierarchy filtering allows the values to change whenever the company organization (the Unit Group fields) changes. This allow the record to always be associated with the current organization structure.

Enabling org hierarchy filtering is useful for people-based hierarchies, such as call centers, where users would not need access to historical information on Unit Groups, such as call center programs where the agents (Units) frequently move to different teams and managers should not inherit historical data. Disabling org hierarchy filtering is useful for location-based hierarchies, such as branches or stores, since historical data should follow hierarchies in these cases.

When org hierarchy filtering is disabled, a user's ability to sees specific unit groups in reports is determined by the intersection of that user's access to unit groups and units. Dynamic filters (also known as multi-select filters) hide unit groups in control panel dropdowns unless the user viewing the report has access to one or more units in those unit groups