simler
FeaturesPricingAbout
Log inSign up
Docs · Context & connectors

Running exercises

Your data

Context & connectors

Exercises get sharper when they know your real organization. This page explains the three sources simler grounds on, how to connect a live source read-only, and how you stay in control of every query.

What grounds an exercise

Every generated scenario draws on up to three sources, and you decide how many of them you use:

  • Your organization profile — industry, size, systems, and regulatory frameworks, maintained on the Context page.
  • Your policy documents — the ISP, BCP, IRP, and DRP you upload or generate in the platform.
  • Connected sources (optional) — live, read-only access to data your organization already keeps, such as a system inventory or on-call roster in Google Sheets.

Connections are never required: the profile and documents alone ground good exercises. A connection adds the last layer of realism — scenarios that name your actual systems and owners, and AI teammates that can look them up mid-exercise.

Connecting Google Sheets

Google Sheets is the first live connector. An admin connects it from the Connectors page:

  1. 1

    Connect

    Approve the Google consent screen. simler asks for file-scoped, read-only access — it can only ever see files you explicitly pick.
  2. 2

    Pick your sheets

    Choose which spreadsheets simler may read in the Google file picker. Everything else in your Drive stays invisible.
  3. 3

    Set rights per sheet

    For each sheet, choose which capabilities may use it: scenario grounding, simulation agents, and Ask your systems.

Use the preview (the eye icon next to a sheet) to see exactly what simler can read — the preview itself shows up in the access log like any other query.

The security model

Connections are engineered so a security team can approve them:

  • Read-only by design. Connectors can never write to or change your systems — there is no write path.
  • Scoped. Access is granted per source, and per use case within each source.
  • Logged. Every query lands in an access log admins can filter by use case, source, and outcome.
  • Revocable. Remove a single sheet or disconnect entirely at any time; credentials are encrypted and never leave our servers.

Where this is going

The connector registry grows on the same foundation — categories like security monitoring, identity, and ticketing are visible on the Connectors page, and requesting one records your need. Every future connector inherits the same read-only rules, rights, and access log.

Provenance

When a simulation is generated, simler records which documents and connected sources grounded it. You'll see this on the scenario overview, and agents that consult a source during an exercise cite it on their message — so real organization facts are always distinguishable from scenario fiction.