Do we need to send data before booking?
No. Describe the workflow first. We can agree on appropriate sample material before you share any records.
See how your team could find useful information across inboxes, compare details from documents and share the updates each audience needs.
Supplier email
Hi there, delivery is planned for 18 October. Internal price: £12,400. We’ll confirm once it’s on route.
Customer view
The internal price stays out of this output.
Try a task such as sorting a shared inbox, checking invoice attachments, tracking delivery changes or handing over an account. Follow the email or document to the useful list, table or shared view your team would use.
A short description is enough. Include:
Include the person who owns the workflow. An IT or security colleague can join if source permissions, sign-in or external sharing need review.
Choose the parts that matter for your workflow:
Choose the accounts and material for the first task, who owns it and what the recipients should see. The implementation guide helps you put the setup into use.
No. Describe the workflow first. We can agree on appropriate sample material before you share any records.
Yes. See who can read the connected information, what appears in shared views, which original files can be downloaded and the sign-in options enabled for your deployment.
Tell us which emails and documents you work with and what your team needs to do with them. That task can guide the session.
Yes. Tell us which assistant or application should receive the data so we can review supported connections, credentials and the information it can read.
Tell us about the task, where the information arrives and who needs the result.