AppsDrive

AI agents on your files · Autessa Drive

Folder scope and acting identity

Autessa Drive confines an agent to one folder when you set a folder scope on its Drive tool: every path the agent sends resolves inside that folder, and nothing outside it is visible, even if its identity could see more. Without a scope, an agent acting for a person sees exactly what that person can see.

Goes beyond a typical cloud drive
Start free
Drive tool · folder scoperootPath: /LegalSAMPLE

Agent can see

Legal
Contracts
NDAs

Invisible to the agent

Finance
HR
Board

the-problem.md

A helpful agent with too much reach

An HR assistant should not stumble into board minutes, even when the person using it happens to have access. Permission-aware AI needs both the person’s limits and the job’s limits.

README · what you get
  • Set rootPath (folder scope), such as /Legal, on a Drive tool.
  • Every path the agent sends is resolved inside the scope.
  • Nothing outside the scope is visible, even if the acting identity could see more.
  • An agent acting for a user sees exactly what that user would see in the explorer.
  • An agent running on its own, with no person, acts as your company, so give its tools a folder scope.
  • Write tools still need Editor access inside the scope.

how-it-works

How does folder scope and acting identity work in Autessa Drive?

  1. 1

    Open the agent’s Drive tool

    Or create one for the drive.

  2. 2

    Set a folder scope

    For example /Shared/Legal.

  3. 3

    Pick the acting identity

    The person chatting, or the company for unattended runs.

  4. 4

    Test it

    Ask about a file outside the scope; the agent cannot see it.

every-option

Scope and identity

OptionWhat it does
Folder scope (rootPath)Confines every path to one folder.
Acting for a userExactly that user’s access.
Running on its ownActs as your company; scope recommended.
PlaceholdersAny argument can be @@{...} filled at run time.

permissions

Who can do what?

WhoCan
Agent with a Drive toolSee the intersection of its scope and its acting identity’s access.
Drive owner and drive adminsGive agents scopes on drives they manage.

AI agents

How AI agents use it

Scope plus identity is the guardrail: the agent can never see more than the person, and never outside the folder the job needs.

Agents only reach files the person they act for can open, and every agent write is a version you can undo.

About Drive tools for agents →

connected

How it connects to the rest of Autessa Drive

DRIVE FEATURE

Drive tools

Where scope is set.

DRIVE FEATURE

Sharing

The person’s access the agent inherits.

AUTESSA PRODUCT

AI Firewall

Further controls on agent behavior.

faq.md

Questions about folder scope and acting identity

Can I limit an AI agent to one folder?

Yes. Set a folder scope on its Drive tool and every path resolves inside that folder; nothing outside it is visible.

Does an agent see more than the user it acts for?

No. An agent acting for a user sees exactly what that user can see, and a folder scope can narrow it further.

What about agents that run on a schedule?

An agent running with no person acts as your company, so give its Drive tools a folder scope.

Autessa Drive

Try folder scope and acting identity in Autessa Drive

Autessa Drive confines an agent to one folder when you set a folder scope, and otherwise lets it see exactly what the person it acts for can see, never more.

Start free

100% customizable, code and all

Make Autessa Drive fully your own.

Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.

Start free and make it yours