One approved connection can cover the suite services named for an AI employee's job. Each service is scoped separately.
An administrator grants the connection in the system itself. The scope requested is shown before you approve it, and it is the narrowest one that does the job: a named mailbox rather than the tenant, a named site rather than every site.
Read and write are requested separately, and an AI employee only receives whichever its job description names. Revoking the grant in your own system takes it away here.
Connections are made over TLS. Documents are read to answer a question or work a piece of work, and what is retained is the memory and the record described elsewhere on this site, not a second copy of your drive.
Customer data is not used to train models. What is sent to a model provider, and what is not, is named on the security page.
Security →The Microsoft and Google suites are supported directly. For other systems, we can assess an existing open-source MCP connector or the work needed to connect it safely.
One mailbox or one drive is enough to start a pilot.
