Shared logins and access sprawl
Every member has an individual account, and roles grant exact actions — seeing a page never implies changing it.
Platform foundation The department foundation
Core
People, roles, permissions, a dashboard of everything waiting on you, department communications, the shared calendar, Workflows automation, and the audit trail every module relies on.
- Action-level permissions
- One calendar, every module
- Automation with approvals
Why departments switch
What Core fixes.
Every Station Clipboard department starts with Core: personnel records, roles you grant action by action, a dashboard that gathers approvals and to-dos from every module, announcements that track acknowledgement, email to members or whole roles, a department calendar that pulls in every module, search across the whole organization, and Workflows — an automation builder with approvals, test runs, and starter templates.
- One secure identity per member
- Access granted action by action
- Every important change on record
Requests stuck in five inboxes
The dashboard puts pending approvals from every module in one queue, with how long each has been waiting.
Dates scattered across tools
One calendar layers shifts, training, interviews, meetings, and department events — each filtered to what the viewer may see.
Repetitive admin busywork
Workflows run department processes on their own, with approval steps, simulated test runs, and a run history.
Inside the module
A closer look at Core.
Real screens from Station Clipboard, shown with a sample department.
01
Everything waiting on you
Required reading and pending approvals from every module, oldest first.
- Approvals from every module
- Waiting time on each request
- Required reading pinned on top
02
Workflows builder
Triggers, waits, conditions, and actions in a readable outline.
- If / otherwise branches and waits
- Event, schedule, button, or webhook triggers
- Live workflows show what they are watching
03
Starter templates, live
Installed templates with their last run and next scheduled run.
- Live, draft, paused, archived counts
- Last run result on every workflow
- Approvals and run history tabs
04
Action-level permissions
Roles with their own color and icon, and a permission editor grouped by module.
- Role colors and icons
- Permissions grouped by module
- Protected full-access role
05
Personnel directory
Every member with station, roles, and who is on the portal right now.
- Who is on the portal now
- Search, filter, and bulk edit
- Email members from the Outbox
On the phone
Your day on a phone
Module shortcuts and a to-do list of what needs the member.
How it works
From setup to a record you can trust.
Set up the department
Add your logo and branding, module colors, timezone, 24-hour time, station and apparatus lists, and an optional 2FA requirement.
Add people and roles
Invite members, assign roles from templates with their own color and icon, and track certifications with expiry reminders.
Communicate
Publish announcements and email named members or whole roles — now, later, or on a repeating schedule.
Automate
Install a starter template or build a workflow, test it with every effect simulated, publish it, and watch its runs and approvals.
Capabilities
Everything Core includes.
Role-based permissions
Role templates, cloning, colors and icons, and a grouped editor. Effective access is the union of a member’s roles.
Personnel directory
Profiles, custom fields, bulk edit, who is on the portal now, and a Certification Hub with expiry reminders.
Dashboard
Pending approvals from every module, required reading, and a to-do list, with widgets each member can arrange.
Dept Communications
Announcements with priority, audiences, scheduling, pinning, and acknowledgement tracking, plus scheduled and recurring email with logs.
Department calendar
Month, week, and phone views; recurring events, categories, RSVP, reminders, a personal feed for phone calendars, and private import of a member’s own calendar.
Organization search
Press Ctrl K to find people, records, and pages across every module the member can see.
Workflows
Triggers from across the modules, approvals, schedules, signed incoming webhooks, starter templates, and test runs where nothing is sent, written, or called.
Security and oversight
Authenticator-app or email 2FA, a logged “view as member” mode, and an activity log with actor, target, and severity.
Part of one portal
Works with the rest of your department.
Members keep one secure sign-in and one set of role permissions across every module you turn on.
Questions
Core FAQ
Is Core required?
Yes. Core is always on — every other module relies on it for sign-in, personnel, roles, and department isolation.
Can members see each other’s records?
Only if a role grants it. “Own” and “all” access are always separate permissions.
Can an automation change records its author could not?
No. Steps that change records check, when the workflow is saved, that its author holds the permission for that action.
Does a member’s personal calendar become visible to the department?
No. A calendar a member connects is shown only to them, and nothing from it is published anywhere.
See Core with your department’s workflow.
Tell us how you handle this work today. We’ll walk you through it in the full Station Clipboard portal.
Need something we don’t have yet? We build custom modules.
