Roles & permissions

Optional step. Finish step 3.0 — Create your organization, outlet, and team first. Return here when you are ready to invite staff and control what each person can do in Invinite.

You can run a small venue with one owner account and add roles later. Larger groups usually set up a few templates (e.g. Bar Manager, Receiver) before inviting the team.

Where to go in the app

Task	Menu
Define what a role can do	Roles & Permissions — create or edit a role, set levels per area (receiving, items, reports, …)
Assign roles to a person	Users — edit user → access section

The organization owner can do everything. Everyone else needs role assignments at the right level.

Concepts

Three levels

Level	What it controls
Organization	Users, billing, roles, master catalog (suppliers, items), outlets
Outlet	Teams under that location
Team	Day-to-day work: items, purchase orders, receiving, stocktakes, sales

Receiving stock checks team access for that bar or kitchen — not organization access alone.

Role templates vs assignments

• Role templates are reusable definitions: “Bar Staff”, “Outlet Manager”, and so on.
• Assignments attach a template to a user at organization, outlet, or team level.

Editing a role template

On Roles & Permissions → Edit role, each row is one permission area (Users, Receiving, Items, …).

Dropdown choice	Meaning
No permission	This role does not allow that area at all.
View / Create / Edit / …	The role allows up to that level (higher levels include lower ones).

There is no “use default” on this screen — defaults only apply when assigning roles to users.

Assigning access to a user

Organization role

Choice	Effect
A role	Organization-wide permissions from that template.
No organization role	No org-level access (unless the user is owner).

Defaults for all locations

Apply to every outlet and team unless you customize per outlet.

Field	If left empty
Default outlet role	No outlet-level role anywhere (unless you override per outlet).
Default team role	No team-level role anywhere (unless you override).

Empty here means no default — not “inherit from above”.

Customize per outlet

Use when one location needs different roles than the defaults.

Field	If left empty
Outlet role override	Use default outlet role
Team role for all teams in this outlet	Use default team role
Per-team dropdown	Use default team role (after outlet-level team default, then org default)

So: on defaults, empty = no access at that level. On overrides, empty = keep using the default you set higher up.

Quick examples

Bar staff at every team

1. Default team role: Bar Staff
2. Leave default outlet role empty unless you need outlet-level permissions.

Manager at one outlet only

1. Leave both defaults empty.
2. Turn on Customize per outlet → set roles only for that outlet.

Most teams as Bar Staff, one outlet stricter

1. Default team role: Bar Staff
2. Customize → set a higher role for that outlet’s teams.

You cannot set a default team role and then “turn off” one team with an empty override — empty on an override row still uses the default. To exclude a team, leave the default empty and assign roles only where needed.

What’s next

With structure (and optionally access) in place, continue to step 4 — Set up your catalog: suppliers, inventory, and menu import.