Skip to main content
Solved

View All Automated Workflows in the System

  • May 26, 2026
  • 1 reply
  • 9 views

I am an Admin User, currently looking to document all the workflow automations in our Sandbox instance. Is there a way to view all the workflow automations currently active? 

In my document describing the automated workflows, I am also planning to add brief notes on each workflow, with details of when they are triggered and what they achieve.

Any expert advice will be appreciated.

Best answer by dkreiger

Hi ​@asubramaniam, Yes — you can view “all workflows” centrally in Automation Center

As an admin, the closest thing to a tenant-wide inventory is the Workflow Automation (Automation) Center, which acts as an enterprise workflow library and shows all workflows that exist in the instance along with their current status.

Where to go

  • Use the app switcher → Automation Center, or go to Admin Console → Platform Tools → Automation Center.


What you’ll see there

  • A list of all workflows in the instance, and each workflow shows its status plus who created it and when.
  • When you click a workflow, the right-side “inline view” shows the workflow’s scope, trigger, conditions, and actions in a read-only specification-style view—which is very handy for documentation.


This is typically the best place to document “everything that’s currently configured,” and to identify which workflows are Paused/Active/Archived, etc.

 

To see what’s active for a specific Position/Community pipeline (runtime view)

If your goal is “what automations are currently running for this job/community,” you can check from inside that pipeline:
 

  • Open the Position or Community pipeline page
  • Open the Automated Workflows side panel/tab
  • Review the list of workflows that are active there (grouped by type, with toggles where allowed). 


Notes:

  • Required global workflows may show as locked and can’t be disabled from the pipeline.
  • Disabling/enabling from here affects that specific pipeline context (job/community), which is useful when documenting “enabled in sandbox for Position X.” 

 

For your documentation notes (trigger + “what it achieves”)

A practical way to build your doc using what the product already exposes:
 

  • Use Automation Center’s inline workflow specification to capture:
    • Trigger
    • Conditions
    • Actions (what it accomplishes)
  • If you want an exportable artifact of workflow activity/performance, Workflow Automation also supports downloading a workflow report (CSV) from the Automated Workflows area.

1 reply

dkreiger
Community Manager
  • Community Manager
  • Answer
  • May 27, 2026

Hi ​@asubramaniam, Yes — you can view “all workflows” centrally in Automation Center

As an admin, the closest thing to a tenant-wide inventory is the Workflow Automation (Automation) Center, which acts as an enterprise workflow library and shows all workflows that exist in the instance along with their current status.

Where to go

  • Use the app switcher → Automation Center, or go to Admin Console → Platform Tools → Automation Center.


What you’ll see there

  • A list of all workflows in the instance, and each workflow shows its status plus who created it and when.
  • When you click a workflow, the right-side “inline view” shows the workflow’s scope, trigger, conditions, and actions in a read-only specification-style view—which is very handy for documentation.


This is typically the best place to document “everything that’s currently configured,” and to identify which workflows are Paused/Active/Archived, etc.

 

To see what’s active for a specific Position/Community pipeline (runtime view)

If your goal is “what automations are currently running for this job/community,” you can check from inside that pipeline:
 

  • Open the Position or Community pipeline page
  • Open the Automated Workflows side panel/tab
  • Review the list of workflows that are active there (grouped by type, with toggles where allowed). 


Notes:

  • Required global workflows may show as locked and can’t be disabled from the pipeline.
  • Disabling/enabling from here affects that specific pipeline context (job/community), which is useful when documenting “enabled in sandbox for Position X.” 

 

For your documentation notes (trigger + “what it achieves”)

A practical way to build your doc using what the product already exposes:
 

  • Use Automation Center’s inline workflow specification to capture:
    • Trigger
    • Conditions
    • Actions (what it accomplishes)
  • If you want an exportable artifact of workflow activity/performance, Workflow Automation also supports downloading a workflow report (CSV) from the Automated Workflows area.