Who this is for
The Super Admin role is for operators who run **more than one property** under a single organisation — a multi-site restaurant group, a franchise owner, or a managed portfolio of venues. If you only run a single site, you don’t need this guide — see the [Property Admin Guide](property-admin.md) instead.
A Super Admin is a normal Chef-Ops-Pro user who also owns an **Organisation**: a container that links several properties together so you can set shared standards across all of them, keep an eye on compliance portfolio-wide, and support any property directly when needed.
Getting Started
There is no separate login or portal for Super Admins — you sign in exactly the same way as any other user, with your email and password on the standard login page. Once you’re in, your account is recognised as the owner of an organisation, and an **Org Overview** link appears in your sidebar navigation alongside your normal property dashboard links.
If your organisation manages several properties, you’ll also see a **property switcher**, letting you move between the properties in your portfolio that you hold a direct membership on.
Organisation Settings
From Org Overview, you can set governed defaults that apply across every property in your organisation — for example:
– Temperature ranges for refrigeration and food safety
– Hot-hold and blast-chill thresholds
– Food cost targets
– Measurement system (metric/imperial) and currency preferences
You can also **lock** specific settings or entire modules. A locked field or module can’t be changed or disabled by an individual property’s Admin — it shows as fixed on their side, keeping standards consistent across every site in your portfolio without you needing to check each property individually.
Linking Properties to Your Organisation
To bring a property into your organisation, generate an **invite code** from Org Overview. Codes are formatted as `XXXX-XXXX-XXXX` and are single-use. Share the code with that property’s Admin, who redeems it from their own Property Settings page to link their property to your organisation.
Managing Property Slots
Your organisation has a set number of property “slots” tied to your subscription. From Org Overview you can:
– Add a new property slot
– Remove a property from your organisation
Removing a property doesn’t happen instantly — it enters a 7-day grace period first, giving you (or the property) time to reverse the decision before the link is permanently severed.
Entering a Property (Read-Only View Mode)
Sometimes you’ll want to look inside one of your properties directly — to support a manager, check on compliance, or investigate an issue. Use **Enter Property** from your Client/Property list to step into that property’s dashboard exactly as its own team sees it.
This is important: **entering a property is read-only.** You can see everything — temperature logs, rotas, checklists, reports — but you cannot add or edit data while viewing. Specifically, while in view mode you cannot:
– Add or edit refrigeration units
– Log a food temperature, delivery temperature, or blast-chill entry
– Calibrate a probe
– Make any other change that would normally require an Admin or Staff action
If you need to make an actual change inside a property, ask that property’s own Admin to do it, or exit view mode and log in as a member of that property if you hold one.
You can only enter properties that belong to **your own organisation** — Super Admins cannot view or access properties belonging to a different organisation or a different Chef-Ops-Pro customer.
Use **Exit Property** in the top navigation to leave view mode and return to your own dashboard.
Organisation Messaging
You can send messages down to the Property Admins across your organisation — useful for portfolio-wide announcements, policy updates, or compliance reminders. These messages are visible only to each property’s Admin, not to their wider staff.
Account & Session
– Update your profile, avatar, and password the same way as any other user (see Account Management in the [Property Admin Guide](property-admin.md))
– Use the **Logout** button in the top-right navigation to end your session
– Toggle **light/dark mode** from the same menu
