Before you begin
The licences, accounts and permissions DocFlo needs, and who in your organisation provides each one.
DocFlo needs four things in place. Most organisations have the first two already; the last two take a few minutes.
| You need | Provided by | Why |
|---|---|---|
| A Microsoft 365 Copilot licence for each person | Your Microsoft 365 administrator | DocFlo runs inside Copilot |
| A DocFlo (⦃param⦄ ai/studio) workspace and user accounts | Your DocFlo workspace owner | Answers come from projects in that workspace |
| DocFlo allowed and assigned in Microsoft 365 | Your Microsoft 365 administrator | So DocFlo appears under Agents in Copilot |
| Copilot access turned on for the DocFlo workspace | A DocFlo workspace owner or admin | Lets members sign in to DocFlo from Copilot |
For SharePoint sync there is one more step: a tenant administrator approves read-only access to the sites DocFlo should read. See setting up for your organisation.
Roles
| Role | Can |
|---|---|
| Microsoft 365 administrator | Allow, assign, block or remove the DocFlo app for the organisation |
| DocFlo workspace owner / admin | Invite members, turn Copilot access on or off, manage projects |
| DocFlo member | Ask questions of the projects they belong to; connect their own OneDrive |
| Tenant / SharePoint administrator | Approve DocFlo’s read-only access to chosen SharePoint sites |