Skip to content

What Are Workspaces?

A Workspace is where you build a report that spans your integrations. You describe what you want in plain language, and Junto pulls the data from across every connected system (your PSA, RMM, identity, security, backup, and billing tools) and assembles it into a single report. It keeps a durable record of everything it did along the way.

A Workspace isn't tied to a single data source. It can draw on any integration you've connected and combine them into one report, whether that's an internal operations view or a client-facing deliverable.

Once a report is in a good place, you can have it rerun on a schedule (daily, weekly, or monthly) and either keep the results in Junto or have them delivered to Slack, Microsoft Teams, or email.

Access

Workspaces are available when the feature is enabled for your organization. Starting a new Workspace requires manager-level rights. You'll see "A manager can start a new Workspace. You can continue existing work below." if you don't have them. Anyone can open and continue existing Workspaces.

The Launchpad

The Workspaces landing page opens on a composer with the placeholder "Ask Junto to research, create, or analyze anything…" Type your request, optionally attach files, and Junto gets to work.

Below the composer you'll find:

  • Your workspaces: recent and in-progress work you can jump back into. Use View all Workspaces to see the full list.
  • Junto-built workspaces: scheduled detection routines maintained by Junto's team (this is the Audits feature surfaced here).

When you start a Workspace, Junto auto-generates a title from your first request. Until it does, the Workspace shows as "Untitled workspace."

Working in a Workspace

Once open, a Workspace is a conversation with an inspector panel alongside it. The inspector organizes everything the Workspace produces into tabs:

TabWhat it holds
ArtifactThe deliverable Junto generated, for example an HTML report you can preview, or a CSV.
SummaryAn overview of the work: business context and schedule status.
ActivityThe run timeline: each step Junto took, and the state of the current run (queued → running → succeeded).
FilesFiles you attached as input, plus the output files the Workspace produced.
ScheduleRecurring-run configuration, when scheduling is enabled.

Attaching files

You can attach files to a request. For example, drop in a CSV and ask Junto to analyze or cross-reference it. Attached files show up under the Files tab alongside anything the Workspace generates.

Running and Scheduling

A Workspace can run on demand whenever you open it and send a request. Many kinds of work are worth repeating, so a Workspace can also be put on a schedule that reruns it and delivers the result automatically.

A schedule has three parts:

  • Cadence: how often it runs (for example, Daily).
  • Deliverables: which artifact to send.
  • Destinations: where to send it, either Email, Slack, or Microsoft Teams. Each destination must be connected and enabled for your organization. You can also send a snapshot link by email.

A Workspace has one active schedule at a time.

Sharing

Workspaces are private to their owner. When you want to hand a result to someone, share the individual artifact rather than the whole Workspace:

  • Copy snapshot link: creates a read-only link. Anyone with the link can view this read-only snapshot.
  • Download: save the artifact (for example, the HTML report or CSV) to send however you like.

Junto-Built Workspaces

Alongside the Workspaces you create, the launchpad also lists Junto-built workspaces: scheduled detection routines authored and maintained by Junto's team (this is the Audits feature). You control their schedule, scope, and what they trigger, but the detection logic itself is written and maintained by Junto.

These are covered in detail on the next page.

Next Steps