Managing integrations

For per-provider setup runbooks, see the Integrations section in the sidebar. This page is the operational reference for managing integrations once they’re connected.

Where to find it

Settings → Integrations. Shows:

• A 2-column directory grid of workspace providers (M365, Google Workspace, Lark / Feishu)
• Each card shows status: Not connected · Connected · Needs re-verification
• An “Other connectors” section below for per-user / coming-soon items

Click any card to open its setup or management modal.

Connect (super admin yourself)

If you’re also your tenant’s IT admin:

1. Click the provider card.
2. Step through the in-modal setup form (same form as the IT-handoff magic-link page).
3. Verify. The card flips to Connected.

Each provider has its own setup pattern — see the per-provider runbook:

• Microsoft 365
• Google Workspace
• Lark / Feishu

Connect (send IT a magic link)

If your IT admin will handle the actual integration setup:

1. Click the provider card.
2. Click Set up via [provider] admin.
3. Enter the IT admin’s email.
4. A one-time magic link is emailed to them — valid for 7 days.

The IT admin opens the link, completes provider-specific setup inline (no Wisteria account needed), and Wisteria emails you when it’s done.

While the link is outstanding, the card shows Awaiting setup — magic link sent.

Disconnect

Click a connected provider card → Disconnect.

What happens:

• The encrypted credentials Wisteria stored are deleted.
• The AI scanner stops querying that provider.
• “Wisteria noticed” cards that came from this provider stay visible (they’re already stored as suggestions) but no new ones are generated.
• Courses that were already generated from this provider’s content are untouched.

To revoke at the provider’s end as well, follow the per-provider runbook’s Disconnecting section.

Re-verify

If credentials are rotated, scopes change, or an integration starts returning errors, click the card → Re-verify.

Wisteria re-runs the original setup check (admin consent for M365, DWD test for Google, app credential validation for Lark) and updates the connection status.

If re-verification fails, the error message points at what needs fixing in the provider’s admin console.

Switching to a different tenant

If your organisation migrates from one tenant to another (e.g. M&A, rebrand, restructure):

1. Disconnect the old integration.
2. Connect the new tenant via the same flow.
3. (Optional) Move the AI Training Profile manually if anything was tenant-specific in the writeup.

Wisteria doesn’t move historical scans or “Wisteria noticed” cards between tenants. They stay associated with the original tenant’s data.

Content connectors

Content connectors (Notion, Zendesk) let the AI scanner read your knowledge base and surface training suggestions. These require super admin setup but no IT admin involvement.

• Notion — scan Notion pages shared with the integration
• Zendesk — scan Zendesk Help Center articles

HR connectors

HR connectors sync your HRIS headcount into Wisteria. When you trigger a sync, Wisteria upserts people from your HR system as learners (or other roles).

• Deel, Talenox, Workday

Per-user connectors

The “Other connectors” section is for lightweight per-user integrations:

• Google Drive (OAuth) — see Per-user Google Drive

These don’t require IT admin involvement and only see what the connecting user can see.

For integrations still on the roadmap, see Coming soon.

Audit log

Every connect, disconnect, and re-verification is recorded with the integration.* action prefix. Filter the audit log for the full integration history of your workspace.