Skip to main content

From feedback to feature: Granular permissions

  • April 27, 2026
  • 3 replies
  • 17 views
Sarah.Masterton-Brown
Mews Employee
Forum|alt.badge.img+2

This week I caught up with @rui.oliveira from our product team to talk about a topic that’s come up time and time again in the community: Permissions.

Rui has been closely involved in shaping the new granular permissions feature, which is being rolled out at the end of April. In this short video, he shares what’s changing, why it’s needed, and how customer feedback played a role in getting it there.

Here’s what’s covered:

  • The move from individual permissions to a role-based system, and what that means in practice and the challenges it addresses.
  • How the feature was developed, including research with customers in the community.
  • What to expect from the rollout, including default roles and a migration path for existing setups

Watch the full conversation below to hear directly from Rui 👇

 

 


More documentation on granular permissions is on the way. In the meantime, feel free to share any questions or first impressions below.

If you want to go fast, go alone; if you want to go far, go together

    3 Replies

    mauritsbots
    Trailblazer
    Forum|alt.badge.img+4
    • mauritsbots
    • Trailblazer
    • April 28, 2026

    ​@rui.oliveira and others, i am currently scoping to change my permissions overview from role based to permission based; basically creating ‘blocks' of permissions, and adding these to the various employees based on their role.

    example: a supervisor reception now is granted the user role ‘supervisor reception’ with a list of privileges but i want to give them not just that one role anymore - but multiple blocks, e.g. ‘reporting’+’front desk operations’+’invoicing & billing’. this should hopefully make maintenance on this easier, and any promotions better to understand between properties. 

    (perhaps good to understand for those reading along, we have multiple properties, and with that multiple very very very similar roles)

    HOWEVER, when building these blocks, I dont want to push three university paths to each user, and ideally I can also add the cashier in this same flow. Is that in scope? Also, i am still missing marketplace privileges to minimize admin access to the properties. 

    is anybody working like this with blocks of persmissions already that i could learn from? 

    Also, in the ideal scenario, the new and classic permissions are clearly linked and explained as Managing user roles and permissions is still referring to only the old - and it is not clear what new tickbox replaces what classic privilege.

    Reporting

    View company & customer data, sensitive reports, all standard reports (view), accounting/guest/city/deposit ledger (view), trial balance (view), action log (view)
    Front Desk Operations Manage accounts & reservations, manage spaces, manage mail queue, charge cards online, perform housekeeping, overbook spaces, override rate price
    Invoicing & Billing Issue invoices, rebate items, reissue bills & invoices, manage invoiceability
    Questions? Brainstorm? Contact me!
    rui.oliveira
    Mews Employee
    Forum|alt.badge.img
    • rui.oliveiraMews Employee
    • Mews Employee
    • April 28, 2026

    Hi ​@mauritsbots 
    Is great to see this engagement and thanks for your questions!
    As off next week, permissions will be running on a role base only. So, users, when added to a given role, will inherit the permissions assigned to that role.

    You will also be able to assign users to multiple roles at the same time, and the permissions from those roles will be aggregated.

    When adding multiple roles, you'll be able to manually select which Learning Path to choose.

    Hope this clears your questions, but we're here to help!

    mauritsbots
    Trailblazer
    Forum|alt.badge.img+4
    • mauritsbots
    • Trailblazer
    • April 28, 2026

    check! will await these changes before rolling onto something i might regret :)

    Questions? Brainstorm? Contact me!
    Terms and ConditionsAccessibility statement