← All agent and harness briefs
Agent runtimeagenticopsdocumentedunattended capable

Operational brief

Dash

Process Street's shared operations teammate for Slack, Teams and the web, with configurable tool approvals and optional scheduled autonomy.

No product visual on file

Choose it when

You want reports and business-tool actions with per-operation Auto, Ask or Off controls, rather than a fixed approval rule for every write.

Skip it when

You need to host the runtime yourself or require an independently verified approval gate before every write, including autonomous tasks.

01 / Classification

Autonomy evidence

This is our classification, not a vendor badge. The record says what the product normally does. The gaps stay visible.

How we classify it
Tool use + multi-step plans, still human-gated per session.
Runs unattended
Yes — that capability is documented in this brief.
Trigger
Normally a person asks in chat. Optional cron-based schedules can run headlessly; only an admin can enable a task's autonomous mode to remove approval pauses. Browser-powered tasks are a separate, side-panel-dependent path.
State
Conversations retain context. Scheduled instructions are self-contained and reuse connections, skills and workspace memory, not a prior open chat. Memory reads span surfaces; memory writes exclude DMs, private channels and Chrome.
Tools
Connected tools can send email, post, update CRM and calendar data. Defaults are reads Auto, routine writes Ask and irreversible destructive operations Off; authorized changes can allow automatic writes.
Human control
Creator/admin or explicitly permitted delegates manage and pause tasks; delegated management doesn't change creator execution identity. The creator is notified when Chrome/credits prevent a start and skipped runs appear in Activity. Autonomous mode is suspended if the granting admin's role changes. Assign an owner to review runs; no universal automatic recovery guarantee.

02 / Operations

Control reality

Useful agents eventually touch something real. This is the operational picture we have, not a promise hidden in a sales page.

Where it runs
Managed service with vendor-deployed sandboxes and a web dashboard, not a locally operated runtime; Chrome-powered tasks also depend on the user's browser.
Data boundary
Shared workspace memory isn't shared private-chat visibility. The memory guide allows writes from public channels/web, and reads across surfaces. Chrome supplies current-page context while its side panel is open; no injection-proof or independently audited no-training claim is made here.
Identity & permissions
Access scope and tool mode are separate. Optional designated approvers narrow who may approve, but actions run as the original requester with access rechecked. Scheduled tasks run as their creator even when delegates manage them. New private mailboxes don't retroactively privatize existing ones.
What it can write
CRM and other connected-tool records · Email, channel posts and calendar actions under effective tool modes · Shared workspace memories from public channels and web conversations
Surfaces
Slack · Microsoft Teams · Web chat and dashboard · Chrome side panel · Managed sandbox · Connected tools / MCP
Export / lock-in
Sessions and stored memories can be reviewed, and memories edited/deleted in the dashboard. A complete portable workspace export isn't established by this source review.

03 / Receipts

Evidence ledger

Here is what this brief is built on. “Documented” means we found a source. “Tested” means this desk actually ran it. Those are different things.

Evidence status
documented
Source set
10 primary sources
Evidence review
2026-10-15

Sources on file

Corrections

  • 2026-10-15 · Removed the every-write approval promise and Slack/Teams-only fit. Primary use is chat-led with optional admin-enabled task autonomy. Added mutable run modes, requester/creator identity, browser-run dependencies and memory-write boundaries; not runtime-tested. Documentation update dates aren't release dates.

Desk notes

What we found

Useful context, not a substitute for the source record above. This is not a desk test unless the evidence status says tested.

Pick it for shared business-tool work with configurable controls; skip it if every write must always stop for approval.

Surface
Slack, Teams and web chat; Chrome side panel
Defaults
Reads Auto; routine writes Ask; destructive Off
Automation
Admin-enabled task autonomy; browser tasks need a side panel
Identity
Requester for actions, creator for scheduled tasks

What the vendor says

Detailed approval and scheduler guides qualify the homepage's blanket asks-before-writing language. Inspect effective modes, not just marketing copy; not runtime-tested.

Sources fetched 2026-10-15

04 / Change log

Related coverage

The brief tells you what the product is. Payloads track the changes that may alter the decision.

No linked change coverage on file yet.