Role-based permissions FAQ

You can use permissions and assign them to an employee's user account in Mews, to ensure they have the correct permissions to manage only those parts of the system that are relevant to them. You use role-based permissions to control access in Mews Operations. You manage them in the User management section to assign roles, reduce security risks, and ensure each user has the correct level of access.

In this article, you can learn about the following FAQs:

What are role-based permissions?

Role-based permissions define specific actions users can perform:

  • The system groups permissions by domain, such as, reservations, operations, billing or analytics.
  • You can control which actions the users can perform for certain areas, such as view, create, edit, delete, and export.

This improves control over access, for example, you can allow a user to view reservations but not edit them. 

How do roles work?

Roles can group permissions based on job functions. The roles each match a hospitality departments and you assign one or more roles to each user, for example, you assign a finance role with access to billing and reporting. This simplifies user management and reduces setup time.

How does Mews structure permissions?

Permissions follow a domain-based structure. The domains include certain areas such as reservations, operations, billing and analytics.

Note: Some permissions depend on others in the hierarchy.

How does migration from classic individual permissions work?

The system supports both classic individual and role-based permissions during transition.

  • Role-based permissions take precedence
  • Existing access remains unchanged after migration
  • A migration tool suggests matching roles

For example, a role with access to sensitive reports keeps access through equivalent role-based permissions.

Note: Only users with permission to manage users can access the migration tool.

 

 

Was this article helpful?
00



Feedback