Notifications & Tags

Create, manage, and track organisational notifications and tags sent to users.

Administrative interface for creating notifications and tags, configuring who receives them, tracking acknowledgement status, and managing tag lifecycles. Accessible from both Organisation and QSS sections depending on your permissions.

1 What's on this page

The Notifications & Tags page is the administrative interface for creating and managing notifications sent to users throughout your organisation. Administrators use this page to create safety alerts, operational updates, policy notifications, and other important communications that require user acknowledgement. You can search existing notifications, track who has acknowledged them, and manage their lifecycle from creation through deactivation.

What you see here
  • Search bar: Find notifications by tag number, name, type, or issuing user
  • Active/Deactivated toggle: Switch between viewing active and deactivated notifications
  • Add new tag button: Create new notifications and tags
  • Notifications table: Comprehensive list of all notifications with management actions
  • Filter controls: Refine the list by issued by user and tag type
  • Pagination: Navigate through multiple pages when you have 16+ notifications
Key concepts
  • Notifications/Tags: Messages requiring acknowledgement from specific users or roles (terms are interchangeable)
  • Tag Types: Predefined categories with colour coding, deadlines, and sign-on restrictions
  • Effective dates: The date range during which a notification is valid
  • Acknowledgement tracking: System tracks which users have read and acknowledged each notification
  • Active vs Deactivated: Active notifications are visible to users; deactivated ones are archived

2 Create a new notification

To create a new notification, click the Add new tag button in the top-right corner of the page. This opens a window where you configure the notification details, recipients, attached documents, and optional custom form fields.

Tag details section
Required notification information
Field Description Required
Tag type Select the category of notification. Tag type determines colour coding, deadlines, and whether it restricts sign-on. Tag types are configured in Organisation/QSS Settings. Yes
Tag name The title or subject of the notification. This is the primary identifier users see in their notification list. Yes
Effective from The date when the notification becomes active and visible to users. Cannot be in the past. Yes
Valid until The end date of the notification. Leave blank if the notification has no end date. Must be after the effective from date. No
Users don't need to acknowledge after valid until date Checkbox that appears when a valid until date is set. If checked, users who haven't acknowledged the notification by the end date won't be required to do so. No
Notification details The full text content of the notification. This is the message users read when they open the notification. Can contain detailed instructions, safety information, policy changes, etc. Yes
Applies to section

Configure who receives the notification by selecting roles and/or specific users:

  • Applies to all users: Checkbox to send to everyone in the organisation
  • Roles selector: Multi-select dropdown to choose which roles receive the notification (e.g., Flight Crew, Maintenance Staff, Administrators)
  • Users selector: Multi-select dropdown to choose specific individuals by name

You can combine roles and specific users. For example, send to all Flight Crew plus a few specific maintenance personnel. If "Applies to all users" is checked, role and user selections are ignored.

Attached documents section

Optionally attach documents to the notification:

  • Click Add document to upload files
  • Each document displays with a name field and delete button
  • Check Require opening of documents to prevent acknowledgement until all documents are opened

Common attached documents include safety bulletins, policy updates, procedure changes, training materials, or reference documents. When "Require opening of documents" is checked, users must open and view each attached document before they can acknowledge the notification.

Custom form fields section

Add optional form fields that users must complete when acknowledging:

  • Click Add field to create a custom field
  • Choose field type: text, dropdown, date, user selector, or airport selector
  • Provide field label and mark as required or optional
  • For dropdown fields, add the list of options

Use custom fields to collect feedback, confirm understanding, or gather specific information (e.g., "Date you completed the training", "Select your base", "Provide comments").

Submitting the notification

When ready to save, use the Submit dropdown button to choose how to publish:

  • Submit: Save the notification without sending email alerts
  • Submit & Send Emails: Save the notification and send email alerts to all recipients immediately

Choose "Submit & Send Emails" when you want recipients to be notified immediately by email. The notification will be visible in the system regardless of which submit option you choose.

4 Edit a notification

Click the blue edit button (pencil icon) in the Edit column to modify an active notification. The same window used for creating notifications opens with all current values populated.

What can be edited

Before any acknowledgements, you can change:

  • Tag type (affects colour, deadline, sign-on restrictions)
  • Tag name
  • Notification details text
  • Recipients (roles and users)
  • Attached documents (add or remove)
  • Custom form fields (add, remove, or modify)
  • Email notification settings
Edit effective dates

Effective dates have special editing rules because they affect when users see the notification:

  • Click the pencil icon next to the effective dates in the table
  • A small window opens to change effective from and valid until dates
  • You can edit dates even after acknowledgements (unlike other fields)
  • Extending the valid until date gives users more time to acknowledge
  • Changing effective from affects deadline calculations

Editing effective dates is useful when deadlines need extension or when a notification's relevance period changes.

5 Copy a notification

The copy feature duplicates an existing notification with all its settings, saving time when creating similar notifications. Click the copy button (copy icon) in the Copy column.

What gets copied
  • Tag type: Same category and colour
  • Tag name: Identical name (you should change this)
  • Notification details: Full text content
  • Recipients: Same roles and users
  • Attached documents: References to the same documents
  • Custom form fields: Same field definitions
  • Email settings: Same notification preferences
