> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/accessnow-user-guide/workflow-creation/workflow-examples/access-workflows.md).

# Access Workflows

{% hint style="warning" %}
All processes are examples only and can be adjusted to customer needs.
{% endhint %}

{% hint style="info" %}
Email Notifications can be sent to relevant parties at selected stages of a workflow. 
{% endhint %}

## Access Request 

A new access request is needed when an employee changes roles, joins a new project, or requires additional resources that were not part of their initial access privileges. It ensures they have the necessary permissions to perform their work efficiently.

1. **Select Access Group:** Employee selects the appropriate access group(s) from the options below. You may request more than one area in a single submission.

{% hint style="info" %}
Access Groups for secure areas can be removed from the list of areas available for employees to select.
{% endhint %}

2. **Approval Process:** Submit an access request. The request is sent to the relevant area approvers. Only one approver needs to review and approve the access request.
3. **Access Provisioning:** Once approved by the area owner, access is automatically granted to the employee.

<figure><img src="https://3605010251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOxYzVrszbXcNBUauC0e%2Fuploads%2FlApBtna9V3abdEQtfxSF%2Fimage.png?alt=media&amp;token=922af899-7ee5-48dd-b0ec-10d0f0baa8a1" alt=""><figcaption></figcaption></figure>

## Access Audit & Removal&#x20;

The access review process is a crucial security measure designed to ensure that only authorised individuals have access to specific areas. This process is needed to mitigate the risk of unauthorised access and to maintain organizational security.&#x20;

It ensures compliance with security policies. Reduces potential security breaches by removing unnecessary access rights. And keeps the access list up-to-date with current personnel requirements.

1. **Kick-off the review:** Area managers may be responsible for conducting a periodic review of people with access to their managed area.&#x20;
2. **Occupants removal from access group:** During this review, area owners can remove individuals who no longer require access.
3. **Occupant notification:** When an individual is removed, they receive an email asking if they still need access.&#x20;
4. **Optional occupant response:** To retain access, notified occupants must respond in AccessNow with a valid reason. Otherwise the access is automatically removed.&#x20;

<figure><img src="https://3605010251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOxYzVrszbXcNBUauC0e%2Fuploads%2FuP4o9r9TTQbRcW0opuYo%2Fimage.png?alt=media&amp;token=bae23a63-600d-43db-b73d-d54fcd964f04" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/accessnow-user-guide/workflow-creation/workflow-examples/access-workflows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.