All help articles › MyWatchtower
On HID communities, access comes from access levels: each level pairs doors with schedules, and individual credentials hold the level. That is the key difference from Brivo — a Brivo group holds people, while an HID access level is held by credentials. This guide covers creating one level and setting it up; for the full access model, see "Groups, Schedules, and Access Levels".
Every access point on a level needs a schedule — with no schedules yet, the level's page tells you: "Create a schedule first — every access point on a level needs one." See "Create an Access Schedule".
1. Open Access > Access Levels ("Organize credentials and access points into access levels"). 2. Click Create Access Level and enter the Access Level Name (required).
Open the level and use the Credentials panel to add or remove the credentials that grant on this level's doors. Credentials can also pick up levels at creation or reassignment — HID requires at least one access level per credential; see "Create a Credential".
Use the Access Points panel to pair each door with a schedule, exactly as with Brivo groups: pick a schedule for the door, then add it.
You never push changes to the panels yourself. Changes to a level — its schedules, doors, grants, and credentials — are queued and delivered to the controllers automatically; push-status chips show whether a change has landed, is still pending, or failed, and API messages surface in snackbars. Recent changes may take a short while to work through the queue.
Deletion is reached from the bin icon on the level's list row. Before you confirm, the dialog runs its own impact check: it counts the credentials on the level and tells you who actually loses access — not every credential on the level necessarily does. Review that information before confirming.
If a schedule delete is being refused because this level still uses it, detach the schedule here first — see "Create an Access Schedule" for how the blocked-delete dialog works.
If the Access Levels tab is missing, your community may use Brivo rather than HID (see "Create a Brivo Group"), or your role may lack the needed permission — check with your community Admin, or submit a help desk ticket.
Was this article helpful?
Still stuck? Open a ticket — the subject and this article are filled in for you — or email support@jekasoftware.com.