Skip to main content
Each user has one or more roles, which decide what they can do, and optionally an access scope, which decides which parts of the estate they can see. You need the View users permission to see the Users page, and the create, update, reset and delete user permissions for each action.

Add a user

If your organisation signs in with Microsoft, you usually don’t need to add users here: they’re created the first time they sign in, with roles from your sign-in mappings. Add users by hand for people who sign in with a password.
  1. Go to Users and select New user.
  2. Enter their Email and Full name.
  3. Tick one or more Roles. A user with several roles can do everything any of their roles allows.
  4. Optionally, limit their access under Physical scope (below).
  5. Set an Initial password of at least 12 characters, and select Create user.
M.A.R.C.U.S. doesn’t send an invitation email. Give the user their password by another route, such as by phone or your password manager. They can change it later with Forgot? on the sign-in page.
If your organisation requires Microsoft sign-in, users can’t be added here; they’re created when they first sign in.

Limit a user to part of the estate

By default a user can see the whole estate. To restrict them, tick the parts they look after under Physical scope:
  • Tick a business unit, region, location, building or room to give access to it and everything inside it, including anything added later.
  • Ticks at different levels combine. Ticking one region and one room elsewhere gives access to both.
  • Leave everything unticked for the whole estate.
A restricted user sees only those parts everywhere in the portal: the sidebar, Overview, Map, Devices, Alerts and reports. Access is enforced by the database itself, not just hidden in the screens. The Users list shows each user’s scope as a chip, such as “2 regions · 1 room”.

Administrators with restricted access

An administrator who is themselves restricted to part of the estate:
  • sees and manages only users inside their own access. Users elsewhere in the estate, and users with access to the whole estate, don’t appear in their list;
  • can’t change anyone’s scope: only administrators with access to the whole estate can;
  • gives new users their own scope automatically.

You can’t give more than you have

Whatever their scope, nobody can:
  • give a role with permissions they don’t hold themselves;
  • edit, reset, disable or delete a user who holds permissions they don’t.
So someone who can manage users but isn’t a full administrator can’t make anyone an administrator, or take over an administrator’s account by resetting its password.

Change, reset or remove a user

Use the icons on the user’s row: You can’t disable or delete your own account. Each row also shows a disabled or you chip where they apply, and when the user last signed in, or Never signed in.
For users who sign in with Microsoft, roles from sign-in mappings are marked from Entra in Edit user. They follow the user’s Entra groups: unticking one only lasts until their next sign-in while they’re still in the group. Roles you tick by hand stay until you remove them.

Business units

If your organisation has several business units, such as separate departments or agencies, M.A.R.C.U.S. can keep each one’s rooms, devices and users apart within a single portal. Your service provider switches this on. Business units are then managed on the Locations page, regions are assigned to them, and users can be scoped to them as above.

Updated 06 Nov 2026 14:07 · page 1014b8b