Employees act through your real business tools — email, CRM, accounting, shops, social. An owner connects a tool once; you decide which employees may use it.
Connect from the Integrations page — usually a sign-in or a pasted API key. Search by name, or narrow by Category (Email & Calendar, Files & Docs, Documents & Signing, CRM & Sales, Support & Helpdesk, Team comms, Project & Dev, Finance & Payments, Online shop, Marketing, Analytics, HR & Time, Automation) and Show (available, connected, on the roadmap). Connecting and disconnecting are owner-only.
Credentials are stored encrypted and never shown back in full. The tools you named at signup appear as favourites. If a connection stops working, a banner says so and Reconnect fixes it.

Employees use the connectors you gave them — set per employee in its editor, or let Vori grant access on your go-ahead. One exception: when Outlook, Gmail or a Hostpoint mailbox is connected, every employee can read the company inbox unless you exclude it (Company inbox in its editor); sending still needs the connector. Marketing employees also see ads performance once an ads platform is connected.
Custom connectors — a webhook or a REST API, optionally imported from an OpenAPI file — let you wire in any tool with an HTTP API.
On the Security page, under per-connector permissions, you decide per tool — separately for reading and writing — Default, Allow, Ask first or Block. «Read Gmail but never send» is one setting. On a connected card, What employees may do offers the quick version for writes: standard, ask first, block. Anything you leave alone keeps the default: reads run, writes follow the approval rules.
Swiss needs are first-class:
Something wrong with a connector? Report a problem on its card (even an unavailable one), in its connection dialog or at the top of the page. The report names the connector, reaches support with a reference number, and keeps your text if sending fails.
Some tools are in the catalog but can't be connected yet — the provider needs partner onboarding, has no public API, or requires its own sign-in integration. They are hidden unless you choose Show → On the roadmap. A tool that connects by sign-in becomes connectable as soon as that sign-in is set up — its card then offers Sign in with….