Managing Roles & Permissions

Roles help you manage access across your organization by defining the permissions available to different types of users.

For example, you might create separate roles for Property Managers, Regional Property Managers, Risk Managers, or Administrators based on the responsibilities of each group.

A Role is a collection of permissions that determines what a user can access and which actions they can perform in Eolas.

Permissions can be configured for different areas of the platform, including Events, Incidents, Forms, Sites, Categories, Workflows, and more.

Note: Permissions apply only within the locations a user has access to.

To view the Roles configured for your organization:

From the Roles list, you can see the Roles currently available within your organization and when they were last updated.

To create a new Role:

Use Role names that make it easy to understand who the Role is intended for.

For example:

Adding a description can also help administrators understand the purpose of a Role when reviewing your organization's configuration later.

For each area of Eolas, you can define the level of access available to the Role.

Depending on the resource and action, permissions may include:

None - The Role does not have access to the selected action.

Limited - Access is limited to items created by or assigned to the user.

All - The Role has access to all applicable items within the locations the user can access.

Disabled - The permission is unavailable or depends on another permission being enabled.

Permissions are organized by resource and action.

Depending on the resource, you may be able to control whether users can:

For example, you may give a Role permission to view all Incidents while limiting the records they can edit.

Review each permission based on what users assigned to the Role need to accomplish in Eolas.

Tip: Give users the access they need to complete their responsibilities without enabling unnecessary permissions.

The permission matrix includes different areas of the Eolas platform, such as:

Additional resources may also appear depending on your organization's configuration.

You can scroll through the permission list when creating or updating a Role to review access across the platform.

To review or update an existing Role:

Before making significant permission changes, consider how those changes may affect users currently assigned to the Role.

Administrators can delete a role that is no longer needed.

Deleting a role removes it from the Roles list and revokes that role from any users or teams it was assigned to. Users may retain access through other assigned roles.

Roles determine what a user is allowed to do, while the user's assigned locations determine where that access applies.

For example, a Property Manager may have permission to view and manage Incidents, but those permissions apply only within the locations available to that user.

This allows organizations to use consistent Roles while controlling access to the appropriate properties or areas of the organization.

For additional support, start a chat with the Eolas Help Team directly from the Help link on the navigation bar, or reach us at [email protected].