> ## Documentation Index
> Fetch the complete documentation index at: https://docs.porcia.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Pulses

> Proactive async outreach to employees to verify app usage — under Workflows → Pulses.

**Pulses** is under **Workflows → Pulses** in the sidebar at `/workflows/pulses`. It's Porcia's async employee outreach system — send targeted check-ins to verify whether people are still using a tool, need to export data before access is removed, or should take a specific action.

## The Pulses page

The Pulses page has a metrics strip at the top, then four tabs:

### Metrics cards

Shows at a glance: total pulses sent, response rate, active automations, and pending responses.

### History tab

Every pulse ever sent from your workspace — with status, send date, target audience, response breakdown, and a link to the full result. Use this to review what's been sent and follow up on non-responders.

### Automation tab

The list of active pulse automations (automated workflows that send pulses on a trigger or schedule). Each automation shows its name, trigger condition, target, last run, and on/off toggle.

This is where you set up recurring pulses — for example, "every month, send a check-in to anyone with an inactive account on any app with spend."

### Templates tab

Pre-built pulse templates for common scenarios:

* "Are you still using \[App]?"
* "Your access to \[App] will be removed soon. Do you need to export any data?"
* "We're reviewing licenses for \[App] ahead of our renewal. Do you still need access?"
* "Please confirm whether you still need your \[App] account."

Templates are fully customizable. Use one as a starting point or write your own.

### Audit Log tab

A complete log of every pulse action — sent, responded, snoozed, opted out, and any automated actions triggered by responses.

## When to use pulses

* **Before a renewal** — verify who still needs the tool before you decide how many licenses to keep
* **Inactive license cleanup** — confirm that low-activity users genuinely don't need access
* **Shadow IT review** — ask employees if they want to keep using an app before IT blocks it
* **Access review** — periodic confirmation that people still need their existing access
* **Offboarding** — give a departing employee a chance to flag data export needs

## How pulses work

<Steps>
  <Step title="Create a pulse">
    Choose a template or write your own question. Select the target audience — specific users, a directory group, or all users assigned to a specific app.
  </Step>

  <Step title="Choose delivery channel">
    Slack, Microsoft Teams, or email. For the best response rates, use Slack or Teams where employees are already active. Employees respond with button clicks — no typing required in Slack and Teams.
  </Step>

  <Step title="Set a deadline">
    Choose a response window. A reminder is sent automatically 24 hours before the deadline to anyone who hasn't responded yet.
  </Step>

  <Step title="Send or schedule">
    Send immediately or schedule for a specific date and time.
  </Step>

  <Step title="Review results">
    The History tab shows the response breakdown. Act on the results — remove access for users who said no, follow up with non-responders, or feed results into a playbook.
  </Step>
</Steps>

## Targeting

* **By app** — automatically targets all users with access to a specific app (from SSO data)
* **By group** — send to a directory group (department, team, or custom group)
* **By manual list** — paste specific email addresses
* **Via rule** — pulses can be triggered automatically when a rule fires (e.g. when login frequency drops below once per month)

## Acting on responses

From the pulse result view in the **History tab**:

* **Remove access** — select users who said "No" and act on their access directly
* **Send to playbook** — feed results into an offboarding or access-removal playbook
* **Export** — download results as CSV
* **Snooze** — for users who asked for more time, snooze and follow up later

## Response handling and opt-outs

Employees can snooze individual pulses (ask to be reminded later). Employees who want to stop receiving pulses entirely can opt out — their preference is stored and respected by future sends.

## Next steps

<CardGroup cols={2}>
  <Card title="Rules" icon="bolt" href="/governance/rules">
    Trigger pulses automatically on usage signals
  </Card>

  <Card title="Playbooks" icon="list-check" href="/governance/playbooks">
    Include pulses as offboarding workflow steps
  </Card>

  <Card title="Spend analytics" icon="chart-line" href="/features/spend-analytics">
    See the inactive/abandoned spend that pulses help you eliminate
  </Card>

  <Card title="Apps catalog" icon="building" href="/features/vendor-management">
    Act on pulse results to right-size licenses
  </Card>
</CardGroup>