# Global 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
{% hint style="warning" %}
Global events are not for incidents. The name does not imply a disaster that affects the whole globe. For any real emergency, do not create a global event.
Global events can not be selected in the event selector, nor in the manage duty Screen. This means users cannot go on duty for global events. Instead, users are automatically given access to global events whenever any of their competent positions match positions allocated to a global event.
{% endhint %}
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](https://docs.cw.crisisworks.com/system-administration/managing-events/..#finding-events):
* 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. [Create a new event](https://docs.cw.crisisworks.com/system-administration/managing-events/..#creating-a-new-event) as usual
2. [Go on duty](https://docs.cw.crisisworks.com/concepts-and-fundamentals/on-a-computer/working-with-events#setting-your-duties-for-events) and [select the event](https://docs.cw.crisisworks.com/concepts-and-fundamentals/on-a-computer/working-with-events#selecting-a-primary-event)
3. [Edit the event](https://docs.cw.crisisworks.com/system-administration/managing-events/..#event-settings) to open the event settings
4. In the Advanced section, tick **This is a global event**\
5. Select a [Security Mode](https://docs.cw.crisisworks.com/system-administration/managing-events/..#security-mode)
6. Save
### Change an Event to or from a Global Event
{% hint style="warning" %}
**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.
{% endhint %}
To remove a global event or make an event global
1. Find and View the Event
2. [Edit the Event](https://docs.cw.crisisworks.com/system-administration/managing-events/..#event-settings)
3. In the Advanced section, change the **This is a global event** checkbox
4. 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.
{% hint style="info" %}
Securing global events relies upon matching its involved positions with a user's positions.
{% endhint %}
The [Security Mode](https://docs.cw.crisisworks.com/system-administration/managing-events/..#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.
{% hint style="info" %}
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.
{% endhint %}
## Adding Items to a Global Event
Users add items to Global Events using the [Event](https://docs.cw.crisisworks.com/concepts-and-fundamentals/on-a-computer/using-the-datagrid/editing-items#event) setting.
Global Events are found indented under the heading 'Global' if Global Events are present.
The Global section of the Event setting
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.cw.crisisworks.com/system-administration/managing-events/global-events.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
