Connectorsowns The plumbing
Moving data, routing it and reshaping it, plus the credentials, the consent and a record of what was fetched. One place for all of it, instead of an adapter inside every module.
Connectors - integration plane
Your providers,
integrated once.
Every system in the family makes the same promise. It calls no provider directly. Connectors is what makes that true. One place holds the credentials and the consent, so no mailbox token ever lands in your procurement or HR database.
The division of labour
Plumbing here. Your records there.
The usual mess is an adapter per module. Five products each holding their own Microsoft credentials, each with their own idea of consent, and five places to look when something breaks. Keeping the plumbing separate fixes that, without making any module depend on a provider.
Each system of recordowns The business state
Procurement, HR, customer and the rest keep owning their own records. No provider password ever lands inside a business system.
Connector packs
Reviewed adapters, not a plugin store.
A pack gets added once it is reviewed, in version control, and backed by a real contract with the source system. That is why this list is short, and why each entry says exactly what it reaches.
Microsoft Graph foundation
The base every Microsoft pack builds on. Consent, permissions and tokens handled in one place.
Outlook Mail
An email becomes activity on the right customer or candidate, instead of sitting in someone's inbox.
Outlook Calendar
Reads and writes against permissions you approved. This is where interview slots and meetings come from.
SharePoint
Reach the documents a process depends on, without copying them into another database.
Microsoft Teams
Optional workforce and collaboration signals. Optional is the point.
Google Workspace
in progressSign-in, permissions and the groundwork are specified. The packs themselves are still being built.
How it is governed
This is a security surface. We treat it like one.
Anything holding the keys to your mailbox, calendar and documents is worth more to an attacker than most of what it feeds. So each line below is something we refuse to do.
Secrets live in a secret manager
We store a pointer to each credential, never the credential. Passwords and tokens are held in a dedicated secret manager, not in our database.
Every call is an ICE principal
Every call needs a real token for the right tenant with the right permission. Reading, changing and auditing are three separate permissions.
Health is the only public endpoint
Nothing else answers without a token. There is no shortcut endpoint that skips the check.
The route inventory starts empty
No sample connectors and no demo data on startup. An adapter gets added once it is reviewed, in version control, and backed by a real contract with the source system.
Failures are inspectable and replayable
You can see every run, open the ones that failed, and replay them once the cause is fixed. A broken sync is something you look at, not a gap in a log.
Who relies on it
The promise every other page makes.
Read the workforce, customer or banking pages and you will find the same line in different words. This module calls no provider directly. That only means something because something else does.
Workforce
Rotas and clock-ins arrive here first and get tidied up. HR keeps its own keys and needs no Microsoft subscription, because the optional Teams pack sits on this side of the line.
Customer
Mailbox, calendar, phone and messaging are integrated once here, then show up as activity on the customer. Sales, marketing and service share one history instead of three separate integrations.
Banking Ops
Core banking, the networks, reconciliation and CRM are all read through here. That is exactly why BankOps can own the dispute case without owning any of the money.
When a sync breaks
A failure you can actually look at.
Integrations fail for ordinary reasons. Someone revoked consent, you hit a rate limit, the provider went down, the source system rejected a message. What matters is whether anyone can tell afterwards.
Run history shows what was tried. Failed messages are kept so you can open one and see why. And once the cause is fixed, someone with the right access can replay it.
Separately scoped
- Registry and runtime reads - see what connectors exist and what they are doing.
- Lifecycle writes - create, bind or retire a connector instance.
- Audit reads - a separate permission again, because reading the evidence trail is its own privilege.
Three separate permissions, not one admin role. Running this and auditing it are different jobs.
Connectors walkthrough
Tell us what you need to reach.
Mailbox, calendar, documents, phone, or something line-of-business. We will show you where the credential lives, what the consent looks like, and what you get back.