On this page
| Table of Contents | ||
|---|---|---|
|
Overview
| Panel |
|---|
Global events are workspaces that are used to store information to be accessed across multiple events. Examples of records that use global events are operating procedures, documents and contact lists — in these cases, users can access this information regardless of the event they are working on, and the information remains active irrespective of when regular events are opened or closed. |
...
Administrators can create additional global events to provide private workspaces for key positions.
When to use global events
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.
...
Global events replace the concept of "Agency Workspaces" in Crisisworks 3.
When not to use global events
| Warning |
|---|
Global events are not for incidents. For any real emergency, use a normal event instead. |
Creating global events
To create a global event:
...
See Setting an event for more instructions on setting up an event.
Securing 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.
...
Note that any built-in global events (such as "Council Workspace" and "Global Workspace") can have positions added, but positions cannot be removed.
| Anchor | ||||
|---|---|---|---|---|
|
Records in global events are integrated into the register views used for managing normal events, so global and non-global records appear in the same list.
...