Roles and Permissions for Hostel and Mess Managers

In a five-member mess, access control barely matters — everyone knows everyone, and if something's wrong, someone just fixes it. Past a certain size, or the moment a workspace involves people who manage it without living there, "everyone can do everything" stops being convenient and starts being a liability.

The three roles most workspaces actually need

Every workspace starts with three built-in roles. Owner is the workspace creator, with full access by default. Admin covers day-to-day management — logging bazar, generating bills, moderating announcements — without necessarily owning the workspace itself. Member is the default for everyone else: they mark their own meals, add their own guests, and see their own bills, nothing more.

For most hostels and messes, those three roles are the entire access model, and nothing further needs configuring.

When three roles aren't enough

Some workspaces need finer control than "admin or not" — a treasurer who should see every ledger but not moderate chat, or a duty coordinator who manages the bazar rota without touching billing. For that, custom roles are built from a permission catalog of 30 individual keys spread across 16 categories, so a role can be scoped to exactly the responsibilities it needs and nothing else.

Manage-only: the case that breaks most simple role systems

The trickiest case in shared-living access isn't "who can do what" — it's "someone who runs the place but doesn't eat there." An owner who manages a mess for a relative, or an admin hired purely to handle logistics, still needs full administrative access, but including them in the meal-rate calculation and per-member averages would be wrong — they're not one of the people the bill is being split between. The manage-only flag on a membership solves exactly that: full admin access, zero presence in meal bills or the averages used to sanity-check them.

The invite lifecycle, not just the role list

Getting people into the right role also means handling what happens around it: email invites to new or existing users, resending one that got missed, accepting it, and — just as often needed — suspending a member who's on leave, reactivating them later, or removing someone who's left for good. A role system that only handles the happy path of "invite once, done forever" doesn't match how membership in a hostel actually turns over.

Read more about team, roles and permissions, or see what it costs to run your workspace this way — free while in beta.