Appearance
Junto-Built Workspaces
Not every Workspace starts from a blank prompt. On the Workspaces launchpad, the Junto-built workspaces section holds scheduled routines that check your clients' environments and surface the exceptions that need attention. This is the Audits capability, surfaced inside Workspaces.
The difference from the Workspaces you build yourself: the detection logic is Junto's, not yours. As the in-app note puts it:
Junto-built workspaces run detection logic our team writes and maintains: per-client standards, license and role awareness, exclusion rules, and write-back into your PSA and RMM. You can set the schedule, the client scope, and what they trigger, but the detection itself is not something you can author in the composer.
Access
Junto-built workspaces are available when the feature is enabled for your organization. Anyone can view them, but creating one, activating it, and running a pass are admin-only actions.
How They Work
- Scan: On a schedule you set, the routine runs a single pass across every company in scope, reading the current state from your connected tools.
- Findings: Each device or user that fails the check becomes one finding. Entities that pass are counted as compliant.
- Response: What happens when a finding opens is configured per company: do nothing, open a ticket, or run a runbook. Nothing fires until you set a response.
- Track: Findings move through a lifecycle (New → In progress → Needs attention → Resolved), and everything is kept on record.
Detection detects; runbooks act. A Junto-built workspace only reads. It can't change a device, user, or ticket on its own. Any change happens through the response you configure, and only through a runbook or ticket you've chosen.
What You Can Configure
You don't write the detection, but you control how and where it runs:
- Schedule: Hourly, Daily, Weekly, Monthly, or Every N days (default Monthly).
- Scope: Global (every company in scope, shown with a globe icon) or a single company. You can add companies, and enable or disable the routine per company.
- What it triggers: the response when a finding opens, either report it, open a ticket, or run a runbook.
Each card on the launchpad shows the routine's schedule and current status ("N need attention," "All clear," or a count of acknowledged and in-progress findings), and a Paused badge when it isn't running. Use Add workspace to create one from a template. Creating a Junto-built workspace requires Admin+.
What They Can Detect
Junto-built workspaces start from a template. The available templates are:
| Template | What it checks | Works with |
|---|---|---|
| Patch compliance | Devices with operating-system patches that are approved or pending but not installed | NinjaOne, ConnectWise RMM, Syncro, Datto RMM |
| MFA coverage | Licensed users and admin-role holders without a registered second factor | Microsoft 365, Google Workspace, CIPP |
| Offline devices | Devices that haven't checked in to the RMM for a set number of days (default 30) | NinjaOne, Datto RMM, ConnectWise RMM |
A new routine starts Inactive and won't run until you activate it. Before activating, you can use Run test pass, a dry run that reports how many findings it would emit and shows a sample, without creating any findings, tickets, or runbook runs.
Go Deeper
The detection routines have their own full documentation, including how findings progress and how to configure responses:
- Creating & Scheduling Audits: start from a template, set the schedule and scope, and activate.
- Findings & the Risk Ledger: how findings progress, and how to acknowledge or suppress them.
- Configuring Responses: decide what happens when a finding opens.
Next Steps
- What Are Workspaces?: the Workspace surface, inspector, scheduling, and sharing.
- What Are Audits?: the detection capability behind Junto-built workspaces.