How Access Roles Work in Enforcium

Access Roles in Enforcium define the level of access a user has within the workspace. They help determine which parts of the system a person can work with and which actions they can perform.

Access is closely connected to the company structure. Enforcium uses Positions from Org Structure when access is assigned to specific areas of the system. This creates a clear relationship between a person’s organizational role and the information they can access.

Access in Enforcium can depend on the user’s Position and the permissions associated with the area they are working in.

A Position represents a role within the organizational structure. Employees are assigned to Positions, and those Positions can be connected to access permissions across different parts of Enforcium.

This structure makes access easier to manage as the company grows. When an employee changes roles, their Position can also change, keeping organizational information aligned with their current responsibilities.

Some areas of Enforcium provide their own access settings.

For example, Customer Experience allows access to be configured separately for each ICP through Manage Access. Access is granted to Positions from Org Structure. The available access levels are:

Owner gives ownership of the ICP.

Can edit allows the user to view and edit the ICP.

Can view allows the user to view the ICP.

Employee Experience follows the same principle. You can define which Positions can access a specific map and which users can edit or view it.

Access levels define what a person can do with a specific piece of information.

Owner has ownership of the relevant content and can manage it.

Can edit provides access to view and change the content.

Can view provides access to review the content.

These permissions are useful when several people participate in the same area. A person responsible for maintaining the content can have editing access, while other employees can receive viewing access.

The exact access options can depend on the module. Customer Experience and Employee Experience use the access levels described above.

Access to information and permission to change it are related concepts.

For example, View mode and Edit mode are used throughout several Enforcium modules. View mode lets users review existing information. Edit mode provides the controls required to make changes.

In Org Structure, View Mode lets users review the company structure, while Edit Mode allows authorized users to create and edit Business Units and Positions and change their place in the hierarchy.

The same principle appears in Customer Experience and Employee Experience. Users with the appropriate permissions can enter Edit mode and maintain the structure of the relevant map.

A Position contains information that connects organizational responsibilities with operational work.

When you open a Position in Org Structure, you can find:

Job Description with responsibilities and expectations.

Employees with the people currently assigned to the Position.

Activity History with changes and actions related to the Position.

Metrics Access with the metrics available to the Position, including the metric name, Accountable Position, latest value, last update date, and access level.

Positions can also participate in Processes. When a Position is assigned as responsible for an Action Step, the related process appears in the employee profile under Job Description → Linked Processes.

This creates a connection between access, organizational responsibility, and daily work.

Access management works together with the rest of the Enforcium structure:

Company → Departments → Positions → Employees

Then, across the workspace:

Position → Access → Responsibilities → Processes → Metrics

This gives the organization a structured way to connect people with the information and work relevant to their roles.

Access settings can also be managed at the level of individual content. For example, Customer Experience and Employee Experience allow specific Positions to receive viewing or editing access through Manage Access.