Skip to main content

Creating Groups

Groups are collections of people who share the same access rules. They are the foundation of CloudAccess Key permissions — you assign access to a Group, then add Users to that Group, rather than configuring every User individually.

When to create a Group​

Create a Group for each distinct access pattern in your organization. Common examples:

  • All Staff — everyone gets access to the front door during business hours
  • Management — additional access to back office and after-hours
  • Cleaning Crew — access only on scheduled cleaning nights
  • Board Members (HOA) — common area + clubhouse access, no maintenance areas
  • Vendors — limited access on specific dates

A Group is not the same as a department label. Group people by what doors and when, not by org chart.

Steps — AccessCore One controllers​

These steps cover AccessCore One controllers (V2 interface) — the current platform.

Step 1: Open the Groups page​

Screenshot placeholder — V2 navigation to Groups.

Groups nav V2

Step 2: Click "New Group"​

Screenshot placeholder — V2 New Group button location.

New Group button V2

Step 3: Name the Group and save​

Screenshot placeholder — V2 Group create form.

Group create form V2

Use a name that describes access, not job title — Front Door Business Hours reads better than Office Staff.

Step 4: Confirm the Group appears in the list​

Screenshot placeholder — V2 Groups list with new entry.

Groups list V2

Steps — Legacy controllers​

These steps cover legacy controllers (V1 interface) — for sites not yet migrated to AccessCore One.

Step 1: Open the Groups page​

Screenshot placeholder — V1 navigation to Groups.

Groups nav V1

Step 2: Add a new Group​

Screenshot placeholder — V1 Add Group button.

Add Group V1

Step 3: Save the Group​

Screenshot placeholder — V1 Group form.

Group form V1

Next steps​

With Groups in place, you can:

  1. Add Users to the Group
  2. Configure Permissions — which doors the Group can use and when

Common pitfalls​

  • Don't create one Group per User — that defeats the purpose. If a person needs unique access, evaluate whether a Group of one is genuinely the cleanest model.
  • Don't name Groups after individuals — Groups outlive specific employees.
  • Don't pre-create Groups you don't need yet — empty Groups clutter the UI.