Automated Email Filer
Use this page to sign in and continue into the filing workspace.
Before you continue, please make sure you have the correct permissions on your O365.
Start with the first brokerage admin. Billing is activated once, then the rest of the team can be invited from setup.
Status
Confirm the mailbox, SharePoint target, and the next action for this brokerage. Then move straight back into setup or the review queue.
Current filing target
Use setup to choose the site, library, and root folder that should receive approved emails.
Mailbox health
Connect Microsoft 365 and run the first refresh to start watching inbox and sent mail.
No mailbox activity to show yet.
What to do next
Connect Microsoft 365, confirm the SharePoint target, and load enough client context to start reviewing live mail.
Tenant Setup
Connect Microsoft 365, choose a filing target, and load just enough Folio context to make mailbox filing trustworthy from day one.
Readiness
This workspace will guide an organisation from Microsoft 365 connection through to live Folio deal sync.
Progress
Brokerage
Shared context
Next best step
Checking setup…We are working out the shortest path to a successful first filing.
Step 1
Start by connecting the mailbox that will review, route, and file live email for this brokerage.
Step 2
Start with the site and document library where approved emails should be filed.
Step 3
Add the files you have, then run the loader. Only the data needed for matching has to be present.
Step 4
Import clients, policies, or deals to preview workspace folders.
Step 5
We are working out which brokerage the current user belongs to.
Support
Use this as a final scan before you move on, not as a second primary workflow.
Support
Recent setup actions appear here so you can confirm the last change before testing live mail.
No onboarding actions have been run yet.
Paste client, contact, policy, or deal data to model a new organisation.
Training guide
This guide shows brokerage admins and end users how Folio decides where email belongs, when a human needs to step in, and how to keep SharePoint records complete without chasing every message manually.
Brokerage admins and everyday mailbox users do not need the same depth of training. Start with the path that matches the role.
Brokerage admin
Admins own Microsoft 365 connection, SharePoint target, shared context, team access, and go-live checks.
End user
Most users should not manage the system. They should review uncertain mail, confirm edge cases, and let thread anchors do the repetitive work.
If someone is brand new to the app, this is the minimum path to become operational without guessing.
Sign in with the mailbox that should be monitored. Folio only starts acting on new mail from that mailbox’s first sync onward.
Select the site, library, and root folder where this user wants filing to land. This is a user setting, not a shared brokerage setting.
Import clients, contacts, policies, and deals so Folio has deterministic context before it ever needs to ask for human help.
Once setup is complete, users work from the queue only when Folio is unsure. Everything obvious should file itself.
The queue is easier to trust when every status has one clear meaning.
Folio found strong client and thread context, saved the message, and recorded the reason it trusted that destination.
Folio found plausible destinations but the confidence stayed below the auto-file threshold. This is where the user should spend time.
Usually seen on brand-new outbound email. Folio waits for thread or SharePoint proof before deciding, instead of prematurely marking the message as failed.
A user chose not to file the email, or the team intentionally excluded it. This is a final human decision, not an automation miss.
How Folio decides
Folio uses the known client, policy, deal, sender, subject, and thread history before it ever asks a person to step in. It is designed to behave like an operations system, not a black box.
What to do each day
Most users do not need to live in Setup. Their real daily workflow is much smaller.
This is the operating rhythm the team should learn. The system is healthy when most traffic follows the happy path and only the uncertain edge cases need a person.
Illustrated workflow
What users should notice
Users should always be able to see the destination, the confidence, and what action is available next.
These are the moments teams usually ask about during rollout.
If the sender, policy, and workspace context are obvious, Folio files it immediately. If not, the message lands in review with ranked candidate folders.
Once a thread has been anchored, replies should inherit the same destination so the team does not re-decide the same conversation.
New outbound items can appear in Waiting until thread context or SharePoint proof confirms the final location.
Folio starts from the first sync onward. It leaves older inbox history alone so teams can go live without backfilling years of mail.
The cleanest rollouts stay narrow at first, prove the workflow, then expand.
Use the checklist below when you onboard a new brokerage admin or rehearse a self-service rollout.
Phase 1
Confirm sign-in, SharePoint target, and shared context with one trusted user before inviting the wider team.
Phase 2
Watch a real day of inbound and outbound traffic. Make sure the obvious mail files itself and the uncertain items are explainable.
Phase 3
Once the filing target and shared context are stable, invite more users and let them inherit the same controlled workflow.
Inbox