> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/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/command-centre/accessnow-user-guide/workflow-creation/workflow-mapping/workflow-mapping-example.md).

# Workflow Mapping Example

## Example: New Employee Credential Request & Access Request

* **Trigger**: A new employee’s manager raises a request.
* **Steps**:
  1. Manager logs into the PIAM system and initiates a “New Employee Credential & Access”.
  2. Manager enters basic employee details, such as name and employee ID, and selects the desired access and schedule.
  3. System notifies the employee to provide additional details.
  4. Employee submits personal details and a photo.
  5. Relevant area approvers are notified of access requests.
  6. Area approvers review the request and grant or deny access to the areas they are responsible for.
  7. If access to an area is granted, the relevant access group is automatically provisioned in Command Centre for the new employee. Otherwise, access is not granted.
  8. The security team reviews the credential request. If it is approved, they print and encode the card with the employee details.
  9. The employee is notified that the credential is ready for pickup.
  10. Employee picks up the credential in person, with identity verification.
  11. Security staff activates the credential.
* **Considerations**:
  * Can employees self-initiate requests, or is it manager-only?
  * Consider whether the employee record is already available in Command Centre before the request is made. The cardholder must already exist in Command Centre for security reasons.
  * Define required fields the manager and employee respectively have to enter:
    * Manager: employee name and ID, access options, schedule (e.g., days/times);
    * Employee: photo size and format, pickup locations if available, identification type or number, and so on.
  * Specify who the area owners, or approvers, are for each access group that can be provisioned through this request.
  * List all available credential pickup options, if applicable.
  * Detail identity verification at pickup (e.g., ID check).
  * Consider what happens if credential or access requests are declined. Is a reason for the rejection required? Who has to be notified?


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.security.gallagher.com/command-centre/accessnow-user-guide/workflow-creation/workflow-mapping/workflow-mapping-example.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.