Home
Genetec ClearID User Guide
Learn how to set up and use ClearID in Security Center SaaS.
Managing identities and users
Learn how to manage identities and users.
About identity request workflow
An identity request workflow is a series of activities performed by the system or authorized people during the life cycle of an identity request. The activities can create an individual identity, or multiple identities using a CSV import, and add each new identity to a role to inherit relevant access for a specified period.

Deployment guide
Learn how to install and connect your Security Center SaaS application.
User guide
Learn about Security Center SaaS.
Genetec ClearID User Guide
Learn how to set up and use ClearID in Security Center SaaS.
- Getting started
  Learn about the ClearID self-service physical access management solution.
- Requirements
  Check your compatibility and deployment requirements.
- Managing identities and users
  Learn how to manage identities and users.
  - About webhooks
    A webhook is a user-defined HTTP callback. A webhook can be triggered by an event in a web application and can be used to send data or notifications to a third-party Application Programming Interface (API).
  - Creating webhooks
    You can create webhooks in Genetec ClearID™ to integrate with third-party solutions APIs so that you can notify interested parties when specific events occur.
  - Viewing webhook logs
    To troubleshoot unreceived webhooks or other associated issues, third-party Application Programming Interface (API) owners can use the webhook logs to verify the status of every HTTP callback request sent to the third-party URL.
  - Granting access to the web portal
    Before a user can access the Genetec ClearID™ web portal, you must grant them the required User or Administrator permissions for the website.
  - About access request workflow
    An access request workflow is a series of activities performed by the system or authorized people during the life cycle of an access request. The activities can change the state and properties of access requests, affect other entities in the system, or wait for a condition to be met.
  - About email notifications
    To inform users about specific events in the Genetec ClearID™ system, email notifications are sent.
  - About identity request workflow
    An identity request workflow is a series of activities performed by the system or authorized people during the life cycle of an identity request. The activities can create an individual identity, or multiple identities using a CSV import, and add each new identity to a role to inherit relevant access for a specified period.
  - About custom fields
    A custom field is a user-defined property associated with an entity type. Custom fields are useful for storing additional information.
- Managing sites
  Learn how to manage sites.
- Managing areas
  Learn how to manage areas.
- Managing visitors
  Learn how to manage visit requests and access requests.
- Managing visitor watchlists
  Learn how to manage visitor access using watchlists.
- Synchronizing data
  Learn how to connect ClearID to other systems.
- Self-Service Kiosk
  Learn about the ClearID Self-Service Kiosk mobile app that simplifies visitor management and check-in.
- Troubleshooting
  Troubleshoot common issues that can occur.
Additional resources
Review the supported device list and other resources.
Glossary

About identity request workflow

2024-08-02

An identity request workflow is a series of activities performed by the system or authorized people during the life cycle of an identity request. The activities can create an individual identity, or multiple identities using a CSV import, and add each new identity to a role to inherit relevant access for a specified period.

The workflow helps automate tasks like approving or rejecting identity requests freeing up time to focus on other tasks.

The following diagram illustrates the identity request workflow that occurs in Genetec ClearID™.

¹ (Optional) Supervisor approval can be enabled and disabled for each identity template.

² (Optional) Identity approver approval can be enabled and disabled for each identity template.

³ (Optional) Email address must be unique in the system.

⁴ (Only if applicable) Cardholder is added to corresponding cardholder group in Security Center SaaS.