The Day I Could Have Crashed My Parents’ Car
When I was 12, my parents trusted me with the house keys… but not the car keys. Sensible. I could get in, feed the dog (and myself), and not burn down the place. Handing me the car would have been chaos.
In Mews, we face a similar challenge: giving the right team members access to the right tools without creating risk or confusion. That’s the philosophy behind granular permissions: give every individual the right keys, at the right time, for the right job.
Hospitality platforms are powerful and, let’s be honest, complex. You’ve got front office teams, revenue managers, housekeeping supervisors, finance, partners—the list goes on. Each role needs access to a very specific slice of capability. Too much access creates risk and noise. Too little turns every shift into a scavenger hunt. Our aim should be simple: reduce liability while making work feel lighter.
Building Permissions That Make Sense
Over recent months, we’ve been recreating permissions across Mews. Not as a giant “role tree” only an admin in God-mode understands, but as clean building blocks mapped to real tasks.
Think “view but not export financial reports,” “see users but not create new users,” “edit rates for dates Y–Z.” It’s precision, not guesswork. Granular permissions should be everywhere, to ensure seamless and exciting governance.
Master access your way
Join Mews and help shape tools that give the right people the right permissions!
I love having friends over for food, but when friends come over, I label spices because not everyone needs Carolina Reapers in their life. In the old world of permissions, it was “open the cupboard and hope.” In the new world, it’s “paprika for everyone, Carolina Reapers for the one person who really needs it in their life—and only for this dish.”
That’s how we’re approaching access in Mews: everyday actions are effortless; sensitive ones are explicit, traceable, and time-bound.
Permissions Like Lego Pieces
Admins can assemble permissions like Lego pieces, not monoliths. Start with sensible presets that mirror common hotel roles, then fine-tune by scope: property vs. group, date windows, monetary limits, data sensitivity. Temporary access is first-class—grant it for a shift or an audit, and it automatically expires.
Transparency is built in: every permission is explainable. Users can see why they can or can’t do something, and who to ask if they need more.
This isn’t just about control. It’s about experience. When the interface reflects your actual job, it shrinks. Fewer dead ends, fewer “ask an admin” moments, fewer risky workarounds. For managers, it means confidence that compliance isn’t a spreadsheet and a prayer. For IT and security, audit logs become signals, not haystacks.
Aligning Permissions to Real-World Objects
Under the bonnet, we’re aligning permissions to real-world objects—bookings, payments, rates, profiles—so policies are consistent everywhere. It also sets us up for smarter defaults. If we know a colleague is on housekeeping in Property A, we don’t need to show that colleague finance exports or customer data on reservation reports. Less surface area, fewer mistakes.
Modern hospitality runs on trust:
- Guests trust you with their time and their data.
- Teams trust the tools to help.
- Leaders trust that growth doesn’t mean growing risk.
Granular permissions are the quiet, diligent, and reliable foundation for all of that.
The day I could have crashed my parents’ car… I didn’t. And with granular permissions, your team can avoid “crashes” too.
