Enabling modules, roles & permissions

Modules are licensed per department

Each module is turned on at the department level. If a module is part of your plan, it appears on the Launchpad and in the side menu. If it is not licensed, its pages are blocked and members will not see it. Changing which modules your department has is handled through your plan and billing — an admin can review the current plan under /billing.

Beyond the department license, each user can be granted access to a module. So even if your department licenses Office, an individual member only sees it if their account has the Office key. This keeps sensitive areas (like member PII or background checks) limited to the people who should see them.

The three roles

• user — the everyday role. Can do the day-to-day work in the modules they have keys for: running truck checks, viewing rosters, recording attendance, and so on.
• admin — can configure modules: edit settings, manage members and officers, build templates, manage CAD connections, and view reports. Admins also see /billing and the /activity log.
• super_admin — full control of the department, including the things admins can do plus the most sensitive configuration. This is the top role inside a department.

Module keys

On top of the role, access is gated by per-module permission. For example the Office module checks an office key, and individual actions check finer permissions (such as voting.edit) before showing edit controls. If a member can see a page but not the buttons to change it, they likely have view access without the edit permission.

Good first steps for a new admin

1. Confirm which modules your department has on the Launchpad and under /billing.
2. Add your members (Office → Members) and set their membership level.
3. Decide who needs admin access versus everyday user access, and grant module keys accordingly.
4. Work through each module's setup article in this Help Center.