# Workflow Mapping Example

## Example: New Employee Credential Request & Access Request&#x20;

* **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 (e.g., name, employee ID)  and selects desired access and schedule.&#x20;
  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 have to reveiw the request and grant or dent access to areas theor responsible for.
  7. If access to an area is granted, relevant access group is automatically provisioned in Command Centre to the new employee.  Otherwise the access is not granted. &#x20;
  8. Security team reviews the request for credential. If the credential request is approved they print and encode the card with employee details. &#x20;
  9. Employee is notified that the credential is ready for pick up.&#x20;
  10. Employee picks up the credential in person, with identity verification.
  11. Security staff activates the credential.&#x20;
* **Considerations**:
  * Can employees self-initiate requests, or is it manager-only?&#x20;
  * Consider if the employee record is already available in Command Centre prior to making the request? Cardholder must already exists in Command Centre for security reasons. &#x20;
  * Define required fields the manager and employee respectively have to enter: &#x20;
    * Manager: employee name and ID, access options, schedule (e.g., days/times);
    * Employee: photo (size/format),  pick up locations if available, identification ID type or number, etc. &#x20;
  * Specify how who are the area owners (approvers) for each access group that can be provisioned via this request.&#x20;
  * List all available credential pick up options if they apply.&#x20;
  * 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?&#x20;


---

# 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://help.security.gallagher.com/command-centre/accessnow-user-guide/workflow-creation/workflow-mapping/workflow-mapping-example.md?ask=<question>
```

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.
