For the complete documentation index, see llms.txt. This page is also available as Markdown.

Global Events

This page explains how to use Global events to store information for access across multiple events.

Overview

Global events are special type of event used to store information for access across multiple other events. These events remain accessible regardless of which event a user is currently working in.

Some common examples include:

  • Contacts - directories for shared contacts

  • Shared Workspaces that all users can access - for example the Library module in this event could hold documents that are relevant to everyone

  • Resources - available to all events

  • Rostering and availability - for all staff

Global events are useful for securely storing documentation, contact lists and other information that does not pertain to any specific incident or event. Data in global events are only accessible by users sharing a position that is attached to the event, meaning secure workspaces can be easily created.

Use global events if you want a private place to put contacts or library records that can only be seen by some positions which will be accessible across all events.

Security Modes

There are two security modes for Global Events:

  • Policy-based: Users need a have a position matching one in this event to access the data

  • Duty-based: Users must go on duty for a position in this event to access the data

Finding Global Events

You can identify Global Events in the Events Datagrid:

  • The Type column will say 'global' for any Global Events

  • The Special filter group contains the filter 'Global' which runs the CQL query special:isGlobal

Managing global events

Global events are managed like any other event, where you add and remove positions to the event to provide access. Unlike regular events, users cannot go on duty for global events, so security is granted immediately based on the user having a competency for any position added to the event.

Creating a Global Event

To create an Global Event:

  1. Edit the event to open the event settings

  2. In the Advanced section, tick This is a global event

  3. Select a Security Mode

  4. Save

Change an Event to or from a Global Event

To remove a global event or make an event global

  1. Find and View the Event

  2. In the Advanced section, change the This is a global event checkbox

  3. Check the Security Mode reflects the desired level of access

Global events, duties and security

Global events behave differently to regular events.

  • Users do not go on duty to global events

  • Global events are not selectable in the event selector

Rather than being segregated, global event data is displayed all the time, even when users selects and work in any other regular event. They are called global events because their data is available globally irrespective of the event a user is working within.

Securing global events relies upon matching its involved positions with a user's positions.

The Security Mode has two main options. The key difference is policy-based matching means the data is always available, while duty-based matching means it is based on a user's duty in another non-global event.

The most common use of global events is in creating a place to store and share long-term information — contacts, documentation, geospatial data, etc. These are commonly named "Workspaces".

In most cases, workspaces are best constructed using policy-based security, as it means users will see the data irrespective whether they are working in another event.

Adding Items to a Global Event

Users add items to Global Events using the Event setting.

Global Events are found indented under the heading 'Global' if Global Events are present.

The Global section of the Event setting

Last updated

Was this helpful?