Get started with Safety Hub
Safety Hub is Pilotbase's unified safety product. This article walks you through first-time setup as an FSP administrator.
For a feature overview, see the "Introducing Safety Hub" article.
Before you begin
You need FSP administrator access to complete this setup.
Step 1 — Grant SMS permissions
Safety Hub uses a FSP permission packs to grant access and who can perform actions in the hub. You assign them per role in FSP.
In the FSP shell, go to Settings → Users → Roles & Permissions.
Select a role and click Edit Role, then open the Permissions tab.
Under the Safety Hub section, enable the permissions appropriate for that role. At minimum, every user who needs SMS access requires Access Safety Hub.
Click Save.
Repeat for each role in your organization. For a full permissions reference, see the "Safety Hub permissions overview" article.
Required permissions by common role
Role | SMS minimum |
Safety Manager | All 10 Safety Hub permissions |
Safety Officer | Access + Manage Reports/Hazards/CAs + View Analytics |
SMS visibility is separate from capability. A permission grants what a user can do. What records they can see depends on Safety Team membership (set up in Step 3). Grant both to give a user full access.
Step 2 — Flag Safety Team members in FSP
Anyone you plan to designate as Accountable Executive, Safety Manager, or Safety Team member must be flagged on their FSP user record first. Safety Hub reads this flag to populate its people pickers.
In FSP, open the user's profile, then Online Access.
Enable the Safety Officer flag.
Save.
If a person is missing from a Safety Hub people picker, check that this flag is set on their FSP record.
Step 3 — Set up the Safety Team
The Safety Team controls SMS record visibility. Users only see records routed to teams they belong to — except the Accountable Executive and Safety Managers, who see all records across the operator.
In Safety Hub, go to Settings → Safety Team.
Designate one Accountable Executive (required; FAA Part 5 mandates exactly one). This is a single-select picker.
Add one or more Safety Managers using the people search. Each Safety Manager receives visibility bypass across all teams. Managers appear as removable chips.
Set the Safety Team Inbox email address. This is the address reporters use to reach your safety team, and it is shown as the contact on report status pages.
Create a Safety Team for each location. Add members and optionally set a default assignee (must be a team member). A default team — shown as "All other locations" — catches any location without its own team.
Incoming safety reports auto-route to the team matching the event's location.
For detailed Safety Team configuration, see the "Configure the Safety Team" article.
Step 4 — Configure SMS settings
With the Safety Team in place, configure the SMS module's core settings. Settings → SMS now organizes these into six tabs: General, Statuses, Forms, Hazards, Corrective Actions, and Documents.
In Safety Hub, go to Settings → SMS.
On the General tab, edit the 5×5 risk matrix (Likelihood × Severity). Click any cell to change its risk level, and click a label to edit its description. This tab also holds the Operational Areas manager — add, edit, set a default, or archive areas. The defaults follow FAA AC 120-92D (Aerodrome, Air Navigation, Operations, Maintenance, Design & Manufacturing).
On the Statuses tab, review or adjust the status workflows for Safety Reports, Hazards, and Corrective Actions.
On the Forms tab, configure your Safety Report form. If you want external reporters to submit without logging in, enable public submission — this generates a shareable link. Reporters receive a Report ID to check status later.
Use the Hazards, Corrective Actions, and Documents tabs to configure the taxonomies (types, categories, folders) for each of those modules.
Click Save on each tab after making changes.
Step 5 — Configure FRAT settings
FRAT (Flight Risk Assessment Tool) requires its own settings before pilots can use it. Settings → FRAT keeps its three tabs: Risk Thresholds, Forms, and Mitigations.
In Safety Hub, go to Settings → FRAT.
On the Risk Thresholds tab, define how risk scores map to named risk levels. You can add custom bands, rename levels, and pick colors. Per-form threshold assignments are set inside each form's builder.
On the Forms tab, build or review FRAT forms. Publish the form when ready.
On the Mitigations tab, configure available mitigations with risk-reduction point values.
Step 6 — Verify end-to-end access
Before rolling out to your team:
Open Safety Hub. Confirm the Safety Dashboard loads — a metrics-rich command center with a Needs Attention callout row, KPI stat tiles, and interactive charts. The left sidebar groups the nav into Safety Management (Safety Reports, Hazards, Corrective Actions, Documents, Analytics), Preflight (Risk Assessments, Weight and Balance), and Settings (FRAT, SMS, Safety Team).
Log in as a test user and confirm they see only the records and tabs their role permits.
Build your Safety Manual
Safety Hub now includes a Safety Manual builder. You author your manual in sections alongside an org profile, and Safety Hub generates a versioned library document with audit history and stored PDFs. Look for the Safety Manual builder alongside your other safety documents once your Safety Team and SMS settings are in place.
Troubleshooting
Issue | Likely cause | Fix |
User cannot open Safety Hub | Missing Access Safety Hub permission | Add permission in FSP → Roles & Permissions |
Person missing from Safety Hub people picker | FSP Safety Team member flag not set | Flag the user in FSP user record (Step 2) |
Safety reports not routing to a team | No Safety Team created for the location | Create a team for that location in Settings → Safety Team |