OpenTeam connector · alpha
Your team in OpenTeam.
Your access in Hub.
Import people once, review what will change, then keep the directory current.
This connects the people directory. Kebabstack roles, Finance and sign-in remain configured in Hub.
01 · Choose your source
Copy the backend canister ID
Get the backend ID from your company's OpenTeam deployment. In Hub, open Directory sync → OpenTeam as an owner. Enter a source name and that ID. The website address is not the backend ID.
The deployments must be able to reach each other. The reviewed API does not need an API key; if your provider restricts roster reads, its operator must allow your Hub backend.
02 · Review before importing
One person, one clear source
Employees are included by default. Import scope can include contractors and partners; AI agents stay excluded. Choose Save & preview to see additions and changes.
If an email already belongs to a Hub identity, the import stops. Exclude that OpenTeam member ID or reconcile the existing source first. Hub never transfers roles by guessing that two matching addresses are the same person.
Only Apply & enable sync changes people. If the directory changes during review, preview again.
03 · Keep it running
Five-minute updates, visible results
Hub checks the full directory every five minutes. A partial response or connection error keeps the last successful directory. Last-success time and errors appear on the source card. Large departure waves require review.
Pause stops imports; it does not revoke existing access. Changing import scope also pauses sync until reviewed. For urgent departures during a source outage, block the person directly in Hub.
Inactive source accounts enter the existing lifecycle flow. Another active source or an audited force-active override can retain access. This is not immediate revocation.
What this connection includes
Stable member IDs, name, email, title, department and manager IDs, activity, member kind and erasure signals. It reads the team-directory v2 API; the reference tested locally is 2.35.0.
It does not import OpenTeam roles or groups, connect OpenSaaS shared sign-in, or write back to OpenTeam. A compatible directory is not the same as full OpenSaaS suite certification.
Erasure clears the imported source profile. Hub history and records in connected apps retain their separate retention policies; this is not a suite-wide erasure receipt.