Custom roles
The role library is deliberately job-shaped, but some operations need a cut it does not have - “front desk, plus expenses, minus guest history”, say. That is what custom roles are for: a role composed for your workspace alone, from the same permission palette the built-in roles are made of.
How you get one
Section titled “How you get one”Custom roles are a plan feature, and their definitions are composed on the Stay N Host platform side and published into your workspace - your Team screen stays assignment-only, by design, so no workspace can quietly redefine what a role name means. Talk to support with the shape you need; your plan sets how many custom roles your workspace can hold.
What a custom role can contain
Section titled “What a custom role can contain”Two kinds of grant, both validated against code-defined registries:
- Capabilities from the palette - the same atomic permissions the library roles are built from (create bookings, record expenses, view reports, and so on).
- Pages from the registry - which screens the role can open.
Anything outside those two registries is refused. There is no free-form grant, which is what makes a custom role auditable: its whole meaning is a list you can read.
The hard ceilings
Section titled “The hard ceilings”Some grants are structurally excluded - not discouraged, impossible to compose:
- No money movement. Verifying or rejecting payments, approving or executing refunds, and recording ledger transactions are single-actor gates that stay with their designated library roles.
- No lock-code release. Generating or sending door codes never joins a custom role.
- No cancellation or no-show powers, no damage resolution - the other single-actor gates are equally out of reach.
The exclusion is enforced three times over: the composition validator refuses the grant, the database refuses the row, and the authorization engine re-checks the holder at runtime. A custom role that seems to need one of these actually needs a person who also holds the corresponding library role - grant both to the same seat instead.
What’s next
Section titled “What’s next”- Most gaps are better solved with a combination of narrow library roles on one seat - read Choose the right role first.
- The full permission matrix is in Reference.