XDocs for Teams
Team workspaces with roles, SAML SSO and an API for every agreement
Team workspaces with four roles, guests narrowed to particular rooms, SAML single sign-on and SCIM provisioning, and an API that covers the whole product.
- Member, manager, admin and owner roles
- Guests who can reach named rooms and nothing else
- SAML SSO and SCIM on the Business plan
- REST API, webhooks, CLI, Zapier and an MCP server
How it goes
1
Joining
Invitations are mailed, expire in a fortnight, and admit only the address they were sent to. With SCIM, your identity provider adds people and removes them the minute they leave.
2
Working
Everyone sees the same documents, templates and rooms for the team they are switched into. The assistant remembers the team's wording and its counterparties between conversations.
3
Integrating
Every event is a webhook and every action is an endpoint, under scoped keys with per-key rate limits.
One place for every agreement, with the right people in it
A company's agreements usually live in four places: a shared drive, a signing tool, somebody's inbox and a data-room product the deal team bought. XDocs holds them in one workspace with four roles — member, manager, admin and owner — so who may create, send, publish and administer is a setting rather than a habit. Guests can be admitted to particular rooms and nothing else. Templates, saved positions and the assistant's memory of how the company words things belong to the team, so a new hire starts from the house version rather than from a blank page or a colleague's old file.
SAML single sign-on and SCIM, so leaving means leaving
On the Business plan the workspace sits behind your identity provider. People sign in with the company account, and SCIM provisioning adds them when they join and removes them the minute they leave, which is the moment a shared drive and a signing tool usually forget about. Invitations expire in a fortnight and admit only the address they were sent to. Every action by every member is in an append-only audit trail with timestamp, actor and IP address, searchable by document, link and envelope, and exportable.
Every action is an endpoint, every event a webhook
The REST API covers the whole product rather than a subset of it: create and send documents, publish and gate links, run data rooms, read back who read what. Keys are scoped and rate-limited per key. Webhooks fire on every event with signed payloads. There is a CLI, a Zapier app, incoming webhooks for other software to post into, and an MCP server that exposes the same tools to an AI agent on the same keys — the whole reference is also published as plain text for models to read. The ops team can wire XDocs into the systems the company already runs without waiting for an integration to be built.
An assistant the whole team can hold to account
The assistant reads the team's real documents, rooms and envelopes, and remembers the team's counterparties and wording between conversations. What it may do without asking is a policy the admin sets, not a default we chose: anything that leaves the workspace waits for approval, every action is logged with an undo, and a declined action is recorded too. Approvals can be mirrored into Slack so the person who should click is the person who does. Pricing is per workspace — Pro $29, Business $99 a month — so adding the twelfth person costs nothing, and a self-hosted deployment in Docker against ordinary Postgres runs unmetered.
The parts you will use most
One place for every important document.
Create, sign, share and understand your documents with XDocs.