Team roles and permissions for property managers
Team permissions decide who on your staff can see and change what. In Ribat, staff belong to teams, and each team is authorised for specific modules, such as Operations but not the Calendar, and for specific properties. Everyone sees only what their job needs, and you can revoke access at any time.
Why permissions matter
As soon as more than one person touches your bookings, shared logins become a risk: nobody knows who changed a rate or issued a door code. Role-based accounts give each person their own login and limit what they can reach.
What you can control
- Teams: group staff and manage their access together.
- Module authorization: give each team only the modules it needs, for example Operations without the Calendar or rates.
- Per-property permissions: staff see only the properties they are assigned to.
- Invite, suspend or revoke access in one click when people join or leave.
- Door-code accountability: every code generated, sent, used or revoked is recorded in the access log.
Typical setups
| Team | Example access |
|---|---|
| Management | Every module and every property |
| Reservations | Calendar and reservations for their properties |
| Operations | The Operations module only, without the Calendar or rates |
| City or building team | The modules they need, limited to their properties |
These are examples. You decide which modules and properties each team can access.
Built for multiple properties
Each property has its own rooms, channels, team and rates, and is billed independently. That makes it practical to give one manager one building without exposing the rest of your portfolio.
Onboarding and offboarding staff
Adding someone is an invitation: choose their team, which sets the modules they can use, pick the properties they cover, and they sign in with their own account. When a team member leaves, suspend or revoke their access in one click so they can no longer see reservations or issue door codes.
Because every action runs under a named account instead of a shared login, you can tell who generated, extended or revoked a code, which matters most for smart-lock access.
Frequently asked questions
Can staff be limited to certain properties?
Yes. Access is scoped, so staff see only the properties they are assigned to.
Can I limit a team to certain parts of Ribat?
Yes. Each team is authorised per module, so for example an operations team can use the Operations module without seeing the Calendar.
Can I remove someone’s access quickly?
Yes. You can invite, suspend or revoke a team member in one click.
Are door-code actions logged?
Yes. Every code generated, sent, used or revoked is recorded, so you can see who could open which door and when.
Do extra team members cost more?
Pricing is a flat monthly fee per property based on room count. See the pricing page for the bands.
Related pages
- Feature Smart lock automation A unique, time-limited TTLock code for every booking, emailed to the guest automatically.
- Feature Booking calendar A single drag-and-drop calendar for every room, reservation and channel.
- Solution Property managers Portfolios of 10, 20 or 50+ units with per-property control and billing.
- Solution Boutique hotels Team roles, rate control and one dashboard across every room and channel.
- Pricing Pricing Flat monthly fee per property from $49, 0% commission.
- Home Ribat home The all-in-one PMS for apartments, hostels and hotels.
See it on your own bookings
Set up in about 15 minutes, with free guided setup and a 14-day free trial. No setup fee and no Ribat booking commission.