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

Managing global events

The following section describes how to manage global events.

Create a Global Event

To create an Global Event:

1. Create a new event as usual

2. Go on duty and select the event

3. Edit the event to open the event settings

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

5. Select a Security Mode:

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

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

6. Save

Change an Event to or from a Global Event

Caution:

Changing the global status of an event can expose, previously restricted, sensitive data.

Always verify the reason for the change and ensure appropriate access controls are in place.

To remove a global event or make an event global

• Edit the event

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

• 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.

This can be set up in one of two ways:

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

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

The key difference is policy-based matching means the data is always available, while duty-based matching means it's 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.