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 a beta preview in the 0.12.0-rc.1 source. This reference does not confirm that your deployment has been upgraded; check its version and explicit add-on entitlements. Native release packaging currently 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. Unreleased describes work not yet claimed as a published release.
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 | Beta preview | Facilities add-on entitlement and activation, an enabled desk, assigned department membership and ticket permissions. Required module keys: module.tickets, module.facilities. |
| Administration desk | Beta preview | 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 | Beta preview | 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”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. |
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 | Beta preview | 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-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 | Beta preview | 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. |
Customer records
Section titled “Customer records”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 | Beta preview | 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 | Beta preview | 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 | Beta preview | 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”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 | 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 | Provider configuration and school permissions apply. |
| Find a person’s devices | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| Read a device fix result | Live handler | Fixtures available | 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 | 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 Chromebook fix command | Live handler | Fixtures available | 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 | Only the provider’s implemented command menu is supported. A generic command does not imply lock or erase support. |
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 | 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 | 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 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 | 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 | Only the provider’s implemented command menu is supported. 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. |
| 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. |
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 | The DeviceManagementManagedDevices.PrivilegedOperations.All application permission. Runs only as an approved device fix on a staff device. |
| Erase a device | Live handler | No simulation | 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 the school’s fix scripts | Live handler | No simulation | Read-only import for the fix catalogue: names and ids, never script bodies. Needs DeviceManagementScripts.Read.All. Uses a beta Graph endpoint. |
| Read a device fix result | Live handler | No simulation | 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 | Provider configuration and school permissions apply. |
| Read a local administrator password | Live handler | No simulation | 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. |
| Run one of the school’s remediation scripts | Live handler | No simulation | 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. |
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 provider’s implemented command menu is supported. A generic command does not imply lock or erase support. |
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. |
Console Email (dev)
Section titled “Console Email (dev)”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Send email | Demo only | Fixtures available | Writes email to development logs; no message is delivered to a real mailbox. |
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 |
|---|---|---|---|
| Send email | Live handler | No simulation | Provider configuration and school permissions apply. |
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 |
|---|---|---|---|
| Import inbox messages as tickets | Live handler | No simulation | 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 | 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”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 ticketing
Section titled “External ticketing”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 | 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. |
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.
- Connector category entitlement:
module.directory.
| What you can do | Live availability | Demo | Requirements and limits |
|---|---|---|---|
| Add a person to a group | Unsupported | No simulation | 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. |
| 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 | Unsupported | No simulation | 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. |
| 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 | Unsupported | No simulation | 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. |
| 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.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. |
| 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 | Unsupported | No simulation | 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. |
| Read a demonstration directory user | 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 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 | 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 identity account status | 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 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 | Unsupported | No simulation | 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. |
| 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 | Unsupported | No simulation | 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. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| 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 the demonstration directory | 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. |
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 | 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 | 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 | No simulation | 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 | 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 | 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 | 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. |
| Issue a temporary access pass | 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. |
| 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 | No simulation | 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 demonstration directory user | 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 | Live handler | 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. |
| Read a person’s manager | Live handler | 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. |
| 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 | 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. |
| Read identity account status | Live handler | 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. |
| Read multifactor registration | Live handler | 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. Google reports 2-Step Verification enrolment, not the list of registered methods. |
| Read organisation licence totals | Live handler | 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. 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 sign-in history | Live handler | 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. |
| Remove a person from a group | Live handler | No simulation | 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 | 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 | Unsupported | No simulation | 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. This provider returns an explicit unsupported result; a registered handler does not establish live support. |
| 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 | Live handler | 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. |
| Search the demonstration directory | 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. |
| 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. |
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 |
|---|---|---|---|
| Add a person to a group | Live handler | No simulation | 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 | Live handler | 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. |
| 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 | No simulation | 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 | 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 | 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 | 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. |
| Issue a temporary access pass | Live handler | 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. |
| Manage Exchange mailbox delegation | Live handler | No simulation | 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 | 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 demonstration directory user | 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 | Live handler | 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. |
| Read a person’s manager | Live handler | 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. |
| Read Conditional Access policies | Live handler | No simulation | 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 | 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 | 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 | 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 organisation licence totals | Live handler | 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. |
| 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 | 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. |
| Remove a person from a group | Live handler | No simulation | 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 | 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 | 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 | 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 | 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 the demonstration directory | 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. |
| 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. |
Networks
Section titled “Networks”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. |
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 subnets and VLANs for the IPAM | Live handler | Fixtures available | Provider configuration and school permissions apply. |
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. |
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 | Live handler | Fixtures available | Provider configuration and school permissions apply. |
| 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”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. |
School information
Section titled “School information”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. |
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 the school roster | Beta preview | 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. No grades, demographic records, family contacts, class rosters, account provisioning or writeback. Invalid or incomplete pulls fail without applying the roster. |
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 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. |
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 | 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 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. |
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 | Provider configuration and school permissions apply. |
| Write a spreadsheet | Live handler | Fixtures available | Provider configuration and school permissions apply. |
Text messages
Section titled “Text messages”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. |
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 | Live handler | No simulation | Provider configuration and school permissions apply. |
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. |
| Read learning courses | 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 learning enrolments | 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. |
| Upload to connector storage | 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 connector storage | 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. |
| Sync directory records | 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. |
| List documentation spaces | 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 external documents | 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 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. |
| 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-05. Content SHA-256: 6ba0684ead2d347117b7a7a0a9a2d06b18aa5c4b17e9148e8162d55157eef2e9.
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.