Set up the department foundation
- 1
Confirm department identity, logo, and branding under Settings → General.
- 2
Set the timezone, 24-hour time preference, station and apparatus lists, and any two-factor authentication requirement.
- 3
Create roles (templates are available) and grant exact actions for each enabled module.
- 4
Add personnel, assign roles, record certifications, and send sign-in instructions.
- 5
Enable optional modules under Settings → Modules.
- 6
Publish a test announcement in Dept Communications and confirm acknowledgement tracking.
- 7
Build and test any Workflows the department wants to automate.
Choose a step-by-step task guide
Each guide includes prerequisites, exact actions, verification, and troubleshooting—not just a feature summary.
Module capabilities
- Dashboard with the information and next actions your roles allow
- Personnel directory with profiles, custom fields, bulk edit, disabling, and deletion controls
- Certification Hub with types, categories, and expiry reminders
- Roles with templates, cloning, colors, and action-level permissions that combine across a member’s roles
- Dept Communications: announcements with priority, audiences, scheduling, pinning, and acknowledgement tracking
- Department email to named members or whole roles — immediately, at a scheduled time, or repeating daily, weekly, or monthly — with email logs
- Department calendar with month, week, and phone views, recurring events, categories, RSVP, reminders, and a personal .ics feed
- Workflows: triggers, actions, approvals, signed incoming webhooks, templates, run history, and simulated test runs
- Authenticator-app or email 2FA with backup codes, and a logged “view as member” mode for authorized admins
- Activity log with actor, target, and severity; critical entries are kept permanently
- Optional Sparky AI assistant (off until enabled) and the Support Hub
Before your department relies on it
- 1
Confirm the department timezone before scheduling messages or importing dated records.
- 2
Define stations and apparatus before configuring modules that use those lists.
- 3
Create roles around job responsibilities; avoid giving broad administrator access for one missing action.
- 4
Grant own-record permissions when a member should not see department-wide records.
- 5
Disable departed members instead of deleting them so their history stays intact.
- 6
Run every new workflow as a test run before publishing it.
Portal destinations
These destinations appear only when the module is enabled and your roles grant the required access.
| Area | Portal path |
|---|---|
| Dashboard | /dashboard |
| Dept Communications | /announcements |
| Scheduled emails | /announcements?view=scheduled-emails |
| Calendar | /calendar |
| My Profile | /profile |
| Personal settings | /settings/appearance |
| Personnel | /settings/users |
| Add personnel | /settings/users/new |
| Certification Hub | /settings/users/certifications |
| Roles & Permissions | /settings/roles |
| General settings | /settings/general |
| Modules | /settings/modules |
| Workflows | /settings/automations/workflows |
| Workflow approvals | /settings/automations/workflows/approvals |
| Activity Log | /settings/logs |
| AI Assistant | /settings/ai-assistant |
| Support Hub | /support-hub |
Associated modules
Required modules must be enabled first. Related modules exchange data or extend the workflow when both are available.
Dependencies
Answers before you get stuck
Why can’t a member see a feature?
The module must be included in the subscription and enabled, and the member must hold the exact action permission through at least one role.
Should I delete someone who left?
Usually no. Disable the account to block access while keeping schedules, time, training, approvals, and audit history.
How long are activity logs kept?
Critical entries are kept permanently. Routine entries are removed after about two months.
Where did Settings → Automations go?
It now opens Workflows. Scheduled and repeating emails to members or roles are sent from Dept Communications.