Quick Approve is a shortcut action shown on request lists when the current user can approve a request without opening the full approval page.

Quick Approve appears when the request is waiting for approval from the current user and the approval can be completed immediately.

It is only shown when all of the following are true:

the request has a current approval action for the signed-in user

the approval does not require the user to update or complete fields before approving

the user is not included as an information-only user

the user is not impersonating another user

the Quick Approve action is enabled in the request list/menu configuration

Quick Approve is hidden when any of the following apply:

the user is not an approver for the current approval step

the approval requires the user to review or update additional information before approving

the user is only included for information purposes

the user is impersonating another account

the Quick Approve option has been removed or disabled in the menu configuration

the user does not have the required access to view or act on the request

The recommended way to disable Quick Approve is to make the approval step editable.

 is enabled, approvers must open the request before approving it. This prevents the Quick Approve shortcut from appearing in the request list.

Quick Approve is designed for simple approval steps only. It is not shown when the approval step requires the approver to update the request before approving.

This helps prevent users from bypassing approval screens where extra information, review fields, or decision context are required.Quick Approve

Quick Approve lets an approver approve a request directly from the request list, without opening the full approval page.

It is intended for simple approval steps where the approver only needs to approve the request. If the approval step requires the approver to open the request first, Activate hides Quick Approve.

Quick Approve appears when the request has a current approval action for the signed-in user and the approval can be completed without opening the request.

It is shown only when all of the following are true:

the signed-in user is an approver for the current approval step

the signed-in user is not an information-only user for the approval step

the signed-in user is not impersonating another user

Quick Approve is hidden when any of those conditions are not met.

the request is waiting on a different approver

the user is included for information only

an administrator is impersonating another user

Disabling Quick Approve does not stop the user from approving the request. It only removes the list-level shortcut.

If the user is still an approver, they can open the request and approve it from the normal approval screen.

How to use the catch node in Activate workflows

Quick Approve

Microsoft’s cloud platform providing infrastructure, networking, storage, and application services. In Activate, it’s used as the hosting environment or for integration with Microsoft 365 and Entra ID services.

Azure

DotNetVersion

Microsoft Entra Connect (formerly Azure AD Connect) is a tool that syncs on-premises Active Directory identities with Microsoft Entra ID, enabling hybrid identity and seamless access to cloud resources.

Microsoft_Entra_Connect

Active Directory (AD) is Microsoft’s directory service that stores and manages user accounts, devices, and permissions, enabling secure authentication and centralized access control within a Windows network.

Active_Directory

ActivateJobService

ActivateAdministrator

SupportedPowerShellVersions

SupportedOSVersions

SupportedSQLVersions

Name that identifies the instance of Activate.  This is only used by Administrators and isn't displayed to end users.

instance_name

An installation type of Activate where there is no local domain connection, all authentication, authorisation and identity management is handled by Entra ID.

Cloud_Only

Microsoft Entra ID (formerly Azure Active Directory) is Microsoft’s cloud-based identity and access management service, providing secure authentication, user lifecycle management, and access control for Microsoft 365 and other apps.

Microsoft_Entra_ID

A software switch that enables or disables functionality at runtime without redeploying code. In Activate, they are configured under //Resources/Configuration/FeatureFlags.

feature_flag

Microsoft module for managing Exchange Online, using modern authentication and REST API–based cmdlets for faster, more reliable automation of mailboxes, compliance, and organisation settings.

EXO_V3_PowerShell_Module

An Organizational Unit (OU) is a container in Active Directory used to organise users, groups, computers, and other objects within a domain. OUs help structure resources logically and apply group policies for easier management and administration.

A User Type is a template in Activate that defines rules, attributes, and behaviours for a category of users (e.g., Employee, Contractor), ensuring consistent user account setup and configuration.

User_Type

A resource object in Activate representing a physical or virtual Exchange Server

Exchange_Server_Resource

Defines the object type that the resource will emulate or operate as.

Class_parameter

Clonesthe selected inherited parameter to make a local copy to override the value

Override

Runs the Activate Provisioning Server and performs actions across target systems.

Orchestrator_Account

A complete, immutable log of identity-related events, including provisioning actions, access approvals, and policy evaluations.

Audit_Trail

An integration module that enables Activate to read/write data from external systems (e.g., provisioning accounts in Azure AD).

Connector

A periodic process where managers or data owners validate that users still require their existing access — critical for compliance.

Access_Certification_and_Review

A user-initiated process to gain access to new systems or roles, often requiring manager or system owner approval.

Access_Request

Any downstream application or service where identities need access (e.g., Active Directory, Okta, Salesforce).

Target_System

The authoritative system from which identity data is imported (e.g., HRIS like Workday or SAP SuccessFactors).

Identity_Source

An access control model that uses user, resource, or environment attributes (e.g., department = "HR", location = "US") to make access decisions dynamically.

ABAC_Attribute-Based_Access_Control

An access control model where users receive permissions based on assigned roles. This model helps enforce least privilege.

RBAC_Role-Based_Access_Control

A collection of entitlements assigned based on a user’s job function or department. Roles simplify access management and are often tied to policies (e.g., "Finance Analyst Role").

Role

A specific access right or permission within a system (e.g., "Read-only access to Salesforce Reports"). Entitlements can be grouped into roles.

Entitlement

The removal or disabling of user accounts and access when they are no longer required — for example, when an employee leaves the organization.

Deprovisioning

The automated process of creating accounts and granting access to systems or applications based on a user’s role or attributes.

Provisioning

A digital representation of a user (employee, contractor, service account, etc.) within an organization. Each identity is typically linked to a unique identifier, such as an email address or employee ID.

Identity

This is the process of bringing on a new user

Onboarding

Hierarchical Role-Based Provisioning automates user access by assigning roles based on organisational structure, ensuring users inherit the correct permissions and resources aligned to their position or function.

Hierarchical_Role-Based_Provisioning

A group email address that automatically forwards messages to all its members, allowing you to send emails to multiple recipients at once.

Distribution_List

An expression is a conditional statement using Activate expression syntax.

expression