What doesn't get copied
  • Tag number: A new unique number is generated
  • Effective dates: You must set new dates
  • Acknowledgement data: Starts fresh with no acknowledgements
  • Issued by: You become the issuer of the copy

6 Track acknowledgement status

The Status column provides real-time tracking of which users have acknowledged each notification. Click the button to open a detailed status window.

Status button badges
Green badge

Shows the count of users who have acknowledged the notification. These users have read the notification, viewed required documents (if any), and completed custom form fields.

Yellow badge

Shows the count of users who haven't acknowledged the notification yet. These users can see the notification but haven't opened it or completed acknowledgement.

Status detail window

The status window displays two tabs:

  • Users who have acknowledged: Table showing user names, acknowledgement date/time, and custom field responses (if any). View individual user responses by clicking their row.
  • Users who haven't acknowledged: Table showing user names and email addresses of users who can see the notification but haven't acknowledged it yet. Useful for follow-up.
Remove users from notification

From the status window, you can remove users from the notification's recipient list:

  • Select users using checkboxes in either tab
  • Click the Remove selected users button
  • Confirm the removal

This is useful when users were included by mistake, changed roles, or left the organisation. Removing users hides the notification from them immediately and removes their requirement to acknowledge.

7 Deactivate and reactivate notifications

Deactivating a notification archives it and immediately removes it from users' notification lists. Notifications can be reactivated if needed.

Deactivate a notification

Click the yellow deactivate button (ban icon) in the Deactivate column for an active notification:

  • Notification is moved to the Deactivated view
  • Users can no longer see or access the notification
  • Acknowledgement data is preserved for record-keeping
  • Unacknowledged users are no longer required to acknowledge
When to deactivate
  • Outdated information: Policy has changed or information is no longer relevant
  • Superseded: A newer notification replaces this one
  • Past valid until date: Notification period has ended naturally
  • Sent in error: Wrong recipients or incorrect information
  • Completed its purpose: Everyone who needed to has acknowledged
Reactivate a notification

Switch to the Deactivated view and click the green activate button (plus icon):

  • Notification becomes active again immediately
  • Users who hadn't acknowledged see it in their notification list again
  • Users who had acknowledged don't see it (already acknowledged)
  • Effective dates and deadlines apply as originally configured

Reactivation is useful if a notification was deactivated by mistake or if circumstances change and the notification becomes relevant again.

8 Generate reports

The Documents column provides export options to generate reports showing notification details and acknowledgement status.

Available report formats
PDF

Generates a formatted PDF report showing notification details, recipients, and acknowledgement status. Suitable for printing or filing.

Excel

Exports acknowledgement data to Excel spreadsheet. Includes user names, acknowledgement dates, and custom field responses. Good for further analysis.

Print

Opens a print-friendly view in a new window. Shows notification content and status summary, optimised for paper output.

Report contents

Reports typically include:

  • Tag number and name
  • Tag type and colour
  • Effective dates and deadline
  • Full notification text
  • Roles and users the notification applies to
  • List of users who acknowledged with dates
  • List of users who haven't acknowledged
  • Custom form field responses (if any)
  • Attached document list

9 Permissions and access control

Access to notification management features is controlled by role-based permissions. Different users see different capabilities based on their assigned permissions.

Permission levels
Notification permissions
Permission Level Capabilities
View only Can view the notifications page and see all notifications. Cannot create, edit, or deactivate. Cannot access acknowledgement status or remove users.
Edit own Can create new notifications. Can edit and deactivate notifications they created (before any acknowledgements). Can copy their own notifications. Can view status and remove users from their own notifications.
Edit all Full control over all notifications regardless of who created them. Can edit, copy, deactivate any notification (subject to acknowledgement restrictions). Can view all status details and remove users from any notification.
Display all tags Can see all notifications created by anyone in the organisation. Without this permission, users only see notifications they created themselves.

10 Tag types configuration

Tag types are predefined categories that control notification behaviour, appearance, and urgency. Tag types are configured separately in Organisation/QSS Settings and then selected when creating notifications.

Tag type properties
  • Name: Category name (e.g., "Safety Alert", "Operational Update", "Policy Change")
  • Colour: Red, Yellow, Green, or custom colour for visual categorisation
  • Description: Explanation of when to use this tag type
  • Restrict sign-on: If enabled, users cannot sign on for duties until they acknowledge notifications of this type
  • Deadline: Number of days after effective date by which users must acknowledge
Standard colour meanings
Red

Urgent safety alerts, critical operational updates, or mandatory compliance notifications requiring immediate attention. Often used with sign-on restrictions and tight deadlines.

Yellow

Important notices, policy updates, or operational changes that require awareness. Standard deadlines and acknowledgement tracking without sign-on restrictions.

Green

General information, updates, or confirmations. Often used for acknowledgement tracking without strict deadlines or sign-on restrictions. Informational purposes.

Navigation
Settings

Theme


Other settings coming soon...

An unhandled error has occurred. Reload 🗙
Interactive features loading...