Optimize Assets. Streamline Operations.

Organization, Access Management and Roles

Access management in Omega 365 is based on a structured combination of Roles, Modules and Capabilities, applied within the organizational hierarchy defined by Org Units.

This structure ensures that users have the appropriate level of access and responsibility, while maintaining control over data visibility and system security across projects and organizational levels.

Roles, Modules and Capabilities

Modules

Modules are collections of applications and data tables grouped together to organize functionality within Omega 365. Each module represents a functional area of the system, such as Completion, Documents, Planning or Assets.

Modules define what applications and data areas a user can access.

Roles

Roles define user access and responsibilities within Omega 365. A Role is configured by combining one or more Modules and, optionally, additional Capabilities.

Roles determine how users interact with the system, including which data they can view, create or modify.

Roles are configured in the System Roles application, located under the Access menu group in the mega menu.

Capabilities

Capabilities are special permissions assigned to Roles. They extend standard access by enabling users to perform specific actions or use advanced functionality that is not covered by module access alone.

Capabilities are typically used to grant:

• approval rights,

• administrative actions,

• specialized system behavior.

Assigning Roles to Users

Roles are not assigned globally. Instead, Roles are assigned to users within a specific Org Unit using Org Unit Roles.

This means that a user’s access and permissions are always evaluated in the context of the Org Unit in which the Role is assigned.

A Role assigned to a user may also be designated as read-only, allowing the user to view applications and data without the ability to update or modify information.

Access Inheritance and Organizational Hierarchy

Once a Role is assigned to a user at a given Org Unit level, access is inherited downward through the organizational hierarchy.

As a result:

• the higher in the hierarchy a Role is assigned,

• the more Org Units the user will have access to.

This inheritance mechanism simplifies access management and reduces the need for repetitive role assignments.

However, Org Units can be configured to block inheritance from higher levels. This allows projects or departments to enforce stricter access control and limit data visibility where required.

Blocking inheritance is particularly useful when handling:

• sensitive project data,

• contractual boundaries,

• restricted organizational structures.