Connector capabilities
Reviewed source reference. Live means a real handler exists; it does not prove configuration, entitlement, a successful vendor pilot or availability in your deployed release. Demo means fictional data or local simulation.
Department add-ons are built-in desks that each need their own entitlement. This reference does not confirm what your deployment runs; check its version and explicit add-on entitlements. Native release packaging targets Linux x64 only; check actual published assets before planning an installation.
Live handler means code exists for a real provider call. Demo only uses fictional data or local simulation. Blocked means the application refuses the action. Unsupported means there is no usable provider implementation. Limited availability means it is built and we set it up with your team, after a pilot with the provider. Add-on is a built-in school desk that needs its own entitlement.
A connection test does not prove every operation works. The table is a source reference, not a list of what your school has enabled. Ask your administrator about the deployed version, licence, permissions and provider consent.
School departments
Section titled “School departments”These are built-in ticketing add-ons, not external provider connectors. A department membership does not bypass campus restrictions or ticket permissions. Global department administrators manage school-wide configuration; ordinary desk managers cannot rewrite shared definitions for other departments.
| School workflow | Availability | Required entitlements and access |
|---|---|---|
| ICT service desk | Live handler | Ticket permissions and the user’s allowed campus and department scope. Required module keys: module.tickets. |
| Facilities desk | Add-on | Facilities add-on entitlement and activation, an enabled desk, assigned department membership and ticket permissions. Required module keys: module.tickets, module.facilities. |
| Administration desk | Add-on | Administration add-on entitlement and activation, an enabled desk, assigned department membership and ticket permissions. Required module keys: module.tickets, module.administration. |
| Other school departments | Add-on | Other-departments add-on entitlement and activation, an enabled desk, assigned department membership and ticket permissions. Required module keys: module.tickets, module.departments. |
AI assistance
Section titled “AI assistance”Amazon Bedrock
Section titled “Amazon Bedrock”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Ask the configured AI assistant | Limited availability | No simulation | Native Converse text chat and tool proposals for one configured model and region with AWS SigV4. No structured JSON, streaming, inference profiles or autonomous actions. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Anthropic (Claude)
Section titled “Anthropic (Claude)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Ask the configured AI assistant | Live handler | No simulation | Provider configuration and school permissions apply. |
Azure OpenAI
Section titled “Azure OpenAI”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Ask the configured AI assistant | Limited availability | No simulation | Native Azure OpenAI v1 text chat, tool proposals and JSON/schema output, plus text embeddings only with an explicitly configured embedding deployment. No streaming, uploads, autonomous actions or credential provisioning; changed embedding model/dimensions require reindexing. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Turn text into vectors for similarity search | Limited availability | No simulation | An explicit embeddingDeployment or matching tiers.embed, compatible Azure embedding deployment and resource API key; no chat deployment fallback. Bounded text embeddings feed existing ticket similarity. Provider/model/dimension changes require reindexing; this adapter does not add external-document retrieval or automatic reindex orchestration. Native Azure OpenAI v1 text chat, tool proposals and JSON/schema output, plus text embeddings only with an explicitly configured embedding deployment. No streaming, uploads, autonomous actions or credential provisioning; changed embedding model/dimensions require reindexing. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Cloudflare Clef (hosted decisions)
Section titled “Cloudflare Clef (hosted decisions)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Make a typed decision over text | Limited availability | No simulation | A Cloudflare account ID, a Workers AI API token and explicit enablement; an AI Gateway is optional. Pseudonymisation is always on, including failover. Managed AI on a Cloudflare endpoint sets one up for a school that has no Clef connector, on the same Cloudflare token as its chat models. Masked text runs on Cloudflare’s network, with no region guarantee; an AI Gateway with logging on keeps it. Calibrated like Jev. Images are not sent. Fixture-tested only; no live key or accuracy benchmark. |
Google Gemini
Section titled “Google Gemini”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Ask the configured AI assistant | Limited availability | No simulation | Native Gemini Developer API text chat, function-call proposals and JSON/schema output for one configured model. Proposals are never executed. No streaming, embeddings, file uploads, decision execution or managed credential provisioning. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Google Vertex AI
Section titled “Google Vertex AI”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Ask the configured AI assistant | Limited availability | No simulation | Native Vertex AI text chat, function proposals and JSON/schema output for one configured project/location/model signed in with a Google service account whose tokens are renewed automatically. No streaming, uploads or autonomous actions. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Laya (local decisions)
Section titled “Laya (local decisions)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Make a typed decision over text | Limited availability | Fixtures available | An explicitly enabled local decision sidecar, sealed model manifest and bearer token. Decision state and criteria are always pseudonymised. Synthetic CPU staging validation only; accuracy and automatic-action eligibility are not established. Local-first routing can fall back to another enabled decision provider. Demo mode returns no answers. |
Ollama (local AI)
Section titled “Ollama (local AI)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Public endpoints must pass the outbound-address checks. Private endpoints require a connector agent or host-authorised network access; the host-configured LOCAL_AI_URL is limited to its own origin. Metadata and link-local destinations are always blocked.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Ask the configured AI assistant | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Turn text into vectors for similarity search | Live handler | Fixtures available | Provider configuration and school permissions apply. |
OpenAI Decisions
Section titled “OpenAI Decisions”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Make a typed decision over text | Limited availability | No simulation | Provider/DPA eligibility review, deployment opt-in, an owner-supplied API key, gpt-6-luna access and explicit enablement. Pseudonymisation is always on, including failover. OpenAI publishes the Decisions API as a public beta: text predicates, choices and rubric scores. Uncalibrated for school data; provider probabilities alone cannot authorize automatic action. Endpoint/account settings determine data handling, with no Australian inference guarantee. Native input cost is estimated with regional and long-context multipliers; gateway fees and DigitalOcean support are unverified. Synthetic fixtures only; no live key or accuracy benchmark. |
OpenAI-compatible endpoint
Section titled “OpenAI-compatible endpoint”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Ask the configured AI assistant | Live handler | No simulation | Provider configuration and school permissions apply. |
| Turn text into vectors for similarity search | Live handler | No simulation | Provider configuration and school permissions apply. |
TypeSafe Jev (hosted decisions)
Section titled “TypeSafe Jev (hosted decisions)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Make a typed decision over text | Limited availability | No simulation | An owner-supplied TypeSafe API key and explicit enablement. Pseudonymisation is always on, including failover. Never provisioned by managed AI. Masked text is sent to TypeSafe in the United States. No customer-data training under its published policy; no fixed standard retention period is published. Enterprise zero retention is separate. Fixture-tested only; no live key or accuracy benchmark. |
Apple device ownership
Section titled “Apple device ownership”Apple Business Manager (devices)
Section titled “Apple Business Manager (devices)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Assign an Apple device to an MDM server | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| List Apple MDM servers | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read an Apple organisation device record | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Apple School Manager (devices)
Section titled “Apple School Manager (devices)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Assign an Apple device to an MDM server | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| List Apple MDM servers | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read an Apple organisation device record | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Backup monitoring
Section titled “Backup monitoring”Veeam Backup & Replication
Section titled “Veeam Backup & Replication”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.backups.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read backup job status | Limited availability | No simulation | Read-only status and last reported result of explicitly selected Veeam Backup & Replication jobs through the site agent. No restores, job execution, recovery verification or RPO guarantees. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Cloud and infrastructure
Section titled “Cloud and infrastructure”Acronis Cyber Protect Cloud tasks
Section titled “Acronis Cyber Protect Cloud tasks”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read service monitoring checks | Limited availability | No simulation | Read-only state of explicitly selected Acronis Task Manager v2 execution tasks. Task records do not establish backup protection, job coverage, restore success or recovery guarantees. Source and synthetic fixture validation only; live provider acceptance remains pending. |
AWS tagged EC2 inventory
Section titled “AWS tagged EC2 inventory”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read cloud and infrastructure resources | Limited availability | No simulation | Read-only tagged EC2 instances in one verified AWS account/region. Tag-scoped inventory is not universal AWS coverage, health or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Azure Resource Manager
Section titled “Azure Resource Manager”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read cloud and infrastructure resources | Limited availability | No simulation | Microsoft 365 > Azure Resource Manager: needs Reader. Read-only Azure resources in one subscription/resource group. Provider provisioning status is not runtime health or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Datadog
Section titled “Datadog”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read service monitoring checks | Limited availability | No simulation | Read-only explicitly selected Datadog monitor states in the configured regional site. No arbitrary metrics, tracing, incidents or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Google Cloud Compute Engine
Section titled “Google Cloud Compute Engine”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read cloud and infrastructure resources | Limited availability | No simulation | Read-only Compute Engine instances in one verified project/zone. No other cloud products, billing or changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Grafana
Section titled “Grafana”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read service monitoring checks | Limited availability | No simulation | Read-only explicitly selected provisioning alert rules in one verified organisation/folder through the site agent. Rule configuration and pause state do not establish firing alert health. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft 365 Aggregate Reports
Section titled “Microsoft 365 Aggregate Reports”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read aggregate Microsoft 365 usage reports | Limited availability | No simulation | Microsoft 365 > Microsoft 365 Aggregate Reports: needs Reports.Read.All. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Aggregate-only active-user and SharePoint storage trends from Microsoft Graph reports. Provider reporting delay and licence availability apply; no person-level activity or productivity assessment. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft 365 Backup
Section titled “Microsoft 365 Backup”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read cloud and infrastructure resources | Limited availability | No simulation | Microsoft 365 > Microsoft 365 Backup: needs BackupRestore-Configuration.Read.All. Read-only explicitly selected Microsoft 365 Backup protection policies/units and up to five recent restore-point summaries for a selected unit. These are not backup job runs, restore verification or recovery guarantees. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read recent restore point metadata for one selected unit | Limited availability | No simulation | Microsoft 365 > Microsoft 365 Backup: needs BackupRestore-Configuration.Read.All, BackupRestore-Monitor.Read.All. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Read-only explicitly selected Microsoft 365 Backup protection policies/units and up to five recent restore-point summaries for a selected unit. These are not backup job runs, restore verification or recovery guarantees. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read selected Microsoft 365 Backup protection units | Limited availability | No simulation | Microsoft 365 > Microsoft 365 Backup: needs BackupRestore-Configuration.Read.All, BackupRestore-Monitor.Read.All. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Read-only explicitly selected Microsoft 365 Backup protection policies/units and up to five recent restore-point summaries for a selected unit. These are not backup job runs, restore verification or recovery guarantees. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft 365 Service Health
Section titled “Microsoft 365 Service Health”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read Microsoft 365 message centre titles and dates | Limited availability | No simulation | Microsoft 365 > Microsoft 365 Service Health: needs ServiceHealth.Read.All, ServiceMessage.Read.All. Provider entitlement, explicitly selected scope and documented administrator consent. See the connector setup guide; real-tenant pilot remains. Explicit connector viewer read with connector.manage, the relevant documentation/directory/security permission and enabled modules. Tenant-wide alerts, audit, XDR, labels and service health require organisation coverage and an unscoped authorised actor. Selected Microsoft 365 service health and current incident summaries in a verified tenant. No remediation or uptime guarantee; provider pilot pending. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read operational incidents | Limited availability | No simulation | Microsoft 365 > Microsoft 365 Service Health: needs ServiceHealth.Read.All, ServiceMessage.Read.All. Provider entitlement, explicitly selected scope and documented administrator consent. See the connector setup guide; real-tenant pilot remains. Explicit connector viewer read with connector.manage, the relevant documentation/directory/security permission and enabled modules. Tenant-wide alerts, audit, XDR, labels and service health require organisation coverage and an unscoped authorised actor. Selected Microsoft 365 service health and current incident summaries in a verified tenant. No remediation or uptime guarantee; provider pilot pending. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read service monitoring checks | Limited availability | No simulation | Microsoft 365 > Microsoft 365 Service Health: needs ServiceHealth.Read.All, ServiceMessage.Read.All. Provider entitlement, explicitly selected scope and documented administrator consent. See the connector setup guide; real-tenant pilot remains. Explicit connector viewer read with connector.manage, the relevant documentation/directory/security permission and enabled modules. Tenant-wide alerts, audit, XDR, labels and service health require organisation coverage and an unscoped authorised actor. Selected Microsoft 365 service health and current incident summaries in a verified tenant. No remediation or uptime guarantee; provider pilot pending. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read the updates posted on one service incident | Limited availability | No simulation | Microsoft 365 > Microsoft 365 Service Health: needs ServiceHealth.Read.All, ServiceMessage.Read.All. Provider entitlement, explicitly selected scope and documented administrator consent. See the connector setup guide; real-tenant pilot remains. Explicit connector viewer read with connector.manage, the relevant documentation/directory/security permission and enabled modules. Tenant-wide alerts, audit, XDR, labels and service health require organisation coverage and an unscoped authorised actor. Selected Microsoft 365 service health and current incident summaries in a verified tenant. No remediation or uptime guarantee; provider pilot pending. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft Hyper-V
Section titled “Microsoft Hyper-V”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- A connector agent on the school network is required, on hosted and self-hosted deployments alike.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read cloud and infrastructure resources | Limited availability | No simulation | Explicitly select a current site connector agent; platform execution is refused even on a deployment with private network access. Windows Hyper-V host running the site agent, its exact host name and SMBIOS UUID, selected VM UUIDs and read-authorized CIM service account. Read-only selected VM inventory and native status on one UUID-pinned local Windows Hyper-V host through the site agent. No remote WinRM, guest health, VM power or console control. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft Power BI
Section titled “Microsoft Power BI”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read cloud and infrastructure resources | Limited availability | No simulation | Microsoft 365 > Microsoft Power BI: needs Service principals can use Fabric APIs, Workspace Viewer. Read-only dataset identity in one selected workspace, signed in as an Entra application. No report embedding, refresh execution, arbitrary query access or invented dataset health. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft Sentinel
Section titled “Microsoft Sentinel”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read cloud and infrastructure resources | Limited availability | No simulation | Microsoft 365 > Microsoft Sentinel: needs Microsoft Sentinel Reader, Log Analytics Reader. Read-only recent Sentinel incidents in one configured subscription/resource group/workspace. No investigations, ingestion, alert rules or response actions. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read operational incidents | Limited availability | No simulation | Microsoft 365 > Microsoft Sentinel: needs Microsoft Sentinel Reader, Log Analytics Reader. Read-only recent Sentinel incidents in one configured subscription/resource group/workspace. No investigations, ingestion, alert rules or response actions. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read service monitoring checks | Limited availability | No simulation | Microsoft 365 > Microsoft Sentinel: needs Microsoft Sentinel Reader, Log Analytics Reader. Read-only recent Sentinel incidents in one configured subscription/resource group/workspace. No investigations, ingestion, alert rules or response actions. Source and synthetic fixture validation only; live provider acceptance remains pending. |
n8n Workflows
Section titled “n8n Workflows”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read cloud and infrastructure resources | Limited availability | No simulation | Read-only identity and active/archive state of explicitly selected workflows through the site agent. No executions, trigger invocation or node/credential payloads. Source and synthetic fixture validation only; live provider acceptance remains pending. |
PagerDuty
Section titled “PagerDuty”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read operational incidents | Limited availability | No simulation | Read-only recent incidents in one verified PagerDuty service. No acknowledgement, resolution, on-call changes or paging. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Power Automate Solution Flows
Section titled “Power Automate Solution Flows”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read cloud and infrastructure resources | Limited availability | No simulation | Microsoft 365 > Power Automate Solution Flows: needs Application user with read on Process. Read-only explicitly selected solution-aware cloud flow definitions in one verified Dataverse organisation, signed in as an Entra application user. No non-solution My Flows, desktop flows, execution history, triggers or workflow changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Proxmox VE
Section titled “Proxmox VE”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read cloud and infrastructure resources | Limited availability | No simulation | Read-only virtual resources on one verified Proxmox node through the site agent. No VM power, console launch, backups or changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read cloud and infrastructure resources | Limited availability | No simulation | Read-only explicitly selected compute nodes in one verified Slurm cluster through the site agent using v0.0.45. No workload payloads, job submission, cancellation or quota changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
VMware vCenter
Section titled “VMware vCenter”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read cloud and infrastructure resources | Limited availability | No simulation | Read-only explicitly selected virtual machines from native vCenter inventory through the site agent. No Hyper-V, ESXi-only API, VM power, console or changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
WatchGuard ThreatSync
Section titled “WatchGuard ThreatSync”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read service monitoring checks | Limited availability | No simulation | Read-only explicitly selected ThreatSync incident checks in one verified WatchGuard account. No universal firewall inventory, invented update times, policies or response actions. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Customer records
Section titled “Customer records”HubSpot
Section titled “HubSpot”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Create a CRM case | Limited availability | No simulation | Owner-scoped company/contact lookup and ticket creation/read within the configured pipeline; no synchronization, marketing operations or webhook ingestion. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Find a CRM account | Limited availability | No simulation | Owner-scoped company/contact lookup and ticket creation/read within the configured pipeline; no synchronization, marketing operations or webhook ingestion. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Find a CRM contact | Limited availability | No simulation | Owner-scoped company/contact lookup and ticket creation/read within the configured pipeline; no synchronization, marketing operations or webhook ingestion. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read a CRM case | Limited availability | No simulation | Owner-scoped company/contact lookup and ticket creation/read within the configured pipeline; no synchronization, marketing operations or webhook ingestion. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Salesforce
Section titled “Salesforce”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Create a CRM case | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Find a CRM account | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Find a CRM contact | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read a CRM case | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Salesforce Agentforce
Section titled “Salesforce Agentforce”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| End a Salesforce Agentforce conversation | Limited availability | No simulation | An activated compatible Salesforce agent, External Client App credentials, a verified advisory execution identity, Integrations and the staff Agentforce permission. Staff pilot prepared locally; live sandbox acceptance is outstanding. Sends typed messages only. Salesforce permissions apply. No automatic retries, native tool execution or billing-cap guarantee. |
| Send a message to Salesforce Agentforce | Limited availability | No simulation | An activated compatible Salesforce agent, External Client App credentials, a verified advisory execution identity, Integrations and the staff Agentforce permission. Staff pilot prepared locally; live sandbox acceptance is outstanding. Sends typed messages only. Salesforce permissions apply. No automatic retries, native tool execution or billing-cap guarantee. |
| Start a Salesforce Agentforce conversation | Limited availability | No simulation | An activated compatible Salesforce agent, External Client App credentials, a verified advisory execution identity, Integrations and the staff Agentforce permission. Staff pilot prepared locally; live sandbox acceptance is outstanding. Sends typed messages only. Salesforce permissions apply. No automatic retries, native tool execution or billing-cap guarantee. |
Devices
Section titled “Devices”Addigy
Section titled “Addigy”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Find a device by serial number | Limited availability | No simulation | Read-only device inventory and serial lookup; no scripts, commands, policies, lock or wipe. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read a device record | Limited availability | No simulation | Read-only device inventory and serial lookup; no scripts, commands, policies, lock or wipe. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read the managed fleet | Limited availability | No simulation | Read-only device inventory and serial lookup; no scripts, commands, policies, lock or wipe. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Chrome Enterprise
Section titled “Chrome Enterprise”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Erase a device | Live handler | Fixtures available | Google Workspace > Chrome Enterprise: needs https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly, https://www.googleapis.com/auth/admin.directory.device.chromeos, with the allowRemoteWipe setting on. A school can set this to act as the technician’s own Google admin account through domain-wide delegation, under Settings, Connectors, Run as. Remote erase must be enabled for this connector. Device permissions, step-up authentication, target confirmation, vendor privileges and device-specific restrictions still apply. |
| Find a device by serial number | Live handler | Fixtures available | Google Workspace > Chrome Enterprise: needs https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly. |
| Find a person’s devices | Live handler | Fixtures available | Google Workspace > Chrome Enterprise: needs https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly. |
| Read a device fix result | Live handler | Fixtures available | Google Workspace > Chrome Enterprise: needs https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly, https://www.googleapis.com/auth/admin.directory.device.chromeos, with the allowDeviceActions setting on. Polled after an approved fix and posted to the ticket as an internal note. Script output is shortened and shown as text. |
| Read a device record | Live handler | Fixtures available | Google Workspace > Chrome Enterprise: needs https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly. |
| Read one selected Chromebook’s OS update telemetry | Limited availability | No simulation | Google Workspace > Chrome Enterprise: needs https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Selected Chromebook OS update reports are dated telemetry; no full EDR, live health or Defender equivalence. |
| Read selected Chrome policies resolved for one organisational unit | Limited availability | No simulation | Google Workspace > Chrome Enterprise: needs https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. |
| Read the managed fleet | Live handler | Fixtures available | Google Workspace > Chrome Enterprise: needs https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly. |
| Search serial numbers | Live handler | Fixtures available | Google Workspace > Chrome Enterprise: needs https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly. |
| Send a Chromebook fix command | Live handler | Fixtures available | Google Workspace > Chrome Enterprise: needs https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly, https://www.googleapis.com/auth/admin.directory.device.chromeos, with the allowDeviceActions setting on. A school can set this to act as the technician’s own Google admin account through domain-wide delegation, under Settings, Connectors, Run as. Device actions must be enabled for this connector, with the provider’s action permission or read-write scope. Runs only as an approved device fix on a staff device, one approval per run. REBOOT and CAPTURE_LOGS only. Google documents log capture for kiosk devices; powerwash and remote desktop are not reachable here. |
| Send a supported device command | Live handler | Fixtures available | Google Workspace > Chrome Enterprise: needs https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly, https://www.googleapis.com/auth/admin.directory.device.chromeos, with the allowDeviceActions setting on. A school can set this to act as the technician’s own Google admin account through domain-wide delegation, under Settings, Connectors, Run as. Only the commands this connector declares, on the platforms it declares them for, and only with device commands turned on for the connector. A generic command does not imply lock or erase support. |
FileWave saved-report device inventory
Section titled “FileWave saved-report device inventory”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read the managed fleet | Limited availability | No simulation | Read-only devices from one saved FileWave inventory report through the site agent, with configured identity columns. No commands, software deployments or policy changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Iru (formerly Kandji)
Section titled “Iru (formerly Kandji)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Find a device by serial number | Live handler | No simulation | Provider configuration and school permissions apply. |
| List the school’s fix scripts | Live handler | No simulation | Lists Self Service custom scripts by name only. Iru’s API cannot start a Self Service item on a device, so imported items are reference entries. |
| Read a device record | Live handler | No simulation | Provider configuration and school permissions apply. |
| Read the managed fleet | Live handler | No simulation | Provider configuration and school permissions apply. |
| Send a device fix action | Live handler | No simulation | Device actions must be enabled for this connector, with the provider’s action permission or read-write scope. Runs only as an approved device fix on a staff device, one approval per run. Blank push, restart and lock only. A Mac lock’s unlock PIN stays in Iru and is not returned. |
Jamf Pro
Section titled “Jamf Pro”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Erase a device | Live handler | No simulation | Uses a separate privileged API client when one is configured, otherwise the main client. Remote erase must be enabled for this connector. Device permissions, step-up authentication, target confirmation, vendor privileges and device-specific restrictions still apply. |
| Find a device by serial number | Live handler | No simulation | Provider configuration and school permissions apply. |
| List managed local administrator accounts | Live handler | No simulation | Uses a separate privileged API client when one is configured, otherwise the main client. LAPS retrieval must be enabled for this connector, with separate device/LAPS permissions and vendor privileges. Password access requires fresh multifactor verification and an audit reason. |
| Push the Plugboard kiosk profile | Live handler | No simulation | Uses a separate commands API client when one is configured, otherwise the main client. An API client with Update on Mobile Device Apps and Create on Mobile Device Configuration Profiles, and the Plugboard app added to Jamf. Creates the objects unassigned: the school scopes them to its kiosk devices in the MDM. Pushed from Settings, Kiosks, Enrolment tokens by someone with both feature.manage and connector.manage. |
| Read a device group | Live handler | No simulation | Provider configuration and school permissions apply. |
| Read a device record | Live handler | No simulation | Provider configuration and school permissions apply. |
| Read a local administrator password | Live handler | No simulation | Uses a separate privileged API client when one is configured, otherwise the main client. LAPS retrieval must be enabled for this connector, with separate device/LAPS permissions and vendor privileges. Password access requires fresh multifactor verification and an audit reason. |
| Read the managed fleet | Live handler | No simulation | Provider configuration and school permissions apply. |
| Search serial numbers | Live handler | No simulation | Provider configuration and school permissions apply. |
| Send a supported device command | Live handler | No simulation | Uses a separate commands API client when one is configured, otherwise the main client. Only the commands this connector declares, on the platforms it declares them for, and only with device commands turned on for the connector. A generic command does not imply lock or erase support. |
Jamf Pro Mobile
Section titled “Jamf Pro Mobile”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Find a device by serial number | Live handler | No simulation | Provider configuration and school permissions apply. |
| Push the Plugboard kiosk profile | Live handler | No simulation | An API client with Update on Mobile Device Apps and Create on Mobile Device Configuration Profiles, and the Plugboard app added to Jamf. Creates the objects unassigned: the school scopes them to its kiosk devices in the MDM. Pushed from Settings, Kiosks, Enrolment tokens by someone with both feature.manage and connector.manage. |
| Read a device record | Live handler | No simulation | Provider configuration and school permissions apply. |
| Read the managed fleet | Live handler | No simulation | Provider configuration and school permissions apply. |
| Send a supported device command | Live handler | No simulation | Only the commands this connector declares, on the platforms it declares them for, and only with device commands turned on for the connector. A generic command does not imply lock or erase support. |
Jamf School
Section titled “Jamf School”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Find a device by serial number | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Read-only device inventory and serial lookup; no commands, policy changes, lock or wipe. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read a device record | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Read-only device inventory and serial lookup; no commands, policy changes, lock or wipe. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read the managed fleet | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Read-only device inventory and serial lookup; no commands, policy changes, lock or wipe. Source and synthetic fixture validation only; live provider acceptance remains pending. |
ManageEngine Endpoint Central
Section titled “ManageEngine Endpoint Central”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a device record | Limited availability | No simulation | Read-only Endpoint Central inventory for one exact domain and branch through the site agent, using the legacy v1.4 API. Installed-version acceptance required; no commands, serial enrichment or other ManageEngine products. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read the managed fleet | Limited availability | No simulation | Read-only Endpoint Central inventory for one exact domain and branch through the site agent, using the legacy v1.4 API. Installed-version acceptance required; no commands, serial enrichment or other ManageEngine products. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft Intune
Section titled “Microsoft Intune”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Ask a device to check in | Live handler | No simulation | Microsoft 365 > Microsoft Intune: needs DeviceManagementManagedDevices.Read.All, DeviceManagementManagedDevices.PrivilegedOperations.All, with the allowRemediation setting on. Runs only as an approved device fix on a staff device. |
| Erase a device | Live handler | No simulation | Microsoft 365 > Microsoft Intune: needs DeviceManagementManagedDevices.Read.All, DeviceManagementManagedDevices.PrivilegedOperations.All, with the allowRemoteWipe setting on. A school can set this to act as the technician through their own Microsoft sign-in, under Settings, Connectors, Run as; technicians who have signed in act as themselves by default. Remote erase must be enabled for this connector. Device permissions, step-up authentication, target confirmation, vendor privileges and device-specific restrictions still apply. |
| Find a device by serial number | Live handler | No simulation | Microsoft 365 > Microsoft Intune: needs DeviceManagementManagedDevices.Read.All. |
| List the school’s fix scripts | Live handler | No simulation | Microsoft 365 > Microsoft Intune: needs DeviceManagementManagedDevices.Read.All, DeviceManagementScripts.Read.All, with the allowRemediation setting on. Read-only import for the fix catalogue: names and ids, never script bodies. Uses a beta Graph endpoint. |
| Push the Plugboard kiosk profile | Live handler | No simulation | Microsoft 365 > Microsoft Intune: needs DeviceManagementManagedDevices.Read.All, DeviceManagementApps.ReadWrite.All, DeviceManagementConfiguration.ReadWrite.All. The Plugboard app added to Intune. Creates the objects unassigned: the school scopes them to its kiosk devices in the MDM. Pushed from Settings, Kiosks, Enrolment tokens by someone with both feature.manage and connector.manage. |
| Read a device fix result | Live handler | No simulation | Microsoft 365 > Microsoft Intune: needs DeviceManagementManagedDevices.Read.All, DeviceManagementConfiguration.Read.All, with the allowRemediation setting on. Polled after an approved fix and posted to the ticket as an internal note. Script output is shortened and shown as text. |
| Read a device record | Live handler | No simulation | Microsoft 365 > Microsoft Intune: needs DeviceManagementManagedDevices.Read.All. |
| Read a local administrator password | Live handler | No simulation | Microsoft 365 > Microsoft Intune: needs DeviceManagementManagedDevices.Read.All, DeviceLocalCredential.Read.All, with the allowLapsRetrieval setting on. A school can set this to act as the technician through their own Microsoft sign-in, under Settings, Connectors, Run as; technicians who have signed in act as themselves by default. LAPS retrieval must be enabled for this connector, with separate device/LAPS permissions and vendor privileges. Password access requires fresh multifactor verification and an audit reason. |
| Read failing compliance policies | Live handler | No simulation | Microsoft 365 > Microsoft Intune: needs DeviceManagementManagedDevices.Read.All, DeviceManagementConfiguration.Read.All. Read when someone opens a non-compliant device, one record at a time. Never read during sync and never stored. |
| Read the managed fleet | Live handler | No simulation | Microsoft 365 > Microsoft Intune: needs DeviceManagementManagedDevices.Read.All. |
| Run one of the school’s remediation scripts | Live handler | No simulation | Microsoft 365 > Microsoft Intune: needs DeviceManagementManagedDevices.Read.All, DeviceManagementManagedDevices.PrivilegedOperations.All, with the allowRemediation setting on. A school can set this to act as the technician through their own Microsoft sign-in, under Settings, Connectors, Run as; technicians who have signed in act as themselves by default. Remediation scripts must be enabled for this connector and the app registration granted DeviceManagementManagedDevices.PrivilegedOperations.All, the same permission as remote wipe. Needs Windows Enterprise E3/E5 or Education A3/A5 licences. Runs only as an approved device fix on a staff device, one approval per run. Starts only scripts that already exist in the school’s MDM, by id. Plugboard never uploads or edits a script. Uses a beta Graph endpoint. |
| Send a supported device command | Live handler | No simulation | Microsoft 365 > Microsoft Intune: needs DeviceManagementManagedDevices.Read.All, DeviceManagementManagedDevices.PrivilegedOperations.All, with the allowDeviceCommands setting on. Only the commands this connector declares, on the platforms it declares them for, and only with device commands turned on for the connector. A generic command does not imply lock or erase support. |
Mosyle
Section titled “Mosyle”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Find a device by serial number | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Find a person’s devices | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read a device record | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read the managed fleet | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Search serial numbers | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Send a supported device command | Live handler | Fixtures available | Only the commands this connector declares, on the platforms it declares them for, and only with device commands turned on for the connector. A generic command does not imply lock or erase support. |
NinjaOne
Section titled “NinjaOne”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a device record | Limited availability | No simulation | Read-only device inventory; no remote access, scripts, patching, alerts or ticket synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read the managed fleet | Limited availability | No simulation | Read-only device inventory; no remote access, scripts, patching, alerts or ticket synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Snipe-IT
Section titled “Snipe-IT”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a device record | Limited availability | No simulation | Read-only hardware identity in one company and category through the site agent. Asset records are not device telemetry; no checkout, inventory writes, licence reconciliation or commands. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read the managed fleet | Limited availability | No simulation | Read-only hardware identity in one company and category through the site agent. Asset records are not device telemetry; no checkout, inventory writes, licence reconciliation or commands. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Directory sign-in
Section titled “Directory sign-in”LDAP / Active Directory
Section titled “LDAP / Active Directory”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Check directory sign-in credentials | Live handler | No simulation | Provider configuration and school permissions apply. |
| Find a directory sign-in account | Live handler | No simulation | Provider configuration and school permissions apply. |
| Reset an LDAP password | Live handler | No simulation | A writable LDAP account and secure LDAP transport; password-policy and provider restrictions apply. |
Google Workspace (Gmail)
Section titled “Google Workspace (Gmail)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Import inbox messages as tickets | Limited availability | No simulation | Google Workspace > Google Workspace (Gmail): needs https://www.googleapis.com/auth/gmail.send. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Gmail intake needs an explicitly saved native start history ID. Expired history refuses advancement until an administrator rebaselines; no automatic historical backfill. |
| Read selected Gmail forwarding, delegate and filter summaries | Limited availability | No simulation | Google Workspace > Google Workspace (Gmail): needs https://www.googleapis.com/auth/gmail.send. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. |
| Send email | Live handler | No simulation | Google Workspace > Google Workspace (Gmail): needs https://www.googleapis.com/auth/gmail.send. |
IMAP inbox
Section titled “IMAP inbox”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A connector agent on the school network is required, on hosted and self-hosted deployments alike.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Import inbox messages as tickets | Limited availability | No simulation | Explicitly select a current site connector agent; platform execution is refused even on a deployment with private network access. Verified TLS mailbox read access and explicit receiveEnabled opt-in. Password/app-password or supplied OAuth bearer; authentication policy remains controlled by the mail server. Read-only verified-TLS mailbox intake through the site agent into existing ticket routing. Password/app-password or supplied OAuth bearer; no sending, marking or deleting mail. UIDVALIDITY changes stop intake until explicitly rebaselined. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft 365 Email
Section titled “Microsoft 365 Email”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Check submission of one recorded outgoing message | Live handler | No simulation | Microsoft 365 > Microsoft 365 Email: needs Application Mail.Send, scoped to this mailbox. Exchange Online mailbox, dedicated single-tenant app credential, and mailbox-scoped Application Mail.Read / Application Mail.Send roles. Do not also grant unscoped Entra mail permissions. Reads the configured mailbox’s Sent Items for an exact Message-ID and recipient match. A match confirms provider submission, not recipient delivery. A missing record never permits an automatic resend. Requires the existing mailbox-scoped read role. |
| Import inbox messages as tickets | Live handler | No simulation | Microsoft 365 > Microsoft 365 Email: needs Application Mail.Send, scoped to this mailbox. Exchange Online mailbox, dedicated single-tenant app credential, and mailbox-scoped Application Mail.Read / Application Mail.Send roles. Do not also grant unscoped Entra mail permissions. Explicit intake enablement and the background worker are required. Imports inbox messages received since configuration; preserves read state. File attachments only, up to 20 and 8 MB total. Failed pages retain their position for retry. |
| Send email | Live handler | No simulation | Microsoft 365 > Microsoft 365 Email: needs Application Mail.Send, scoped to this mailbox. Exchange Online mailbox, dedicated single-tenant app credential, and mailbox-scoped Application Mail.Read / Application Mail.Send roles. Do not also grant unscoped Entra mail permissions. Microsoft acceptance is not final delivery. Sending is not retried automatically after an ambiguous response. |
SMTP Email
Section titled “SMTP Email”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Send email | Live handler | No simulation | Provider configuration and school permissions apply. |
Endpoint protection
Section titled “Endpoint protection”Bitdefender GravityZone
Section titled “Bitdefender GravityZone”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| List protected computers | Limited availability | No simulation | Read-only endpoint inventory within the configured company; no incidents, policies, scans or response actions. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read endpoint protection status | Limited availability | No simulation | Read-only endpoint inventory within the configured company; no incidents, policies, scans or response actions. Source and synthetic fixture validation only; live provider acceptance remains pending. |
CrowdStrike Falcon
Section titled “CrowdStrike Falcon”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| List protected computers | Limited availability | No simulation | Read-only endpoint inventory and bounded EPP alerts by native update time in the configured CID, preserving Critical severity. No non-endpoint alert products, process/file/user payloads, containment or response commands. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read endpoint protection status | Limited availability | No simulation | Read-only endpoint inventory and bounded EPP alerts by native update time in the configured CID, preserving Critical severity. No non-endpoint alert products, process/file/user payloads, containment or response commands. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read recent security alerts | Limited availability | No simulation | Alerts READ for the exact configured customer CID and regional endpoint; enabled security module and device.view for snapshot access. Complete native updated_timestamp window of at most seven days and 5,000 EPP endpoint alerts. Critical is preserved; unknown severity/status stay explicit. Read-only endpoint inventory and bounded EPP alerts by native update time in the configured CID, preserving Critical severity. No non-endpoint alert products, process/file/user payloads, containment or response commands. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft Defender for Endpoint
Section titled “Microsoft Defender for Endpoint”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| List protected computers | Limited availability | No simulation | Microsoft 365 > Microsoft Defender for Endpoint: needs Machine.Read.All. Read-only endpoint inventory and alerts updated in the last seven days, restricted to the configured tenant and device group. No investigations, isolation, remediation or security-policy changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read endpoint protection status | Limited availability | No simulation | Microsoft 365 > Microsoft Defender for Endpoint: needs Machine.Read.All. Read-only endpoint inventory and alerts updated in the last seven days, restricted to the configured tenant and device group. No investigations, isolation, remediation or security-policy changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read one Defender device’s vulnerabilities and recommendations | Limited availability | No simulation | Microsoft 365 > Microsoft Defender for Endpoint: needs Machine.Read.All, Vulnerability.Read.All. Provider entitlement, explicitly selected scope and documented administrator consent. See the connector setup guide; real-tenant pilot remains. Explicit connector viewer read with connector.manage, the relevant documentation/directory/security permission and enabled modules. Tenant-wide alerts, audit, XDR, labels and service health require organisation coverage and an unscoped authorised actor. One verified device in its configured Endpoint device group; recommendations endpoint carries a provider prerelease warning. No automated remediation. Read-only endpoint inventory and alerts updated in the last seven days, restricted to the configured tenant and device group. No investigations, isolation, remediation or security-policy changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read recent security alerts | Limited availability | No simulation | Microsoft 365 > Microsoft Defender for Endpoint: needs Machine.Read.All. Read-only endpoint inventory and alerts updated in the last seven days, restricted to the configured tenant and device group. No investigations, isolation, remediation or security-policy changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft Defender XDR
Section titled “Microsoft Defender XDR”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read Microsoft Defender XDR incident summaries | Limited availability | No simulation | Microsoft 365 > Microsoft Defender XDR: needs SecurityIncident.Read.All. Provider entitlement, explicitly selected scope and documented administrator consent. See the connector setup guide; real-tenant pilot remains. Explicit connector viewer read with connector.manage, the relevant documentation/directory/security permission and enabled modules. Tenant-wide alerts, audit, XDR, labels and service health require organisation coverage and an unscoped authorised actor. Tenant-wide scope; Endpoint device-group restrictions do not apply. Tenant-wide Defender XDR incident and alert summaries plus Microsoft Secure Score/control metadata. Separate from Endpoint device-group scope; no evidence contents, response actions or incident updates. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read Microsoft Secure Score and control metadata | Limited availability | No simulation | Microsoft 365 > Microsoft Defender XDR: needs SecurityIncident.Read.All. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Tenant-wide Defender XDR incident and alert summaries plus Microsoft Secure Score/control metadata. Separate from Endpoint device-group scope; no evidence contents, response actions or incident updates. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read tenant-wide Defender alert summaries | Limited availability | No simulation | Microsoft 365 > Microsoft Defender XDR: needs SecurityIncident.Read.All. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Scheduled alert snapshots are separately enabled by collectTenantAlerts; Google snapshots also require identity.signins.view and the directory module. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Tenant-wide Defender XDR incident and alert summaries plus Microsoft Secure Score/control metadata. Separate from Endpoint device-group scope; no evidence contents, response actions or incident updates. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft Purview (Microsoft 365)
Section titled “Microsoft Purview (Microsoft 365)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read metadata from selected Microsoft 365 audit activity feeds | Limited availability | No simulation | Microsoft 365 > Microsoft Purview (Microsoft 365): needs InformationProtectionPolicy.Read.All, ActivityFeed.Read. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Existing enabled subscriptions only; requested window follows content availability, while individual event times can be earlier. No sensitive context payloads or feed subscription writes. Tenant sensitivity-label definitions, existing enabled audit activity metadata and status of selected existing audit queries. No query creation, evidence, retention changes, content scanning or enforcement assurance. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read Purview sensitivity-label definitions | Limited availability | No simulation | Microsoft 365 > Microsoft Purview (Microsoft 365): needs InformationProtectionPolicy.Read.All. Provider entitlement, explicitly selected scope and documented administrator consent. See the connector setup guide; real-tenant pilot remains. Explicit connector viewer read with connector.manage, the relevant documentation/directory/security permission and enabled modules. Tenant-wide alerts, audit, XDR, labels and service health require organisation coverage and an unscoped authorised actor. Label definitions only; no DLP, retention, eDiscovery or compliance assessment. Tenant sensitivity-label definitions, existing enabled audit activity metadata and status of selected existing audit queries. No query creation, evidence, retention changes, content scanning or enforcement assurance. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read status metadata of selected existing Purview audit queries | Limited availability | No simulation | Microsoft 365 > Microsoft Purview (Microsoft 365): needs InformationProtectionPolicy.Read.All, AuditLogsQuery.Read.All. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Configured existing query statuses only; no audit query creation, records, search terms or evidence exports. Tenant sensitivity-label definitions, existing enabled audit activity metadata and status of selected existing audit queries. No query creation, evidence, retention changes, content scanning or enforcement assurance. Source and synthetic fixture validation only; live provider acceptance remains pending. |
SentinelOne
Section titled “SentinelOne”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| List protected computers | Limited availability | No simulation | Read-only endpoint inventory in one account and site. No alerts, isolation commands, remediation or policy changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read endpoint protection status | Limited availability | No simulation | Read-only endpoint inventory in one account and site. No alerts, isolation commands, remediation or policy changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Sophos
Section titled “Sophos”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| List protected computers | Limited availability | No simulation | Read-only endpoint inventory within the configured tenant; no alerts, isolation, scans or response actions. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read endpoint protection status | Limited availability | No simulation | Read-only endpoint inventory within the configured tenant; no alerts, isolation, scans or response actions. Source and synthetic fixture validation only; live provider acceptance remains pending. |
ThreatLocker
Section titled “ThreatLocker”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Isolate an endpoint | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| List protected computers | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read endpoint protection status | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read endpoint security history | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read security requests | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Resolve a security request | Live handler | Fixtures available | Provider configuration and school permissions apply. |
External documentation
Section titled “External documentation”Confluence Cloud
Section titled “Confluence Cloud”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.docs.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| List documentation spaces | Limited availability | No simulation | Read-only spaces and bounded page bodies in one configured Confluence Cloud space. Storage markup is text, never evaluated; no writes, macros, attachments or native document mirroring. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| List external documents | Limited availability | No simulation | Read-only spaces and bounded page bodies in one configured Confluence Cloud space. Storage markup is text, never evaluated; no writes, macros, attachments or native document mirroring. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external document | Limited availability | No simulation | Read-only spaces and bounded page bodies in one configured Confluence Cloud space. Storage markup is text, never evaluated; no writes, macros, attachments or native document mirroring. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Notion
Section titled “Notion”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.docs.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| List documentation spaces | Limited availability | No simulation | Read-only pages and bounded plain-text block content beneath one configured Notion root page. Unsupported block content refuses complete reads; no writes or native document mirroring. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| List external documents | Limited availability | No simulation | Read-only pages and bounded plain-text block content beneath one configured Notion root page. Unsupported block content refuses complete reads; no writes or native document mirroring. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external document | Limited availability | No simulation | Read-only pages and bounded plain-text block content beneath one configured Notion root page. Unsupported block content refuses complete reads; no writes or native document mirroring. Source and synthetic fixture validation only; live provider acceptance remains pending. |
SharePoint Online Pages
Section titled “SharePoint Online Pages”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.docs.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| List documentation spaces | Limited availability | No simulation | Microsoft 365 > SharePoint Online Pages: needs Sites.Read.All. Selected SharePoint site pages (signed in as an Entra application), text web parts and optionally library metadata/reported quota. Unsupported page parts refuse complete reads; no file contents, writes or full sharing assessment. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| List external documents | Limited availability | No simulation | Microsoft 365 > SharePoint Online Pages: needs Sites.Read.All. Selected SharePoint site pages (signed in as an Entra application), text web parts and optionally library metadata/reported quota. Unsupported page parts refuse complete reads; no file contents, writes or full sharing assessment. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external document | Limited availability | No simulation | Microsoft 365 > SharePoint Online Pages: needs Sites.Read.All. Selected SharePoint site pages (signed in as an Entra application), text web parts and optionally library metadata/reported quota. Unsupported page parts refuse complete reads; no file contents, writes or full sharing assessment. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read caller-visible permissions on one SharePoint item | Limited availability | No simulation | Microsoft 365 > SharePoint Online Pages: needs Sites.Read.All. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Selected SharePoint site pages (signed in as an Entra application), text web parts and optionally library metadata/reported quota. Unsupported page parts refuse complete reads; no file contents, writes or full sharing assessment. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read selected SharePoint library metadata and reported quota | Limited availability | No simulation | Microsoft 365 > SharePoint Online Pages: needs Sites.Read.All. Provider entitlement, explicitly selected scope and documented administrator consent. See the connector setup guide; real-tenant pilot remains. Explicit connector viewer read with connector.manage, the relevant documentation/directory/security permission and enabled modules. Tenant-wide alerts, audit, XDR, labels and service health require organisation coverage and an unscoped authorised actor. Selected SharePoint site pages (signed in as an Entra application), text web parts and optionally library metadata/reported quota. Unsupported page parts refuse complete reads; no file contents, writes or full sharing assessment. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read SharePoint tenant sharing settings | Limited availability | No simulation | Microsoft 365 > SharePoint Online Pages: needs Sites.Read.All. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Selected SharePoint site pages (signed in as an Entra application), text web parts and optionally library metadata/reported quota. Unsupported page parts refuse complete reads; no file contents, writes or full sharing assessment. Source and synthetic fixture validation only; live provider acceptance remains pending. |
External ticketing
Section titled “External ticketing”Autotask
Section titled “Autotask”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add an external ticket comment | Limited availability | No simulation | Tickets within the configured company: create, read, status, notes and close. No contracts, billing, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Close an external ticket | Limited availability | No simulation | Tickets within the configured company: create, read, status, notes and close. No contracts, billing, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Raise an external ticket | Limited availability | No simulation | Tickets within the configured company: create, read, status, notes and close. No contracts, billing, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket | Limited availability | No simulation | Tickets within the configured company: create, read, status, notes and close. No contracts, billing, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket’s status | Limited availability | No simulation | Tickets within the configured company: create, read, status, notes and close. No contracts, billing, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Freshservice
Section titled “Freshservice”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add an external ticket comment | Limited availability | No simulation | An API key for an agent restricted to the configured Freshservice workspace and an existing requester ID in that workspace. Source and fixture validation only; provider sandbox acceptance pending. Create, read, status, notes and close only. No inbound webhook ingestion, attachment sync, search, arbitrary field mapping or cross-workspace operations. Configure required vendor fields before enabling; mandatory-field rules are never bypassed. |
| Close an external ticket | Limited availability | No simulation | An API key for an agent restricted to the configured Freshservice workspace and an existing requester ID in that workspace. Source and fixture validation only; provider sandbox acceptance pending. Create, read, status, notes and close only. No inbound webhook ingestion, attachment sync, search, arbitrary field mapping or cross-workspace operations. Configure required vendor fields before enabling; mandatory-field rules are never bypassed. |
| Raise an external ticket | Limited availability | No simulation | An API key for an agent restricted to the configured Freshservice workspace and an existing requester ID in that workspace. Source and fixture validation only; provider sandbox acceptance pending. Create, read, status, notes and close only. No inbound webhook ingestion, attachment sync, search, arbitrary field mapping or cross-workspace operations. Configure required vendor fields before enabling; mandatory-field rules are never bypassed. |
| Read an external ticket | Limited availability | No simulation | An API key for an agent restricted to the configured Freshservice workspace and an existing requester ID in that workspace. Source and fixture validation only; provider sandbox acceptance pending. Create, read, status, notes and close only. No inbound webhook ingestion, attachment sync, search, arbitrary field mapping or cross-workspace operations. Configure required vendor fields before enabling; mandatory-field rules are never bypassed. |
| Read an external ticket’s status | Limited availability | No simulation | An API key for an agent restricted to the configured Freshservice workspace and an existing requester ID in that workspace. Source and fixture validation only; provider sandbox acceptance pending. Create, read, status, notes and close only. No inbound webhook ingestion, attachment sync, search, arbitrary field mapping or cross-workspace operations. Configure required vendor fields before enabling; mandatory-field rules are never bypassed. |
GitHub Issues
Section titled “GitHub Issues”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add an external ticket comment | Limited availability | No simulation | Issues in one configured repository: create, read, status, comment and close. No pull requests, code access, attachments or webhook sync. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Close an external ticket | Limited availability | No simulation | Issues in one configured repository: create, read, status, comment and close. No pull requests, code access, attachments or webhook sync. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Raise an external ticket | Limited availability | No simulation | Issues in one configured repository: create, read, status, comment and close. No pull requests, code access, attachments or webhook sync. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket | Limited availability | No simulation | Issues in one configured repository: create, read, status, comment and close. No pull requests, code access, attachments or webhook sync. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket’s status | Limited availability | No simulation | Issues in one configured repository: create, read, status, comment and close. No pull requests, code access, attachments or webhook sync. Source and synthetic fixture validation only; live provider acceptance remains pending. |
GitLab Issues
Section titled “GitLab Issues”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add an external ticket comment | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Issues in one configured project: create, read, status, comment and close. No merge requests, code access, attachments or webhook sync. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Close an external ticket | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Issues in one configured project: create, read, status, comment and close. No merge requests, code access, attachments or webhook sync. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Raise an external ticket | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Issues in one configured project: create, read, status, comment and close. No merge requests, code access, attachments or webhook sync. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Issues in one configured project: create, read, status, comment and close. No merge requests, code access, attachments or webhook sync. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket’s status | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Issues in one configured project: create, read, status, comment and close. No merge requests, code access, attachments or webhook sync. Source and synthetic fixture validation only; live provider acceptance remains pending. |
- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add an external ticket comment | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Tickets within the configured client and site: create, read, status, notes and close. No billing, contracts, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Close an external ticket | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Tickets within the configured client and site: create, read, status, notes and close. No billing, contracts, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Raise an external ticket | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Tickets within the configured client and site: create, read, status, notes and close. No billing, contracts, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Tickets within the configured client and site: create, read, status, notes and close. No billing, contracts, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket’s status | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Tickets within the configured client and site: create, read, status, notes and close. No billing, contracts, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Jira Cloud Issues
Section titled “Jira Cloud Issues”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add an external ticket comment | Limited availability | No simulation | Issues in one configured Jira Cloud project. No Jira Service Management request catalogue, SLA, portal or webhook integration. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Close an external ticket | Limited availability | No simulation | Issues in one configured Jira Cloud project. No Jira Service Management request catalogue, SLA, portal or webhook integration. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Raise an external ticket | Limited availability | No simulation | Issues in one configured Jira Cloud project. No Jira Service Management request catalogue, SLA, portal or webhook integration. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket | Limited availability | No simulation | Issues in one configured Jira Cloud project. No Jira Service Management request catalogue, SLA, portal or webhook integration. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket’s status | Limited availability | No simulation | Issues in one configured Jira Cloud project. No Jira Service Management request catalogue, SLA, portal or webhook integration. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Jira Service Management Cloud
Section titled “Jira Service Management Cloud”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add an external ticket comment | Limited availability | No simulation | Native customer requests in one configured service desk/request type with verified project, explicit write opt-in and configured close transition. No SLAs, attachment sync or webhooks. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Close an external ticket | Limited availability | No simulation | Native customer requests in one configured service desk/request type with verified project, explicit write opt-in and configured close transition. No SLAs, attachment sync or webhooks. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Raise an external ticket | Limited availability | No simulation | Native customer requests in one configured service desk/request type with verified project, explicit write opt-in and configured close transition. No SLAs, attachment sync or webhooks. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket | Limited availability | No simulation | Native customer requests in one configured service desk/request type with verified project, explicit write opt-in and configured close transition. No SLAs, attachment sync or webhooks. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket’s status | Limited availability | No simulation | Native customer requests in one configured service desk/request type with verified project, explicit write opt-in and configured close transition. No SLAs, attachment sync or webhooks. Source and synthetic fixture validation only; live provider acceptance remains pending. |
ServiceDesk Plus Cloud
Section titled “ServiceDesk Plus Cloud”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add an external ticket comment | Limited availability | No simulation | A Self Client registered by the school in the Zoho API console of its data centre, and a refresh token with SDPOnDemand.requests.CREATE, READ and UPDATE only, made by a technician kept for Plugboard. Requests in one ServiceDesk Plus Cloud portal, and one site when set: create, read, status, private or public notes and close, with explicit write opt-in. The data centre fixes every host; custom domains are refused. No requester, technician or field mapping, attachments, search or webhook synchronisation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Close an external ticket | Limited availability | No simulation | A Self Client registered by the school in the Zoho API console of its data centre, and a refresh token with SDPOnDemand.requests.CREATE, READ and UPDATE only, made by a technician kept for Plugboard. Requests in one ServiceDesk Plus Cloud portal, and one site when set: create, read, status, private or public notes and close, with explicit write opt-in. The data centre fixes every host; custom domains are refused. No requester, technician or field mapping, attachments, search or webhook synchronisation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Raise an external ticket | Limited availability | No simulation | A Self Client registered by the school in the Zoho API console of its data centre, and a refresh token with SDPOnDemand.requests.CREATE, READ and UPDATE only, made by a technician kept for Plugboard. Requests in one ServiceDesk Plus Cloud portal, and one site when set: create, read, status, private or public notes and close, with explicit write opt-in. The data centre fixes every host; custom domains are refused. No requester, technician or field mapping, attachments, search or webhook synchronisation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket | Limited availability | No simulation | A Self Client registered by the school in the Zoho API console of its data centre, and a refresh token with SDPOnDemand.requests.CREATE, READ and UPDATE only, made by a technician kept for Plugboard. Requests in one ServiceDesk Plus Cloud portal, and one site when set: create, read, status, private or public notes and close, with explicit write opt-in. The data centre fixes every host; custom domains are refused. No requester, technician or field mapping, attachments, search or webhook synchronisation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket’s status | Limited availability | No simulation | A Self Client registered by the school in the Zoho API console of its data centre, and a refresh token with SDPOnDemand.requests.CREATE, READ and UPDATE only, made by a technician kept for Plugboard. Requests in one ServiceDesk Plus Cloud portal, and one site when set: create, read, status, private or public notes and close, with explicit write opt-in. The data centre fixes every host; custom domains are refused. No requester, technician or field mapping, attachments, search or webhook synchronisation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
ServiceNow
Section titled “ServiceNow”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add an external ticket comment | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Incidents within the configured company: create, read, status, notes and close. No catalogue requests, CMDB, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Close an external ticket | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Incidents within the configured company: create, read, status, notes and close. No catalogue requests, CMDB, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Raise an external ticket | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Incidents within the configured company: create, read, status, notes and close. No catalogue requests, CMDB, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Incidents within the configured company: create, read, status, notes and close. No catalogue requests, CMDB, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket’s status | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Incidents within the configured company: create, read, status, notes and close. No catalogue requests, CMDB, attachments or webhook synchronization. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Web Help Desk
Section titled “Web Help Desk”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Close an external ticket | Limited availability | No simulation | Legacy REST ticket operations through the site agent on a REST-enabled installed version. SolarWinds Web Help Desk 2026.2.1 has no REST API. Confirm the exact supported version; no CMDB, attachment sync or webhook ingestion. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Raise an external ticket | Limited availability | No simulation | Legacy REST ticket operations through the site agent on a REST-enabled installed version. SolarWinds Web Help Desk 2026.2.1 has no REST API. Confirm the exact supported version; no CMDB, attachment sync or webhook ingestion. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket | Limited availability | No simulation | Legacy REST ticket operations through the site agent on a REST-enabled installed version. SolarWinds Web Help Desk 2026.2.1 has no REST API. Confirm the exact supported version; no CMDB, attachment sync or webhook ingestion. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read an external ticket’s status | Limited availability | No simulation | Legacy REST ticket operations through the site agent on a REST-enabled installed version. SolarWinds Web Help Desk 2026.2.1 has no REST API. Confirm the exact supported version; no CMDB, attachment sync or webhook ingestion. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Search external tickets | Limited availability | No simulation | External search is separately opt-in. Results use the school’s connector credential, not the individual technician’s vendor access. Legacy REST ticket operations through the site agent on a REST-enabled installed version. SolarWinds Web Help Desk 2026.2.1 has no REST API. Confirm the exact supported version; no CMDB, attachment sync or webhook ingestion. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Zendesk
Section titled “Zendesk”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add an external ticket comment | Live handler | No simulation | Provider configuration and school permissions apply. |
| Close an external ticket | Live handler | No simulation | Provider configuration and school permissions apply. |
| Raise an external ticket | Live handler | No simulation | Provider configuration and school permissions apply. |
| Read an external ticket | Live handler | No simulation | Provider configuration and school permissions apply. |
| Read an external ticket’s status | Live handler | No simulation | Provider configuration and school permissions apply. |
| Search external tickets | Live handler | No simulation | External search is separately opt-in. Results use the school’s connector credential, not the individual technician’s vendor access. |
Finance connectors
Section titled “Finance connectors”MYOB cloud purchasing
Section titled “MYOB cloud purchasing”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.operations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Check a finance document | Live handler | No simulation | School operations entitlement, operations.manage and integration.manage permissions, and an authorized Xero organisation or MYOB company file. Connector setup additionally requires connector.manage. Fixture-tested provider adapters; a sandbox or school-account pilot is still required. No automatic payments, bank feeds, payroll, journals, vendor webhooks or background finance synchronization. |
| Create a purchase order | Live handler | No simulation | School operations entitlement, operations.manage and integration.manage permissions, and an authorized Xero organisation or MYOB company file. Connector setup additionally requires connector.manage. Explicit purchase-write opt-in, current purchasing approval, account/tax mappings and a reviewed export. Bills require receipt of the purchase. Fixture-tested provider adapters; a sandbox or school-account pilot is still required. No automatic payments, bank feeds, payroll, journals, vendor webhooks or background finance synchronization. One export per purchase and document type across providers. Uncertain attempts require reconciliation before another send. Status checks do not change purchase approvals or actual costs. Creates Open MYOB service documents; bills may affect accounts immediately. An administrator must confirm the configured company currency. Only supported simple tax codes matching the approved line tax can be posted. |
| Create a supplier bill | Live handler | No simulation | School operations entitlement, operations.manage and integration.manage permissions, and an authorized Xero organisation or MYOB company file. Connector setup additionally requires connector.manage. Explicit purchase-write opt-in, current purchasing approval, account/tax mappings and a reviewed export. Bills require receipt of the purchase. Fixture-tested provider adapters; a sandbox or school-account pilot is still required. No automatic payments, bank feeds, payroll, journals, vendor webhooks or background finance synchronization. One export per purchase and document type across providers. Uncertain attempts require reconciliation before another send. Status checks do not change purchase approvals or actual costs. Creates Open MYOB service documents; bills may affect accounts immediately. An administrator must confirm the configured company currency. Only supported simple tax codes matching the approved line tax can be posted. |
| Read finance suppliers | Live handler | No simulation | School operations entitlement, operations.manage and integration.manage permissions, and an authorized Xero organisation or MYOB company file. Connector setup additionally requires connector.manage. Fixture-tested provider adapters; a sandbox or school-account pilot is still required. No automatic payments, bank feeds, payroll, journals, vendor webhooks or background finance synchronization. |
| Read purchasing accounts | Live handler | No simulation | School operations entitlement, operations.manage and integration.manage permissions, and an authorized Xero organisation or MYOB company file. Connector setup additionally requires connector.manage. Fixture-tested provider adapters; a sandbox or school-account pilot is still required. No automatic payments, bank feeds, payroll, journals, vendor webhooks or background finance synchronization. |
| Read tax codes | Live handler | No simulation | School operations entitlement, operations.manage and integration.manage permissions, and an authorized Xero organisation or MYOB company file. Connector setup additionally requires connector.manage. Fixture-tested provider adapters; a sandbox or school-account pilot is still required. No automatic payments, bank feeds, payroll, journals, vendor webhooks or background finance synchronization. |
Xero purchasing
Section titled “Xero purchasing”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.operations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Check a finance document | Live handler | No simulation | School operations entitlement, operations.manage and integration.manage permissions, and an authorized Xero organisation or MYOB company file. Connector setup additionally requires connector.manage. Fixture-tested provider adapters; a sandbox or school-account pilot is still required. No automatic payments, bank feeds, payroll, journals, vendor webhooks or background finance synchronization. |
| Create a purchase order | Live handler | No simulation | School operations entitlement, operations.manage and integration.manage permissions, and an authorized Xero organisation or MYOB company file. Connector setup additionally requires connector.manage. Explicit purchase-write opt-in, current purchasing approval, account/tax mappings and a reviewed export. Bills require receipt of the purchase. Fixture-tested provider adapters; a sandbox or school-account pilot is still required. No automatic payments, bank feeds, payroll, journals, vendor webhooks or background finance synchronization. One export per purchase and document type across providers. Uncertain attempts require reconciliation before another send. Status checks do not change purchase approvals or actual costs. Creates draft Xero documents for authorization in Xero. |
| Create a supplier bill | Live handler | No simulation | School operations entitlement, operations.manage and integration.manage permissions, and an authorized Xero organisation or MYOB company file. Connector setup additionally requires connector.manage. Explicit purchase-write opt-in, current purchasing approval, account/tax mappings and a reviewed export. Bills require receipt of the purchase. Fixture-tested provider adapters; a sandbox or school-account pilot is still required. No automatic payments, bank feeds, payroll, journals, vendor webhooks or background finance synchronization. One export per purchase and document type across providers. Uncertain attempts require reconciliation before another send. Status checks do not change purchase approvals or actual costs. Creates draft Xero documents for authorization in Xero. |
| Read finance suppliers | Live handler | No simulation | School operations entitlement, operations.manage and integration.manage permissions, and an authorized Xero organisation or MYOB company file. Connector setup additionally requires connector.manage. Fixture-tested provider adapters; a sandbox or school-account pilot is still required. No automatic payments, bank feeds, payroll, journals, vendor webhooks or background finance synchronization. |
| Read purchasing accounts | Live handler | No simulation | School operations entitlement, operations.manage and integration.manage permissions, and an authorized Xero organisation or MYOB company file. Connector setup additionally requires connector.manage. Fixture-tested provider adapters; a sandbox or school-account pilot is still required. No automatic payments, bank feeds, payroll, journals, vendor webhooks or background finance synchronization. |
| Read tax codes | Live handler | No simulation | School operations entitlement, operations.manage and integration.manage permissions, and an authorized Xero organisation or MYOB company file. Connector setup additionally requires connector.manage. Fixture-tested provider adapters; a sandbox or school-account pilot is still required. No automatic payments, bank feeds, payroll, journals, vendor webhooks or background finance synchronization. |
Identity and accounts
Section titled “Identity and accounts”Active Directory
Section titled “Active Directory”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.directory.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add a person to a group | Live handler | Fixtures available | The directory.manage permission, fresh multifactor verification, confirmation of the target and an audit record. The site agent on the school’s network with the connector assigned to its site; an LDAPS address (plain LDAP is refused), base DN, users OU and a service account delegated “create users and manage membership” on the users OU and named groups only, never Domain Admins. The bind password is held by the site agent. Explicit demo mode runs the same rules against a fictional demo directory; nothing changes in a real domain. Refuses groups that grant administrator rights (adminCount, Domain/Enterprise/Schema Admins, Administrators, the Operators groups, Group Policy Creator Owners, DnsAdmins, Key Admins), including groups nested inside them. |
| Assign or remove an identity licence | Unsupported | No simulation | The identity.license.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Change demonstration licences | Demo only | Fixtures available | Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Change demonstration mailbox delegates | Demo only | Fixtures available | Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Create an identity account | Live handler | Fixtures available | The identity.account.manage permission, fresh multifactor verification, confirmation of the target and an audit record. The site agent on the school’s network with the connector assigned to its site; an LDAPS address (plain LDAP is refused), base DN, users OU and a service account delegated “create users and manage membership” on the users OU and named groups only, never Domain Admins. The bind password is held by the site agent. Explicit demo mode runs the same rules against a fictional demo directory; nothing changes in a real domain. Searches by employee id first and adopts an existing account unchanged, so a retry repeats nothing. Refuses a sign-in name or address that belongs to another account, and any OU outside the users OU. Sets a random password nobody sees, generated on the agent and never returned; the first password is set at hand-over. |
| Enable or disable a demonstration account | Demo only | Fixtures available | Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Enable or disable an identity account | Live handler | Fixtures available | The identity.account.manage permission, fresh multifactor verification, confirmation of the target and an audit record. The site agent on the school’s network with the connector assigned to its site; an LDAPS address (plain LDAP is refused), base DN, users OU and a service account delegated “create users and manage membership” on the users OU and named groups only, never Domain Admins. The bind password is held by the site agent. Explicit demo mode runs the same rules against a fictional demo directory; nothing changes in a real domain. Refuses to change an account that itself holds administrator rights in Active Directory. |
| Find licences on disabled accounts | Unsupported | No simulation | The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Issue a temporary access pass | Unsupported | No simulation | The identity.tap.issue permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Manage Exchange mailbox delegation | Unsupported | No simulation | The identity.mailbox.delegate permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Move an account to another organisational unit | Live handler | Fixtures available | The directory.manage permission, fresh multifactor verification, confirmation of the target and an audit record. The site agent on the school’s network with the connector assigned to its site; an LDAPS address (plain LDAP is refused), base DN, users OU and a service account delegated “create users and manage membership” on the users OU and named groups only, never Domain Admins. The bind password is held by the site agent. Explicit demo mode runs the same rules against a fictional demo directory; nothing changes in a real domain. Refuses to change an account that itself holds administrator rights in Active Directory. |
| Read a directory account | Demo only | Fixtures available | Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Read a group’s members | Unsupported | No simulation | The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Read a person’s manager | Unsupported | No simulation | The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Read a person’s photo | Limited availability | No simulation | Read access to thumbnailPhoto through the site agent, and directory photos allowed in Settings, Photos. Staff only, and only for an account linked to the person; never matched by email. Re-encoded to WebP and stored in Plugboard. Fixture validation only; live pilot pending. Demo mode returns no photo. |
| Read Conditional Access policies | Unsupported | No simulation | The identity.policy.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Read directory groups | Live handler | Fixtures available | The identity.view permission and the provider’s consent/licence requirements for this read. The site agent on the school’s network with the connector assigned to its site; an LDAPS address (plain LDAP is refused), base DN, users OU and a service account delegated “create users and manage membership” on the users OU and named groups only, never Domain Admins. The bind password is held by the site agent. Explicit demo mode runs the same rules against a fictional demo directory; nothing changes in a real domain. |
| Read identity account status | Live handler | Fixtures available | The identity.view permission and the provider’s consent/licence requirements for this read. The site agent on the school’s network with the connector assigned to its site; an LDAPS address (plain LDAP is refused), base DN, users OU and a service account delegated “create users and manage membership” on the users OU and named groups only, never Domain Admins. The bind password is held by the site agent. Explicit demo mode runs the same rules against a fictional demo directory; nothing changes in a real domain. |
| Read multifactor registration | Unsupported | No simulation | The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Read organisation licence totals | Unsupported | No simulation | The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Read sign-in history | Unsupported | No simulation | The identity.signins.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Remove a person from a group | Live handler | Fixtures available | The directory.manage permission, fresh multifactor verification, confirmation of the target and an audit record. The site agent on the school’s network with the connector assigned to its site; an LDAPS address (plain LDAP is refused), base DN, users OU and a service account delegated “create users and manage membership” on the users OU and named groups only, never Domain Admins. The bind password is held by the site agent. Explicit demo mode runs the same rules against a fictional demo directory; nothing changes in a real domain. Refuses groups that grant administrator rights (adminCount, Domain/Enterprise/Schema Admins, Administrators, the Operators groups, Group Policy Creator Owners, DnsAdmins, Key Admins), including groups nested inside them. |
| Reset a demonstration password | Demo only | Fixtures available | Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Reset an identity password | Live handler | Fixtures available | The identity.password.reset permission, fresh multifactor verification, confirmation of the target and an audit record. The site agent on the school’s network with the connector assigned to its site; an LDAPS address (plain LDAP is refused), base DN, users OU and a service account delegated “create users and manage membership” on the users OU and named groups only, never Domain Admins. The bind password is held by the site agent. “Allow account recovery” turned on for the connection (off by default; turning it off stops these actions at once). Delegate “Write lockoutTime” and “Reset password” on the users OU to the service account. Explicit demo mode runs the same rules against a fictional demo directory; nothing changes in a real domain. Refused for any account holding an administrator role, and for a ticket requester without a recorded identity check. The person is told by email and text. Hourly ceilings per technician. Anything shown once (a temporary password or one-time codes) is never stored. Sets the school’s password preset (unicodePwd) and pwdLastSet 0 in one change, so a new password is required at next sign-in. |
| Reset multifactor methods | Unsupported | No simulation | The identity.mfa.reset permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Revoke sign-in sessions | Unsupported | No simulation | The identity.session.revoke permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Search directory accounts | Demo only | Fixtures available | Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Set reviewed account details (usage location, department, job title) | Live handler | Fixtures available | The directory.manage permission, fresh multifactor verification, confirmation of the target and an audit record. The site agent on the school’s network with the connector assigned to its site; an LDAPS address (plain LDAP is refused), base DN, users OU and a service account delegated “create users and manage membership” on the users OU and named groups only, never Domain Admins. The bind password is held by the site agent. Explicit demo mode runs the same rules against a fictional demo directory; nothing changes in a real domain. Refuses to change an account that itself holds administrator rights in Active Directory. Department, title, office, company and employee id only. Active Directory has no usage location; it is set in Microsoft Entra ID after the sync. |
| Unlock an identity account | Live handler | Fixtures available | The identity.account.enable permission, fresh multifactor verification, confirmation of the target and an audit record. The site agent on the school’s network with the connector assigned to its site; an LDAPS address (plain LDAP is refused), base DN, users OU and a service account delegated “create users and manage membership” on the users OU and named groups only, never Domain Admins. The bind password is held by the site agent. “Allow account recovery” turned on for the connection (off by default; turning it off stops these actions at once). Delegate “Write lockoutTime” and “Reset password” on the users OU to the service account. Explicit demo mode runs the same rules against a fictional demo directory; nothing changes in a real domain. Refused for any account holding an administrator role, and for a ticket requester without a recorded identity check. The person is told by email and text. Hourly ceilings per technician. Anything shown once (a temporary password or one-time codes) is never stored. |
Cisco Duo
Section titled “Cisco Duo”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.directory.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read identity account status | Limited availability | No simulation | The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. Account state, plus clearing a lockout and issuing bypass codes only when “Allow account recovery” is on; no enrolment changes, authentication logs or policy changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Reset multifactor methods | Limited availability | No simulation | The identity.mfa.reset permission, fresh multifactor verification, confirmation of the target and an audit record. “Allow account recovery” turned on for the connection (off by default; turning it off stops these actions at once). An Admin API integration with Grant resource - Write and Grant administrators - Read. Duo administrators are matched to users by email. Identity information and privileged identity actions are never simulated in demo mode. Refused for any account holding an administrator role, and for a ticket requester without a recorded identity check. The person is told by email and text. Hourly ceilings per technician. Anything shown once (a temporary password or one-time codes) is never stored. Bypass codes only: one to three single-use codes, valid for at most eight hours, replacing any earlier codes. Account state, plus clearing a lockout and issuing bypass codes only when “Allow account recovery” is on; no enrolment changes, authentication logs or policy changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Unlock an identity account | Limited availability | No simulation | The identity.account.enable permission, fresh multifactor verification, confirmation of the target and an audit record. “Allow account recovery” turned on for the connection (off by default; turning it off stops these actions at once). An Admin API integration with Grant resource - Write and Grant administrators - Read. Duo administrators are matched to users by email. Identity information and privileged identity actions are never simulated in demo mode. Refused for any account holding an administrator role, and for a ticket requester without a recorded identity check. The person is told by email and text. Hourly ceilings per technician. Anything shown once (a temporary password or one-time codes) is never stored. Only a user Duo reports as locked out, and only to active; never bypass. Account state, plus clearing a lockout and issuing bypass codes only when “Allow account recovery” is on; no enrolment changes, authentication logs or policy changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Google Cloud Directory Sync
Section titled “Google Cloud Directory Sync”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.directory.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read when the directory last synced, and its errors | Live handler | Fixtures available | The site agent installed on the GCDS host, with the absolute paths of sync-cmd and its saved configuration file set by an administrator. Knows only the runs Plugboard started since the site agent last restarted; GCDS’s own scheduled runs are not visible. Explicit demo mode answers without touching a sync server or tenant. |
| Sync directory records | Live handler | Fixtures available | The site agent installed on the GCDS host, with the absolute paths of sync-cmd and its saved configuration file set by an administrator. The directory.manage permission and a person’s go-ahead on the flow step; the intent is audited before the call. Starts sync-cmd -a -c with the configured file and answers at once; a sync that is still running is reported, not started twice. Explicit demo mode answers without touching a sync server or tenant. |
Google Workspace (Directory)
Section titled “Google Workspace (Directory)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.directory.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add a person to a group | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/admin.directory.group.member. A school can set this to act as the technician’s own Google admin account through domain-wide delegation, under Settings, Connectors, Run as. The directory.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. |
| Assign or remove an identity licence | Unsupported | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.license.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Change demonstration licences | Demo only | Fixtures available | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Change demonstration mailbox delegates | Demo only | Fixtures available | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Convert a mailbox to a shared mailbox | Unsupported | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.account.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Create an identity account | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/admin.directory.user. The identity.account.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. |
| Enable or disable a demonstration account | Demo only | Fixtures available | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Enable or disable an identity account | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/admin.directory.user. A school can set this to act as the technician’s own Google admin account through domain-wide delegation, under Settings, Connectors, Run as. The identity.account.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. |
| Find licences on disabled accounts | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/apps.licensing. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. Known SKU assignments and a bounded account scan; this is not a completeness guarantee for the whole school. |
| Hide or show a mailbox in the address book | Unsupported | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.account.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Issue a temporary access pass | Unsupported | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.tap.issue permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Manage Exchange mailbox delegation | Unsupported | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.mailbox.delegate permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Move an account to another organisational unit | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/admin.directory.user. The directory.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. |
| Publish an approved booking or event to a calendar | Live handler | No simulation | Calendar API application consent or delegated service-account access; each target mailbox/calendar must be explicitly listed in the connector calendar allowlist. Creates or updates an event on an allowlisted calendar only when calendar publishing is enabled in connector settings. Provider access must cover that calendar. |
| Read a directory account | Limited availability | Fixtures available | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. Enable management reads with a verified Google customer and primary domain, a delegated administrator, and selected exact organizational unit paths. Requires admin.directory.customer.readonly and admin.directory.user.readonly delegation. Read-only People Accounts search and preview. Search scans at most 5000 customer accounts and returns at most 25 matches within selected exact organizational units; descendants are excluded. Licence, group and delegation details are not collected by this lookup. Source and fixture checks passed; live pilot acceptance remains pending. |
| Read a group’s members | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. |
| Read a person’s manager | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. |
| Read a person’s photo | Limited availability | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. Management reads with selected organizational units and admin.directory.user.readonly delegation, and directory photos allowed in Settings, Photos. Staff only, and only for an account linked to the person; never matched by email. Re-encoded to WebP and stored in Plugboard. Fixture validation only; live pilot pending. Demo mode returns no photo. |
| Read Conditional Access policies | Unsupported | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.policy.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Read directory groups | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. |
| Read identity account status | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. |
| Read multifactor registration | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. Google reports 2-Step Verification enrolment, not the list of registered methods. |
| Read organisation licence totals | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/apps.licensing. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. Counts known Google education SKU assignments; does not establish purchased capacity and is not a complete contract register. |
| Read room or staff calendar availability | Live handler | No simulation | Calendar API application consent or delegated service-account access; each target mailbox/calendar must be explicitly listed in the connector calendar allowlist. Availability is read from the selected provider; a failed or unsupported response does not establish that a room is free. |
| Read selected shared-drive root access summaries | Limited availability | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. Provider entitlement, explicitly selected scope and documented administrator consent. See the connector setup guide; real-tenant pilot remains. Explicit connector viewer read with connector.manage, the relevant documentation/directory/security permission and enabled modules. Tenant-wide alerts, audit, XDR, labels and service health require organisation coverage and an unscoped authorised actor. Domain-wide delegation and verified customer/domain. Alert Center requires apps.alerts (broader than a read-only permission); shared-drive reads require explicit drive.readonly and verified domain-read consent. Allowlisted root metadata and direct grants only; accessible drive membership does not establish customer ownership, full file sharing or effective access. |
| Read selected Workspace audit event summaries | Limited availability | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. Provider entitlement, explicitly selected scope and documented administrator consent. See the connector setup guide; real-tenant pilot remains. Explicit connector viewer read with connector.manage, the relevant documentation/directory/security permission and enabled modules. Tenant-wide alerts, audit, XDR, labels and service health require organisation coverage and an unscoped authorised actor. Domain-wide delegation and verified customer/domain. Alert Center requires apps.alerts (broader than a read-only permission); shared-drive reads require explicit drive.readonly and verified domain-read consent. |
| Read sign-in history | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.signins.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. |
| Read Teams presence or calendar status for technicians and, when switched on, staff requesters | Limited availability | No simulation | Domain-wide delegation for calendar.freebusy (impersonating the configured administrator) and calendar.events.owned.readonly (impersonating each person, for out-of-office and focus time). Polled, not pushed: Teams every minute while anyone has the desk open and every ten minutes otherwise, Google Calendar every five minutes. Display only, overwritten in place and never kept as a history. Staff requesters only when the Microsoft Entra staff-status switch is on; students never. |
| Read Workspace security alert summaries | Limited availability | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/apps.alerts, with the allowManagementReads setting on. Provider entitlement, explicitly selected scope and documented administrator consent. See the connector setup guide; real-tenant pilot remains. Explicit connector viewer read with connector.manage, the relevant documentation/directory/security permission and enabled modules. Tenant-wide alerts, audit, XDR, labels and service health require organisation coverage and an unscoped authorised actor. Domain-wide delegation and verified customer/domain. Alert Center requires apps.alerts (broader than a read-only permission); shared-drive reads require explicit drive.readonly and verified domain-read consent. |
| Read Workspace usage and account protection summaries | Limited availability | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. |
| Remove a person from a group | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/admin.directory.group.member. A school can set this to act as the technician’s own Google admin account through domain-wide delegation, under Settings, Connectors, Run as. The directory.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. |
| Reset a demonstration password | Demo only | Fixtures available | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Reset an identity password | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/admin.directory.user, with the allowAccountRecovery setting on. The identity.password.reset permission, fresh multifactor verification, confirmation of the target and an audit record. “Allow account recovery” turned on for the connection (off by default; turning it off stops these actions at once). Identity information and privileged identity actions are never simulated in demo mode. Refused for any account holding an administrator role, and for a ticket requester without a recorded identity check. The person is told by email and text, and a staff member’s manager by email where Google Workspace records one. Hourly ceilings per technician. Anything shown once (a temporary password or one-time codes) is never stored. Sets the school’s Student or Staff password preset with a change required at next sign-in. Needs admin.directory.user delegation. |
| Reset multifactor methods | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/admin.directory.user.security, with the allowAccountRecovery setting on. The identity.mfa.reset permission, fresh multifactor verification, confirmation of the target and an audit record. “Allow account recovery” turned on for the connection (off by default; turning it off stops these actions at once). Identity information and privileged identity actions are never simulated in demo mode. Refused for any account holding an administrator role, and for a ticket requester without a recorded identity check. The person is told by email and text, and a staff member’s manager by email where Google Workspace records one. Hourly ceilings per technician. Anything shown once (a temporary password or one-time codes) is never stored. Turns 2-Step Verification off, or issues a fresh set of backup codes shown once. Needs admin.directory.user.security delegation. |
| Revoke sign-in sessions | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/admin.directory.user.security. A school can set this to act as the technician’s own Google admin account through domain-wide delegation, under Settings, Connectors, Run as. The identity.session.revoke permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. |
| Search directory accounts | Limited availability | Fixtures available | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. Enable management reads with a verified Google customer and primary domain, a delegated administrator, and selected exact organizational unit paths. Requires admin.directory.customer.readonly and admin.directory.user.readonly delegation. Read-only People Accounts search and preview. Search scans at most 5000 customer accounts and returns at most 25 matches within selected exact organizational units; descendants are excluded. Licence, group and delegation details are not collected by this lookup. Source and fixture checks passed; live pilot acceptance remains pending. |
| Send a workflow notification to Teams or Google Chat | Live handler | No simulation | A configured Teams Workflows or Google Chat incoming webhook, sealed with the existing directory connector credentials. Sends to the configured channel webhook only. This is not a general Teams or Google Chat conversation mirror. |
| Set or clear a mailbox’s automatic reply | Unsupported | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.account.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Set reviewed account details (usage location, department, job title) | Live handler | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/admin.directory.user. The directory.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Domain-wide delegation for admin.directory.user. Identity information and privileged identity actions are never simulated in demo mode. Department, title, company, office and the organisation employee id only. Google has no usage location; that field is refused. |
| Unlock an identity account | Unsupported | No simulation | Google Workspace > Google Workspace (Directory): needs https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly. The identity.account.enable permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
Grouper
Section titled “Grouper”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.directory.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a group’s members | Limited availability | No simulation | The identity.view permission and the provider’s consent/licence requirements for this read. A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Identity information and privileged identity actions are never simulated in demo mode. Verified catalogue and read-only membership of explicitly allowed groups. Unknown group safety properties keep membership changes unavailable. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read directory groups | Limited availability | No simulation | The identity.view permission and the provider’s consent/licence requirements for this read. A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Identity information and privileged identity actions are never simulated in demo mode. Verified catalogue and read-only membership of explicitly allowed groups. Unknown group safety properties keep membership changes unavailable. Source and synthetic fixture validation only; live provider acceptance remains pending. |
JumpCloud
Section titled “JumpCloud”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.directory.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read identity account status | Limited availability | No simulation | The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. Account state, plus unlock, password expiry and a fresh MFA enrolment only when “Allow account recovery” is on; no provisioning, group changes or device management. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Reset an identity password | Limited availability | No simulation | The identity.password.reset permission, fresh multifactor verification, confirmation of the target and an audit record. “Allow account recovery” turned on for the connection (off by default; turning it off stops these actions at once). Identity information and privileged identity actions are never simulated in demo mode. Refused for any account holding an administrator role, and for a ticket requester without a recorded identity check. The person is told by email and text. Hourly ceilings per technician. Anything shown once (a temporary password or one-time codes) is never stored. Expires the password; JumpCloud sets none, and the person chooses a new one through JumpCloud. Account state, plus unlock, password expiry and a fresh MFA enrolment only when “Allow account recovery” is on; no provisioning, group changes or device management. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Reset multifactor methods | Limited availability | No simulation | The identity.mfa.reset permission, fresh multifactor verification, confirmation of the target and an audit record. “Allow account recovery” turned on for the connection (off by default; turning it off stops these actions at once). Identity information and privileged identity actions are never simulated in demo mode. Refused for any account holding an administrator role, and for a ticket requester without a recorded identity check. The person is told by email and text. Hourly ceilings per technician. Anything shown once (a temporary password or one-time codes) is never stored. Starts a new TOTP enrolment with a one-day exclusion. JumpCloud administrator status is read from the user’s admin object; when it is absent the account is refused. Account state, plus unlock, password expiry and a fresh MFA enrolment only when “Allow account recovery” is on; no provisioning, group changes or device management. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Unlock an identity account | Limited availability | No simulation | The identity.account.enable permission, fresh multifactor verification, confirmation of the target and an audit record. “Allow account recovery” turned on for the connection (off by default; turning it off stops these actions at once). Identity information and privileged identity actions are never simulated in demo mode. Refused for any account holding an administrator role, and for a ticket requester without a recorded identity check. The person is told by email and text. Hourly ceilings per technician. Anything shown once (a temporary password or one-time codes) is never stored. Account state, plus unlock, password expiry and a fresh MFA enrolment only when “Allow account recovery” is on; no provisioning, group changes or device management. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft 365 Administrative Diagnostics
Section titled “Microsoft 365 Administrative Diagnostics”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A connector agent on the school network is required, on hosted and self-hosted deployments alike.
- Connector category entitlement:
module.directory.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read bounded delivery traces for one approved mailbox | Limited availability | No simulation | Microsoft 365 > Microsoft 365 Administrative Diagnostics: needs Exchange.ManageAsApp, Exchange Administrator or a scoped role group, Teams Administrator. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Windows site agent, approved exact mailbox/user IDs, pinned PowerShell executable and official Exchange/Teams modules, approved certificate and least-privilege management roles. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Explicitly approved Exchange mailbox diagnostics, bounded delivery traces and selected effective Teams policy settings through an isolated site agent with pinned official modules. No arbitrary commands, policy changes or mailbox content. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read one approved Exchange mailbox’s usage and quota | Limited availability | No simulation | Microsoft 365 > Microsoft 365 Administrative Diagnostics: needs Exchange.ManageAsApp, Exchange Administrator or a scoped role group, Teams Administrator. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Windows site agent, approved exact mailbox/user IDs, pinned PowerShell executable and official Exchange/Teams modules, approved certificate and least-privilege management roles. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Explicitly approved Exchange mailbox diagnostics, bounded delivery traces and selected effective Teams policy settings through an isolated site agent with pinned official modules. No arbitrary commands, policy changes or mailbox content. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read one approved user’s effective Teams policies | Limited availability | No simulation | Microsoft 365 > Microsoft 365 Administrative Diagnostics: needs Exchange.ManageAsApp, Exchange Administrator or a scoped role group, Teams Administrator, TeamsUserConfiguration.Read.All, with the allowEffectivePolicy setting on. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Windows site agent, approved exact mailbox/user IDs, pinned PowerShell executable and official Exchange/Teams modules, approved certificate and least-privilege management roles. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Explicitly approved Exchange mailbox diagnostics, bounded delivery traces and selected effective Teams policy settings through an isolated site agent with pinned official modules. No arbitrary commands, policy changes or mailbox content. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft Entra Connect Sync
Section titled “Microsoft Entra Connect Sync”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.directory.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read when the directory last synced, and its errors | Live handler | Fixtures available | The site agent installed on the active (not staging) Entra Connect sync server, its account in the ADSyncOperators group, and the connector assigned to that site. Reads the scheduler and the last run profile result (Get-ADSyncScheduler, Get-ADSyncConnectorRunStatus, Get-ADSyncRunProfileResult) only. Explicit demo mode answers without touching a sync server or tenant. |
| Sync directory records | Live handler | Fixtures available | The site agent installed on the active (not staging) Entra Connect sync server, its account in the ADSyncOperators group, and the connector assigned to that site. The directory.manage permission and a person’s go-ahead on the flow step; the intent is audited before the call. Runs Start-ADSyncSyncCycle -PolicyType Delta and nothing else; answers “started” or “a sync is already running”. Nothing from a flow reaches the command. Explicit demo mode answers without touching a sync server or tenant. |
Microsoft Entra ID
Section titled “Microsoft Entra ID”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.directory.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Activate an eligible admin role as the person themselves | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.view permission and the provider’s consent/licence requirements for this read. The person’s own interactive Microsoft sign-in at that moment, with the school’s admin consent for the delegated PIM scope. Plugboard holds no permission that can grant or remove a role. Identity information and privileged identity actions are never simulated in demo mode. The connector’s own credentials never do this; Microsoft’s MFA, authentication context and the role’s approval rules stay in force. |
| Activate eligible PIM group membership as the person themselves | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.view permission and the provider’s consent/licence requirements for this read. The person’s own interactive Microsoft sign-in at that moment, with the school’s admin consent for the delegated PIM scope. Plugboard holds no permission that can grant or remove a role. Identity information and privileged identity actions are never simulated in demo mode. The connector’s own credentials never do this; Microsoft’s MFA, authentication context and the role’s approval rules stay in force. |
| Add a person to a group | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The directory.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. Groups with Privileged Identity Management eligibility are refused as well; checking needs PrivilegedEligibilitySchedule.Read.AzureADGroup, and without it membership stays read-only. |
| Approve or deny a PIM group request as the approver themselves | Unsupported | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. Approvers decide as themselves in Microsoft Entra for now. |
| Assign or remove an identity licence | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.license.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. |
| Change demonstration licences | Demo only | Fixtures available | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Change demonstration mailbox delegates | Demo only | Fixtures available | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Convert a mailbox to a shared mailbox | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.account.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Leaver mailbox changes switched on for this connector, the Exchange certificate used for mailbox delegation, and an Exchange role for the app limited to Get/Set-Mailbox and Get/Set-MailboxAutoReplyConfiguration. Identity information and privileged identity actions are never simulated in demo mode. Checked first; a mailbox that is already shared is left alone. Convert before removing the licence, or the mail goes with it. |
| Create an identity account | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.account.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. |
| Enable or disable a demonstration account | Demo only | Fixtures available | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Enable or disable an identity account | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.account.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. |
| End an admin role activation as the person themselves | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.view permission and the provider’s consent/licence requirements for this read. The person’s own interactive Microsoft sign-in at that moment, with the school’s admin consent for the delegated PIM scope. Plugboard holds no permission that can grant or remove a role. Identity information and privileged identity actions are never simulated in demo mode. The connector’s own credentials never do this; Microsoft’s MFA, authentication context and the role’s approval rules stay in force. |
| Find licences on disabled accounts | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. |
| Hide or show a mailbox in the address book | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.account.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Leaver mailbox changes switched on for this connector, the Exchange certificate used for mailbox delegation, and an Exchange role for the app limited to Get/Set-Mailbox and Get/Set-MailboxAutoReplyConfiguration. Identity information and privileged identity actions are never simulated in demo mode. Hides or shows again; checked first. |
| Issue a temporary access pass | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.tap.issue permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. |
| Manage Exchange mailbox delegation | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.mailbox.delegate permission, fresh multifactor verification, confirmation of the target and an audit record. Separately enabled mailbox delegation, an Exchange certificate and reviewed Exchange RBAC. The validated setup uses five commands: Get/Add/Remove-MailboxPermission and Get/Remove-RecipientPermission. Add-RecipientPermission is excluded. Identity information and privileged identity actions are never simulated in demo mode. The earlier six-command setup allowed an out-of-scope Send As grant in two live pilots, despite the recipient-scope lookup excluding that mailbox. That Send As credential boundary was not accepted; a healthy connection does not validate scope. |
| Grant Full Access | Live handler | No simulation | The identity.mailbox.fullaccess permission in addition to mailbox delegation permission, step-up authentication, explicit enablement, certificate and the reviewed Exchange role. The live Full Access pilot passed grant, repeated grant and revocation, and refused an out-of-scope request. Confirm the deployed role and scope match the tested setup; this does not validate Send As grants. |
| Grant Send As | Blocked | No simulation | Blocked in the application and connector before Exchange authentication. No configuration override enables this grant. |
| Revoke Full Access | Live handler | No simulation | Mailbox delegation permission, step-up authentication, certificate and explicit connector enablement. Available for authorised removal and cleanup; does not establish that grant scope is safe. |
| Revoke Send As | Live handler | No simulation | Mailbox delegation permission, step-up authentication, certificate and explicit connector enablement. Available for authorised removal and cleanup within Exchange permissions while new Send As grants remain blocked. The pilot’s out-of-scope removal was refused to the app and required independent Exchange administrator cleanup. |
| Move an account to another organisational unit | Unsupported | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The directory.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| Publish an approved booking or event to a calendar | Live handler | No simulation | Calendar API application consent or delegated service-account access; each target mailbox/calendar must be explicitly listed in the connector calendar allowlist. Creates or updates an event on an allowlisted calendar only when calendar publishing is enabled in connector settings. Provider access must cover that calendar. |
| Read a directory account | Live handler | Fixtures available | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. Graph application consent for account, membership and licence reads. Demo mode must be disabled to read real accounts. The People Accounts consumer invokes Graph for these two Entra reads. Explicit demo mode returns fictional accounts. Mailbox delegates are not verified by this account response; missing sub-reads must not establish absence. Legacy directory write actions remain demonstration-only. |
| Read a group’s members | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. |
| Read a person’s eligible admin roles and their PIM settings | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All, RoleEligibilitySchedule.Read.Directory, RoleManagementPolicy.Read.Directory. The identity.view permission and the provider’s consent/licence requirements for this read. Microsoft Entra ID P2 (Microsoft 365 A5 includes it). Read-only permissions only, never the ReadWrite or Remove variants. Identity information and privileged identity actions are never simulated in demo mode. Built on roleManagement/directory only; eligibility through role-assignable groups is read group by group. Tenant-wide eligibility only. |
| Read a person’s manager | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. |
| Read a person’s photo | Limited availability | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. Graph application consent for ProfilePhoto.Read.All (least privilege) or User.Read.All, and “Also use photos from Microsoft 365 or Google” turned on in Settings, Photos. Staff only, and only for an account linked to the person; never matched by email. Re-encoded to WebP and stored in Plugboard. Fixture validation only; live pilot pending. Demo mode returns no photo. |
| Read active admin role assignments | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All, RoleAssignmentSchedule.Read.Directory. The identity.view permission and the provider’s consent/licence requirements for this read. Microsoft Entra ID P2 (Microsoft 365 A5 includes it). Read-only permissions only, never the ReadWrite or Remove variants. Identity information and privileged identity actions are never simulated in demo mode. Built on roleManagement/directory only; eligibility through role-assignable groups is read group by group. Tenant-wide eligibility only. |
| Read Conditional Access policies | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.policy.view permission and the provider’s consent/licence requirements for this read. Suitable Microsoft licensing and Graph application consent; missing access is reported rather than treated as an empty result. Identity information and privileged identity actions are never simulated in demo mode. |
| Read directory groups | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. |
| Read Entra MFA registration totals, without names | Limited availability | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. |
| Read identity account status | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. |
| Read multifactor registration | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. |
| Read one admin role’s PIM settings | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All, RoleManagementPolicy.Read.Directory. The identity.view permission and the provider’s consent/licence requirements for this read. Microsoft Entra ID P2 (Microsoft 365 A5 includes it). Read-only permissions only, never the ReadWrite or Remove variants. Identity information and privileged identity actions are never simulated in demo mode. Built on roleManagement/directory only; eligibility through role-assignable groups is read group by group. Tenant-wide eligibility only. |
| Read organisation licence totals | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. |
| Read PIM’s own audit entries | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.view permission and the provider’s consent/licence requirements for this read. Microsoft Entra ID P2 (Microsoft 365 A5 includes it). Read-only permissions only, never the ReadWrite or Remove variants. Identity information and privileged identity actions are never simulated in demo mode. Built on roleManagement/directory only; eligibility through role-assignable groups is read group by group. Tenant-wide eligibility only. |
| Read room or staff calendar availability | Live handler | No simulation | Calendar API application consent or delegated service-account access; each target mailbox/calendar must be explicitly listed in the connector calendar allowlist. Availability is read from the selected provider; a failed or unsupported response does not establish that a room is free. |
| Read sign-in history | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.signins.view permission and the provider’s consent/licence requirements for this read. Suitable Microsoft licensing and Graph application consent; missing access is reported rather than treated as an empty result. Identity information and privileged identity actions are never simulated in demo mode. |
| Read Teams presence or calendar status for technicians and, when switched on, staff requesters | Limited availability | No simulation | The Microsoft Graph application permission Presence.Read.All with admin consent, and User.Read.All to find an account by address. Polled, not pushed: Teams every minute while anyone has the desk open and every ten minutes otherwise, Google Calendar every five minutes. Display only, overwritten in place and never kept as a history. Staff requesters only when the Microsoft Entra staff-status switch is on; students never. |
| Read when the directory last synced, and its errors | Live handler | Fixtures available | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All, Synchronization.Read.All. Entra Cloud Sync: the provisioning service principal and job ids in the connector settings, and Graph application consent for Synchronization.ReadWrite.All (Synchronization.Read.All for status). Reads the job’s last run, last success, interval and quarantine state; whether a cycle is running now is not reported. Explicit demo mode answers without touching a sync server or tenant. |
| Remove a person from a group | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The directory.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. Groups with Privileged Identity Management eligibility are refused as well; checking needs PrivilegedEligibilitySchedule.Read.AzureADGroup, and without it membership stays read-only. |
| Reset a demonstration password | Demo only | Fixtures available | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. Explicitly enable built-in demo data. Fictional directory records only. These legacy actions do not read or change the school’s real directory. |
| Reset an identity password | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.password.reset permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. |
| Reset multifactor methods | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.mfa.reset permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. |
| Revoke sign-in sessions | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.session.revoke permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. |
| Search directory accounts | Live handler | Fixtures available | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. Graph application consent for account, membership and licence reads. Demo mode must be disabled to read real accounts. The People Accounts consumer invokes Graph for these two Entra reads. Explicit demo mode returns fictional accounts. Mailbox delegates are not verified by this account response; missing sub-reads must not establish absence. Legacy directory write actions remain demonstration-only. |
| Send a workflow notification to Teams or Google Chat | Live handler | No simulation | A configured Teams Workflows or Google Chat incoming webhook, sealed with the existing directory connector credentials. Sends to the configured channel webhook only. This is not a general Teams or Google Chat conversation mirror. |
| Set or clear a mailbox’s automatic reply | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.account.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Leaver mailbox changes switched on for this connector, the Exchange certificate used for mailbox delegation, and an Exchange role for the app limited to Get/Set-Mailbox and Get/Set-MailboxAutoReplyConfiguration. Identity information and privileged identity actions are never simulated in demo mode. One message for internal and external senders, sent as plain text; an empty message turns the reply off. Checked before it is set. |
| Set reviewed account details (usage location, department, job title) | Live handler | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The directory.manage permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. Usage location, department, job title, office, company and employee id only. A synced account’s details other than usage location are set in Active Directory, and Microsoft refuses them here. |
| Sync directory records | Live handler | Fixtures available | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All, Synchronization.ReadWrite.All. Entra Cloud Sync: the provisioning service principal and job ids in the connector settings, and Graph application consent for Synchronization.ReadWrite.All (Synchronization.Read.All for status). The directory.manage permission and a person’s go-ahead on the flow step; the intent is audited before the call. Provisions one account on demand by its Active Directory distinguished name, so it follows the Active Directory create step. Does not start a full cycle. Explicit demo mode answers without touching a sync server or tenant. |
| Unlock an identity account | Unsupported | No simulation | Microsoft 365 > Microsoft Entra ID: needs AuditLog.Read.All, Policy.Read.All, UserAuthenticationMethod.Read.All, User.Read.All, Organization.Read.All, Group.Read.All. The identity.account.enable permission, fresh multifactor verification, confirmation of the target and an audit record. Identity information and privileged identity actions are never simulated in demo mode. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
Microsoft Teams
Section titled “Microsoft Teams”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.directory.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read selected Teams channel membership context | Limited availability | No simulation | Microsoft 365 > Microsoft Teams: needs Team.ReadBasic.All, Channel.ReadBasic.All. Explicit read opt-in where configured, selected native scope and documented provider consent; real-provider acceptance remains outstanding. Use the operational integration view with connector.manage and the relevant module/read permission. Tenant-wide administrative views require organisation coverage without a campus filter. Bounded native metadata only; missing entitlement, incomplete data and unknown provider fields do not become a healthy or compliant assessment. Native outbound messages in one verified team/channel through a delegated Microsoft sign-in and explicit write opt-in. Microsoft offers no application permission for channel posts, so a refresh token is stored sealed and rotated as it is used; if it is revoked, sign in again. No inbound sync or file uploads. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read selected Teams membership, channels and settings | Limited availability | No simulation | Microsoft 365 > Microsoft Teams: needs Team.ReadBasic.All, Channel.ReadBasic.All. Provider entitlement, explicitly selected scope and documented administrator consent. See the connector setup guide; real-tenant pilot remains. Explicit connector viewer read with connector.manage, the relevant documentation/directory/security permission and enabled modules. Tenant-wide alerts, audit, XDR, labels and service health require organisation coverage and an unscoped authorised actor. Selected team membership and channel metadata; no private messages or inferred access to channel contents. Native outbound messages in one verified team/channel through a delegated Microsoft sign-in and explicit write opt-in. Microsoft offers no application permission for channel posts, so a refresh token is stored sealed and rotated as it is used; if it is revoked, sign in again. No inbound sync or file uploads. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Send a workflow notification to Teams or Google Chat | Limited availability | No simulation | A delegated Microsoft sign-in (refresh token with offline_access) for the configured tenant/team/channel with Channel.ReadBasic.All and ChannelMessage.Send permissions, and explicit allowWrites opt-in. Plugboard renews the access token and keeps the newest refresh token. Native outbound messages to the configured channel only. Provider acceptance does not establish recipient delivery. No incoming message sync or file uploads. Microsoft offers no application permission for regular channel posts, so sending uses a delegated sign-in; if it is revoked, sign in again. No shared-channel sending. Native outbound messages in one verified team/channel through a delegated Microsoft sign-in and explicit write opt-in. Microsoft offers no application permission for channel posts, so a refresh token is stored sealed and rotated as it is used; if it is revoked, sign in again. No inbound sync or file uploads. Source and synthetic fixture validation only; live provider acceptance remains pending. |
- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.directory.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read identity account status | Limited availability | No simulation | The identity.view permission and the provider’s consent/licence requirements for this read. Identity information and privileged identity actions are never simulated in demo mode. Account state in the configured organisation, plus unlock, password reset and MFA reset only when “Allow account recovery” is on. No provisioning or group changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Reset an identity password | Limited availability | No simulation | The identity.password.reset permission, fresh multifactor verification, confirmation of the target and an audit record. “Allow account recovery” turned on for the connection (off by default; turning it off stops these actions at once). An API token from an administrator allowed to manage users (okta.users.manage) and read their roles (okta.roles.read). Identity information and privileged identity actions are never simulated in demo mode. Refused for any account holding an administrator role, and for a ticket requester without a recorded identity check. The person is told by email and text. Hourly ceilings per technician. Anything shown once (a temporary password or one-time codes) is never stored. Okta chooses the temporary password and revokes current sessions. Accounts sourced from Active Directory are refused by Okta. Account state in the configured organisation, plus unlock, password reset and MFA reset only when “Allow account recovery” is on. No provisioning or group changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Reset multifactor methods | Limited availability | No simulation | The identity.mfa.reset permission, fresh multifactor verification, confirmation of the target and an audit record. “Allow account recovery” turned on for the connection (off by default; turning it off stops these actions at once). An API token from an administrator allowed to manage users (okta.users.manage) and read their roles (okta.roles.read). Identity information and privileged identity actions are never simulated in demo mode. Refused for any account holding an administrator role, and for a ticket requester without a recorded identity check. The person is told by email and text. Hourly ceilings per technician. Anything shown once (a temporary password or one-time codes) is never stored. Resets every enrolled factor; Okta has no backup codes. Account state in the configured organisation, plus unlock, password reset and MFA reset only when “Allow account recovery” is on. No provisioning or group changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Unlock an identity account | Limited availability | No simulation | The identity.account.enable permission, fresh multifactor verification, confirmation of the target and an audit record. “Allow account recovery” turned on for the connection (off by default; turning it off stops these actions at once). An API token from an administrator allowed to manage users (okta.users.manage) and read their roles (okta.roles.read). Identity information and privileged identity actions are never simulated in demo mode. Refused for any account holding an administrator role, and for a ticket requester without a recorded identity check. The person is told by email and text. Hourly ceilings per technician. Anything shown once (a temporary password or one-time codes) is never stored. Account state in the configured organisation, plus unlock, password reset and MFA reset only when “Allow account recovery” is on. No provisioning or group changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.directory.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Send a workflow notification to Teams or Google Chat | Limited availability | No simulation | A bot token for the verified workspace, chat:write and channels:read or groups:read permissions, membership of the configured channel, and explicit allowWrites opt-in. Native outbound messages to the configured channel only. Provider acceptance does not establish recipient delivery. No incoming message sync or file uploads. Native outbound messages in one verified workspace/channel, only with explicit write opt-in. Provider acceptance is not receipt; no inbound sync or file uploads. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Learning systems
Section titled “Learning systems”Canvas
Section titled “Canvas”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read learning courses | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Read-only course and enrolment context; no grades, submissions or writeback. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read learning enrolments | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Read-only course and enrolment context; no grades, submissions or writeback. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Google Classroom
Section titled “Google Classroom”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read learning courses | Limited availability | No simulation | Google Workspace > Google Classroom: needs https://www.googleapis.com/auth/classroom.courses.readonly, https://www.googleapis.com/auth/classroom.rosters.readonly. Read-only courses and enrolments through a school-authorized delegated service account; no assignments or grades. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read learning enrolments | Limited availability | No simulation | Google Workspace > Google Classroom: needs https://www.googleapis.com/auth/classroom.courses.readonly, https://www.googleapis.com/auth/classroom.rosters.readonly. Read-only courses and enrolments through a school-authorized delegated service account; no assignments or grades. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Moodle
Section titled “Moodle”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read learning courses | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Read-only course and enrolment context through explicitly granted web-service functions; no grades or writeback. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read learning enrolments | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Read-only course and enrolment context through explicitly granted web-service functions; no grades or writeback. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Schoology
Section titled “Schoology”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read learning courses | Limited availability | No simulation | Read-only course and enrolment context; no grades, submissions or writeback. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read learning enrolments | Limited availability | No simulation | Read-only course and enrolment context; no grades, submissions or writeback. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Networks
Section titled “Networks”Aruba Central
Section titled “Aruba Central”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a network device | Limited availability | No simulation | Read-only monitored devices in one New Aruba Central site and workspace. No Classic Central, configuration, clients or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network equipment | Limited availability | No simulation | Read-only monitored devices in one New Aruba Central site and workspace. No Classic Central, configuration, clients or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network sites | Limited availability | No simulation | Read-only monitored devices in one New Aruba Central site and workspace. No Classic Central, configuration, clients or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a network device | Limited availability | No simulation | Read-only sites and network device status; no device control, configuration backup or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network equipment | Limited availability | No simulation | Read-only sites and network device status; no device control, configuration backup or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network sites | Limited availability | No simulation | Read-only sites and network device status; no device control, configuration backup or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Check Point Management
Section titled “Check Point Management”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a network device | Limited availability | No simulation | Read-only explicitly selected Check Point Security Management gateways in one verified domain through the site agent using v1.9. Inventory is not live connectivity, threat alerts or policy remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network equipment | Limited availability | No simulation | Read-only explicitly selected Check Point Security Management gateways in one verified domain through the site agent using v1.9. Inventory is not live connectivity, threat alerts or policy remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network sites | Limited availability | No simulation | Read-only explicitly selected Check Point Security Management gateways in one verified domain through the site agent using v1.9. Inventory is not live connectivity, threat alerts or policy remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Cisco Catalyst Center
Section titled “Cisco Catalyst Center”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a network device | Limited availability | No simulation | Read-only explicitly selected Catalyst Center device inventory through the site agent. No client tracking, configuration or network remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network equipment | Limited availability | No simulation | Read-only explicitly selected Catalyst Center device inventory through the site agent. No client tracking, configuration or network remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network sites | Limited availability | No simulation | Read-only explicitly selected Catalyst Center device inventory through the site agent. No client tracking, configuration or network remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Cisco Meraki
Section titled “Cisco Meraki”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a network device | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read a redacted configuration snapshot | Live handler | Fixtures available | Read only, with the key the connector already holds. Secrets are redacted before storage; nothing is pushed back or restored. |
| Read internet uplinks | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read network client connections | Live handler | Fixtures available | Client tracking must be explicitly enabled for this school; network permissions and campus mapping still apply. |
| Read network equipment | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read network events | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read network sites | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read subnets and VLANs for the IPAM | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Crestron XiO Cloud AV monitoring
Section titled “Crestron XiO Cloud AV monitoring”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read AV equipment and room health | Live handler | No simulation | Enable network monitoring and configure the connector in the existing integration settings. XiO Cloud API access, account ID and subscription key; subscription requirements depend on enabled vendor API features. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Account inventory and connectivity only; component health and automatic room discovery are not available. V1 reads are cached for five minutes without changing observation timestamps. |
| Read network equipment | Live handler | No simulation | Enable network monitoring and configure the connector in the existing integration settings. XiO Cloud API access, account ID and subscription key; subscription requirements depend on enabled vendor API features. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Account inventory and connectivity only; component health and automatic room discovery are not available. V1 reads are cached for five minutes without changing observation timestamps. |
| Read network sites | Live handler | No simulation | Enable network monitoring and configure the connector in the existing integration settings. XiO Cloud API access, account ID and subscription key; subscription requirements depend on enabled vendor API features. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Account inventory and connectivity only; component health and automatic room discovery are not available. V1 reads are cached for five minutes without changing observation timestamps. |
Domotz
Section titled “Domotz”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a network device | Limited availability | No simulation | Read-only sites and network device status; no device control, configuration backup or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network equipment | Limited availability | No simulation | Read-only sites and network device status; no device control, configuration backup or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network sites | Limited availability | No simulation | Read-only sites and network device status; no device control, configuration backup or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
FortiGate
Section titled “FortiGate”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a network device | Limited availability | No simulation | Read-only status of one serial-pinned firewall and VDOM through the site connector agent. No policies, sessions, configuration or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network equipment | Limited availability | No simulation | Read-only status of one serial-pinned firewall and VDOM through the site connector agent. No policies, sessions, configuration or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network sites | Limited availability | No simulation | Read-only status of one serial-pinned firewall and VDOM through the site connector agent. No policies, sessions, configuration or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
LogicMonitor
Section titled “LogicMonitor”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a network device | Limited availability | No simulation | Read-only monitoring of immediate devices in one native group. No nested-group expansion, alert workflows or configuration. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network equipment | Limited availability | No simulation | Read-only monitoring of immediate devices in one native group. No nested-group expansion, alert workflows or configuration. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network sites | Limited availability | No simulation | Read-only monitoring of immediate devices in one native group. No nested-group expansion, alert workflows or configuration. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Network diagnostics
Section titled “Network diagnostics”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Ping, port, DNS and route checks from the campus agent | Live handler | No simulation | A connector agent on the campus and the network.diagnose permission. Off for each campus until an administrator turns it on. Targets are network devices and devices the technician can already see, never a typed address. The agent checks only addresses inside diagnostics.allow in its own config. Nothing is written to the network. |
Network discovery
Section titled “Network discovery”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- A connector agent on the school network is required, on hosted and self-hosted deployments alike.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Sweep part of an approved range for network infrastructure from the campus agent | Live handler | No simulation | A connector agent on the campus, a range approved with step-up by someone holding network.discovery.manage, and the same range listed in discovery.allow in the agent config. Off for each campus until an administrator turns it on. Private IPv4 only, no range wider than /20 and at most 16,384 addresses per campus. Reads named SNMP identity objects with the school’s own credential profiles and makes TCP connects to five fixed ports. Never writes to a device, never guesses a community string. |
Network hardware (SNMP)
Section titled “Network hardware (SNMP)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a network device | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read network equipment | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read network sites | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read one switch port: status, speed and errors | Live handler | Fixtures available | Read only: one interface on a switch this connector is configured to poll. |
| Read subnets and VLANs for the IPAM | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Paessler PRTG
Section titled “Paessler PRTG”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a network device | Limited availability | No simulation | Read-only probes and device monitoring through the site connector agent; no configuration, sensor changes or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network equipment | Limited availability | No simulation | Read-only probes and device monitoring through the site connector agent; no configuration, sensor changes or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network sites | Limited availability | No simulation | Read-only probes and device monitoring through the site connector agent; no configuration, sensor changes or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Projectors and displays (PJLink)
Section titled “Projectors and displays (PJLink)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read AV equipment and room health | Live handler | No simulation | Enable network monitoring and configure the connector in the existing integration settings. A site connector agent or an explicitly authorized local deployment with access to the AV management network. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Up to 64 explicitly configured endpoints with shared protocol credentials and port. Each endpoint can be mapped to a campus; one site agent binding per connector. PJLink Class 1 queries only: power state, lamp hours, input, identity and reported hardware errors. Standby is not an outage. |
| Read network equipment | Live handler | No simulation | Enable network monitoring and configure the connector in the existing integration settings. A site connector agent or an explicitly authorized local deployment with access to the AV management network. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Up to 64 explicitly configured endpoints with shared protocol credentials and port. Each endpoint can be mapped to a campus; one site agent binding per connector. PJLink Class 1 queries only: power state, lamp hours, input, identity and reported hardware errors. Standby is not an outage. |
| Read network sites | Live handler | No simulation | Enable network monitoring and configure the connector in the existing integration settings. A site connector agent or an explicitly authorized local deployment with access to the AV management network. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Up to 64 explicitly configured endpoints with shared protocol credentials and port. Each endpoint can be mapped to a campus; one site agent binding per connector. PJLink Class 1 queries only: power state, lamp hours, input, identity and reported hardware errors. Standby is not an outage. |
Q-SYS AV monitoring
Section titled “Q-SYS AV monitoring”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read AV equipment and room health | Live handler | No simulation | Enable network monitoring and configure the connector in the existing integration settings. A site connector agent or an explicitly authorized local deployment with access to the AV management network. Enable QRC on TCP 1710 and configure a QRC user where authentication is enabled. Expose named standard status controls in Q-SYS Designer for room-level health. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Up to 64 explicitly configured endpoints with shared protocol credentials and port. Each endpoint can be mapped to a campus; one site agent binding per connector. Core StatusGet and named Control.Get only. Additional Cores report Core health; named room controls are read from the primary Core. No gain, mute, power or other control commands. |
| Read network equipment | Live handler | No simulation | Enable network monitoring and configure the connector in the existing integration settings. A site connector agent or an explicitly authorized local deployment with access to the AV management network. Enable QRC on TCP 1710 and configure a QRC user where authentication is enabled. Expose named standard status controls in Q-SYS Designer for room-level health. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Up to 64 explicitly configured endpoints with shared protocol credentials and port. Each endpoint can be mapped to a campus; one site agent binding per connector. Core StatusGet and named Control.Get only. Additional Cores report Core health; named room controls are read from the primary Core. No gain, mute, power or other control commands. |
| Read network sites | Live handler | No simulation | Enable network monitoring and configure the connector in the existing integration settings. A site connector agent or an explicitly authorized local deployment with access to the AV management network. Enable QRC on TCP 1710 and configure a QRC user where authentication is enabled. Expose named standard status controls in Q-SYS Designer for room-level health. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Up to 64 explicitly configured endpoints with shared protocol credentials and port. Each endpoint can be mapped to a campus; one site agent binding per connector. Core StatusGet and named Control.Get only. Additional Cores report Core health; named room controls are read from the primary Core. No gain, mute, power or other control commands. |
UniFi (local console)
Section titled “UniFi (local console)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a network device | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read a redacted configuration snapshot | Live handler | Fixtures available | Read only, with the key the connector already holds. Secrets are redacted before storage; nothing is pushed back or restored. |
| Read network client connections | Live handler | Fixtures available | Client tracking must be explicitly enabled for this school; network permissions and campus mapping still apply. |
| Read network equipment | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read network sites | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read subnets and VLANs for the IPAM | Live handler | Fixtures available | Provider configuration and school permissions apply. |
UniFi (Site Manager cloud)
Section titled “UniFi (Site Manager cloud)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read network equipment | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read network sites | Live handler | Fixtures available | Provider configuration and school permissions apply. |
WhatsUp Gold
Section titled “WhatsUp Gold”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a network device | Limited availability | No simulation | Read-only devices and monitoring status in one selected non-root group through the site agent. Public v1 contract requires installed-version acceptance; no configuration changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network equipment | Limited availability | No simulation | Read-only devices and monitoring status in one selected non-root group through the site agent. Public v1 contract requires installed-version acceptance; no configuration changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network sites | Limited availability | No simulation | Read-only devices and monitoring status in one selected non-root group through the site agent. Public v1 contract requires installed-version acceptance; no configuration changes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Zabbix
Section titled “Zabbix”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a network device | Limited availability | No simulation | Read-only sites and host monitoring through the site connector agent; no triggers, configuration changes or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network equipment | Limited availability | No simulation | Read-only sites and host monitoring through the site connector agent; no triggers, configuration changes or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read network sites | Limited availability | No simulation | Read-only sites and host monitoring through the site connector agent; no triggers, configuration changes or remediation. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Zoom Rooms AV monitoring
Section titled “Zoom Rooms AV monitoring”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.network.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read AV equipment and room health | Live handler | No simulation | Enable network monitoring and configure the connector in the existing integration settings. Active Server-to-Server OAuth app with zoom_rooms:read:list_rooms:admin (or room:read:admin), and Pro-or-higher Zoom plan with Zoom Rooms licensing. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Room availability and offline status only. Activation codes, participant information and meeting content are not retained; no room controls are sent. |
| Read network equipment | Live handler | No simulation | Enable network monitoring and configure the connector in the existing integration settings. Active Server-to-Server OAuth app with zoom_rooms:read:list_rooms:admin (or room:read:admin), and Pro-or-higher Zoom plan with Zoom Rooms licensing. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Room availability and offline status only. Activation codes, participant information and meeting content are not retained; no room controls are sent. |
| Read network sites | Live handler | No simulation | Enable network monitoring and configure the connector in the existing integration settings. Active Server-to-Server OAuth app with zoom_rooms:read:list_rooms:admin (or room:read:admin), and Pro-or-higher Zoom plan with Zoom Rooms licensing. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Room availability and offline status only. Activation codes, participant information and meeting content are not retained; no room controls are sent. |
Printing
Section titled “Printing”PaperCut MF / NG
Section titled “PaperCut MF / NG”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.printers.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Adjust a print balance | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Look up a print account | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read printer status | Limited availability | Fixtures available | Site agent access to the installed PaperCut XML-RPC API, authorized token and printer-property reads; provider pilot pending. Complete bounded list of up to 1,000 print queues. Queue enabled/disabled state and PaperCut accounting totals do not establish physical printer health, offline status or queued-job count. |
| Update a print-release card | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Printers (SNMP)
Section titled “Printers (SNMP)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.printers.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read printer status | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Update a print-release card | Demo only | Fixtures available | SNMP reads printer status; its print-card handler only acknowledges demo data. Use an implemented print-management connector for real card changes. |
Remote support
Section titled “Remote support”AnyDesk device status
Section titled “AnyDesk device status”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read remote-support device status | Limited availability | No simulation | Read-only status of explicitly mapped devices in the licensed client list. No remote session launch, recording or device control. Source and synthetic fixture validation only; live provider acceptance remains pending. |
BeyondTrust Remote Support connected status
Section titled “BeyondTrust Remote Support connected status”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read remote-support device status | Limited availability | No simulation | Read-only currently connected client lookup using explicit serial-to-hostname mappings through the site agent. Ephemeral clients are not stable fleet identities; no remote session launch. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Splashtop Enterprise computer status
Section titled “Splashtop Enterprise computer status”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read remote-support device status | Limited availability | No simulation | Read-only exact serial-to-computer mappings in one verified Splashtop team/region. No remote session launch or generic URL shortcut. Source and synthetic fixture validation only; live provider acceptance remains pending. |
TeamViewer device status
Section titled “TeamViewer device status”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read remote-support device status | Live handler | No simulation | TeamViewer commercial plan with API access and a user script token granting Computers & Contacts read permission (ContactList.Read). Explicit serial-to-remotecontrol_id mappings and remote target names are required for online badges. Read-only device status. Does not infer serials from aliases, create sessions, control devices or change existing launch links. Unmatched, ambiguous or unrecognised states remain unknown. Live account validation is still required. |
Repair suppliers
Section titled “Repair suppliers”CompNow
Section titled “CompNow”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add a vendor repair note | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Attach a vendor repair file | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Lodge a vendor repair | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read a vendor repair status | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Edunet
Section titled “Edunet”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add a vendor repair note | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Attach a vendor repair file | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Lodge a vendor repair | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read a vendor repair status | Live handler | Fixtures available | Provider configuration and school permissions apply. |
School information
Section titled “School information”Aeries
Section titled “Aeries”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read term dates | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Read-only roster for the configured school; no academic, wellbeing or safeguarding records. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read the school roster | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Read-only roster for the configured school; no academic, wellbeing or safeguarding records. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Compass Education
Section titled “Compass Education”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Find a staff member | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Find a student | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read a tutor group | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read the school roster | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Edumate
Section titled “Edumate”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read the school roster | Limited availability | No simulation | Read-only current student and staff identity from the configured school API feed using a supplied OAuth bearer token. Whole-school feed, no inferred campus filter or independent tenant-identity claim; no family, academic, wellbeing records, managed consent or writeback. Source and synthetic fixture validation only; live provider acceptance remains pending. |
OneRoster
Section titled “OneRoster”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read classes, rooms and enrolments | Limited availability | No simulation | OneRoster 1.1 or 1.2 over HTTPS, an OAuth client-credentials token endpoint and roster-core.readonly access. Fixture-tested read-only student and staff roster adapter; a school-provider pilot is still required. Classes, their location and periods, and enrolments feed the timetable; OneRoster has no bell times or day cycle, so those are imported. No grades, demographic records, family contacts, account provisioning or writeback. Invalid or incomplete pulls fail without applying the roster or timetable. |
| Read term dates | Limited availability | No simulation | OneRoster 1.1 or 1.2 over HTTPS, an OAuth client-credentials token endpoint and roster-core.readonly access. Fixture-tested read-only student and staff roster adapter; a school-provider pilot is still required. Classes, their location and periods, and enrolments feed the timetable; OneRoster has no bell times or day cycle, so those are imported. No grades, demographic records, family contacts, account provisioning or writeback. Invalid or incomplete pulls fail without applying the roster or timetable. |
| Read the school roster | Limited availability | No simulation | OneRoster 1.1 or 1.2 over HTTPS, an OAuth client-credentials token endpoint and roster-core.readonly access. Fixture-tested read-only student and staff roster adapter; a school-provider pilot is still required. Classes, their location and periods, and enrolments feed the timetable; OneRoster has no bell times or day cycle, so those are imported. No grades, demographic records, family contacts, account provisioning or writeback. Invalid or incomplete pulls fail without applying the roster or timetable. |
Schoolbox
Section titled “Schoolbox”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read the school roster | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Read-only school roster; no academic, wellbeing or safeguarding records. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Sentral
Section titled “Sentral”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Find a staff member | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Find a student | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read a person’s photo | Limited availability | No simulation | The same Sentral API key, with permission for the staff photo route (unconfirmed until a live key is tested), and staff photos on in Settings, Photos. Staff photos only; student photos and Sentral consent flags are not read. Run only by the nightly photo pass, never in a flow. Fixture validation only. Demo mode returns no photo. |
| Read a tutor group | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read term dates | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read the school roster | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Synergetic
Section titled “Synergetic”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Find a student | Limited availability | No simulation | School-managed REST bridge using custom /api/* routes and optional fictional demo data. This is not native SynAPI WCF or CoreAPI support. Native method/version, roster schema and complete-source semantics require the school-provided contract. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read a tutor group | Limited availability | No simulation | School-managed REST bridge using custom /api/* routes and optional fictional demo data. This is not native SynAPI WCF or CoreAPI support. Native method/version, roster schema and complete-source semantics require the school-provided contract. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read term dates | Limited availability | No simulation | School-managed REST bridge using custom /api/* routes and optional fictional demo data. This is not native SynAPI WCF or CoreAPI support. Native method/version, roster schema and complete-source semantics require the school-provided contract. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Read the school roster | Limited availability | No simulation | School-managed REST bridge using custom /api/* routes and optional fictional demo data. This is not native SynAPI WCF or CoreAPI support. Native method/version, roster schema and complete-source semantics require the school-provided contract. Source and synthetic fixture validation only; live provider acceptance remains pending. |
- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read the school roster | Limited availability | No simulation | A publicly reachable HTTPS provider endpoint. This adapter does not currently route private instances through a site agent. Read-only roster using the school-authorized API application; no academic records or writeback. Source and synthetic fixture validation only; live provider acceptance remains pending. |
- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Find a staff member | Limited availability | Fixtures available | A Wonde school token for one school, the school’s Wonde id, and the school’s approval of Plugboard in Wonde. A token that reads more than one school is refused. Fixture-tested from Wonde’s public API reference only; no school or Wonde sandbox has run it. Read only: students on roll and current staff, with name, school email, username, card, year, roll class and campus, and staff dates and role. Never reads medical, wellbeing, behaviour, family, date of birth, gender or address records. Lookups take an id only. A pull that does not match Wonde’s own totals fails without applying anything; revoked access deactivates nobody. |
| Find a student | Limited availability | Fixtures available | A Wonde school token for one school, the school’s Wonde id, and the school’s approval of Plugboard in Wonde. A token that reads more than one school is refused. Fixture-tested from Wonde’s public API reference only; no school or Wonde sandbox has run it. Read only: students on roll and current staff, with name, school email, username, card, year, roll class and campus, and staff dates and role. Never reads medical, wellbeing, behaviour, family, date of birth, gender or address records. Lookups take an id only. A pull that does not match Wonde’s own totals fails without applying anything; revoked access deactivates nobody. |
| Read a person’s photo | Limited availability | No simulation | A Wonde school token for one school, the school’s Wonde id, and the school’s approval of Plugboard in Wonde. A token that reads more than one school is refused. The photo permission approved in Wonde, and staff photos on in Settings, Photos. Fixture-tested from Wonde’s public API reference only; no school or Wonde sandbox has run it. Read only: students on roll and current staff, with name, school email, username, card, year, roll class and campus, and staff dates and role. Never reads medical, wellbeing, behaviour, family, date of birth, gender or address records. Lookups take an id only. A pull that does not match Wonde’s own totals fails without applying anything; revoked access deactivates nobody. Staff photos only; student photos and consent flags are not read, and Wonde’s bulk photo list is never called. Run only by the photo pass, weekly, never in a flow. Fixture validation only. Demo mode returns no photo. |
| Read a tutor group | Limited availability | Fixtures available | A Wonde school token for one school, the school’s Wonde id, and the school’s approval of Plugboard in Wonde. A token that reads more than one school is refused. Fixture-tested from Wonde’s public API reference only; no school or Wonde sandbox has run it. Read only: students on roll and current staff, with name, school email, username, card, year, roll class and campus, and staff dates and role. Never reads medical, wellbeing, behaviour, family, date of birth, gender or address records. Lookups take an id only. A pull that does not match Wonde’s own totals fails without applying anything; revoked access deactivates nobody. |
| Read the school roster | Limited availability | Fixtures available | A Wonde school token for one school, the school’s Wonde id, and the school’s approval of Plugboard in Wonde. A token that reads more than one school is refused. Fixture-tested from Wonde’s public API reference only; no school or Wonde sandbox has run it. Read only: students on roll and current staff, with name, school email, username, card, year, roll class and campus, and staff dates and role. Never reads medical, wellbeing, behaviour, family, date of birth, gender or address records. Lookups take an id only. A pull that does not match Wonde’s own totals fails without applying anything; revoked access deactivates nobody. |
Spreadsheets
Section titled “Spreadsheets”Google Sheets
Section titled “Google Sheets”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read a spreadsheet | Live handler | Fixtures available | Google Workspace > Google Sheets: needs Share the sheet with the service account. |
| Write a spreadsheet | Live handler | Fixtures available | Google Workspace > Google Sheets: needs Share the sheet with the service account. |
Staff credentials
Section titled “Staff credentials”Certelva
Section titled “Certelva”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read permitted staff credential records | Limited availability | No simulation | Read-only minimal credential records for one verified Certelva Business organisation. Public issuer records do not authenticate ownership, competence or privileged-action authority; no private study data or writes. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Storage
Section titled “Storage”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A connector agent on the school network is required, on hosted and self-hosted deployments alike.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read connector storage | Limited availability | No simulation | Explicitly select a current site connector agent; platform execution is refused even on a deployment with private network access. Dedicated server-enforced chroot, preapproved SSH host key and read account. Uploads additionally require allowWrites and confirmed atomic no-overwrite rename; no upload UI is provided. Bounded UTF-8 file reads through the site agent from a server-enforced chroot with a pinned SSH host key. Optional explicitly enabled new-file uploads; no overwrite, deletion, binary attachment backend or automatic roster import. Source text is displayed without executing markup. Source and synthetic fixture validation only; live provider acceptance remains pending. |
| Upload to connector storage | Limited availability | No simulation | Explicitly select a current site connector agent; platform execution is refused even on a deployment with private network access. Dedicated server-enforced chroot, preapproved SSH host key and read account. Uploads additionally require allowWrites and confirmed atomic no-overwrite rename; no upload UI is provided. Bounded UTF-8 file reads through the site agent from a server-enforced chroot with a pinned SSH host key. Optional explicitly enabled new-file uploads; no overwrite, deletion, binary attachment backend or automatic roster import. Source text is displayed without executing markup. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Text messages
Section titled “Text messages”MessageMedia
Section titled “MessageMedia”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Send a text message | Limited availability | No simulation | Send one outbound SMS. Provider acceptance is not delivery confirmation; no inbound messages or delivery-receipt ingestion. Source and synthetic fixture validation only; live provider acceptance remains pending. |
SMSGlobal
Section titled “SMSGlobal”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Send a text message | Limited availability | No simulation | Send one outbound SMS. Provider acceptance is not delivery confirmation; no inbound messages or delivery-receipt ingestion. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Twilio SMS
Section titled “Twilio SMS”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Send a text message | Live handler | No simulation | Provider configuration and school permissions apply. |
Voice and call records
Section titled “Voice and call records”Cisco Webex Calling CDR history
Section titled “Cisco Webex Calling CDR history”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read completed call records | Limited availability | No simulation | Read-only regional Webex Calling detailed records for the provider-reporting window. Native reporting-time bounds and retention apply; no live calls, recordings or control. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Microsoft Teams Phone call history
Section titled “Microsoft Teams Phone call history”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read completed call records | Limited availability | No simulation | Microsoft 365 > Microsoft Teams Phone call history: needs CallRecords.Read.All. callSource explicitly selects PSTN or DIRECT_ROUTING (existing configurations default to PSTN). Tenant-wide historical logs: Plugboard campus coverage controls visibility but is not a native site filter. Direct Routing uses call-start time and native outcome/SIP code, with no recording or live-call retrieval. Read-only completed PSTN or explicitly selected Direct Routing call records for one verified tenant, using a call-start window. This is not all Teams calls; no recordings, transcription or call control. Source and synthetic fixture validation only; live provider acceptance remains pending. |
RingCentral call history
Section titled “RingCentral call history”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read completed call records | Limited availability | No simulation | Read-only extension call history in one configured RingCentral account. No live calls, recording retrieval, transcription or call control. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Zoom Phone call history
Section titled “Zoom Phone call history”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- Connector category entitlement:
module.integrations.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Read completed call records | Limited availability | No simulation | Read-only completed Zoom Phone history using current call_history API. No live calls, recordings, transcription or call control. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Warranty
Section titled “Warranty”Apple Business Manager
Section titled “Apple Business Manager”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Look up warranty cover | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Apple GSX
Section titled “Apple GSX”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Look up warranty cover | Limited availability | No simulation | Institution-supplied compatibility gateway using custom bearer-token /api/ping and /api/device/warranty routes. Native Apple GSX authentication, version-specific warranty contract and entitlement are not verified by this adapter. Source and synthetic fixture validation only; live provider acceptance remains pending. |
Apple School Manager
Section titled “Apple School Manager”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Look up warranty cover | Live handler | Fixtures available | Provider configuration and school permissions apply. |
CompNow warranty & insurance
Section titled “CompNow warranty & insurance”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Look up warranty cover | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Dell warranty
Section titled “Dell warranty”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Look up warranty cover | Live handler | Fixtures available | Provider configuration and school permissions apply. |
HP warranty
Section titled “HP warranty”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Look up warranty cover | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Lenovo warranty
Section titled “Lenovo warranty”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Look up warranty cover | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Contracts with no registered tenant provider
Section titled “Contracts with no registered tenant provider”The following contracts do not have an executing tenant connector. Recording an approval, opening a vendor console or using a separate built-in feature does not add connector execution.
| Requested operation | Availability | Meaning |
|---|---|---|
| Lock a device | Unsupported | An approval request can be recorded, but no registered connector executes device locking. Approval is not a successful lock. |
| Provision an identity account | Unsupported | No tenant connector is registered to execute this contract. Built-in product features and vendor-console links may exist independently; this is not a promise of connector support. |
| Send a learning notification | Unsupported | No tenant connector is registered to execute this contract. Built-in product features and vendor-console links may exist independently; this is not a promise of connector support. |
| Send a provider-templated email | Unsupported | No tenant connector is registered to execute this contract. Built-in product features and vendor-console links may exist independently; this is not a promise of connector support. |
| Look up a directory record | Unsupported | No tenant connector is registered to execute this contract. Built-in product features and vendor-console links may exist independently; this is not a promise of connector support. |
| Read a person’s licences | Unsupported | No tenant connector is registered to execute this contract. Built-in product features and vendor-console links may exist independently; this is not a promise of connector support. |
| Create a connector checkout | Unsupported | No tenant connector is registered to execute this contract. Built-in product features and vendor-console links may exist independently; this is not a promise of connector support. |
| Read a connector subscription | Unsupported | No tenant connector is registered to execute this contract. Built-in product features and vendor-console links may exist independently; this is not a promise of connector support. |
| Open a connector billing portal | Unsupported | No tenant connector is registered to execute this contract. Built-in product features and vendor-console links may exist independently; this is not a promise of connector support. |
| Search external documentation | Unsupported | No tenant connector is registered to execute this contract. Built-in product features and vendor-console links may exist independently; this is not a promise of connector support. |
| Write back an external document | Unsupported | No tenant connector is registered to execute this contract. Built-in product features and vendor-console links may exist independently; this is not a promise of connector support. |
| List remote-support devices | Unsupported | No tenant connector is registered to execute this contract. Built-in product features and vendor-console links may exist independently; this is not a promise of connector support. |
| Create a remote-support session | Unsupported | No tenant connector is registered to execute this contract. Built-in product features and vendor-console links may exist independently; this is not a promise of connector support. |
| Explain a content-filter decision | Unsupported | No tenant connector is registered to execute this contract. Built-in product features and vendor-console links may exist independently; this is not a promise of connector support. |
Reference provenance
Section titled “Reference provenance”Reviewed source metadata: 2026-09-30. Content SHA-256: 7bab28e5f3049319dbb3885e87bdaf36460f372ced32afcda2a0a902d799bd51.
The product Help page and this guide use the same generated reference. Registry coverage and generated-file checks run in platform CI. Public documentation validates its vendored snapshot; a newer platform reference must be explicitly synced and reviewed before publication. No customer settings, credentials or connection-test results are included.