SECURITY & CONTROL
Autonomous does not mean unsupervised.
Folio acts where it should and asks where it matters. Every sensitive action runs inside your existing permissions, and the team can see exactly what it did.
§ 01 — Approvals
Folio asks before anything irreversible.
Sensitive workspace actions surface as an approval card. Tool approvals are configurable by action type, so the team decides what runs automatically and what waits for a human.
Control at every level
PLACE-LEVEL ACCESS
Permissions can vary by client, project, team, folder, page, file, channel, and role. Access follows the Place, so client work stays scoped.
GRANULAR PERMISSIONS
Control who can view, edit, move, archive, restore, and manage work — for people, files, pages, channels, and projects alike.
VISIBLE ACTIVITY HISTORY
Every change is recorded. The team can see what changed and exactly what Folio did, when, and on whose approval.
§ Data & access
Scoped to the work — not the person.
Folio operates within the permissions you already set. It can use signed file access and only the connected-app capabilities you approve, so it never reaches further than the work in front of it.
It is designed to ask before sensitive or irreversible actions, every time.
FOR YOUR SECURITY TEAM
We’re glad to walk your security and IT teams through Folio’s permissions model, approval controls, data handling, and current compliance posture before you roll it out.
Talk to us about security →Detailed compliance documentation is provided on request and confirmed before rollout.
“Autonomous where it should be. Approval-led where it matters.”