Sharing Files

Share your own files and folders with a project so the agent can use them, choose read-only or read and write, and take access back

The agent can always use the files in its project folder. To let it use files kept somewhere else, such as a report on your desktop or a folder on a network share, share them with the project from the Levee app. You choose each file or folder and whether the agent may only read it or also change it, and you can take access back at any time.

Share documents and data: reports, spreadsheets, presentations, text files, images, exports and datasets. The agent reads and edits them like any other file.

Do not share programs or tools. Windows cannot start a program, or load the files a program needs, from the shared drive. If the agent needs a tool, ask your IT team: they can provide it as an AI tool or a plugin.

Sharing is on the project's Access Policy tab, which is shown in Advanced mode. If you use Easy mode, switch to Advanced in Settings > Experience > Mode first.

Select the project in the sidebar and open the Access Policy tab.
In the File access section, click Add file or Add folder, and pick it.
In the Grant file access window, check the Host location (the real place of the file or folder).
Under Access, choose Read-only or Read and write.
Click Grant access.

The item now appears in the list with its access level. You do not need to restart the project: a running project receives the change immediately.

You can share files from a drive in your computer or from a network share. Removable drives are refused.

Read-only or read and write?

Read-only: the agent can open and read the item, but not change, create, rename or delete anything in it. If it tries to write, Levee asks you first (see Approvals).
Read and write: the agent can also change, create, rename and delete files in it.

Choose Read-only unless the agent needs to change the files. To change the level of an item, revoke it and share it again; sharing the same item twice is refused with "This path already has a grant. Revoke it before changing its access."

Where does the agent find my files?

Shared items appear inside the sandbox on the L: drive, under a path that mirrors where they really are:

On your computer	Inside the sandbox
`C:\Users\alex\Documents\Reports`	`L:\local\c\Users\alex\Documents\Reports`
`\\finance\share\budgets`	`L:\network\finance\share\budgets`

Only what you shared is there; the agent cannot browse to anything else. Levee gives the agent a short guide to the sandbox, so when you mention "my documents" or "the budget file", it knows to look on L:\. You can just say which file you mean.

If the shared files cannot be connected in a session, the agent tells you they are not available and asks you to check the project's status in Levee, instead of claiming nothing was shared.

What about mapped network drives?

If you pick a file on a mapped drive letter, such as Z:\reports, Levee records its real network location instead (for example \\finance\share\reports). The Grant file access window shows both: the Selected path you picked and the Host location that will be shared. The item then appears under L:\network\....

If Levee cannot find the network location, you see "A file on a network drive could not be linked to its network location. Reconnect the network drive and try again. If the problem continues, contact support."

Can the agent open more than I can?

No. Levee opens shared files as you, with your own Windows permissions, and reaches network shares with your own sign-in. If you cannot open a file yourself, the agent cannot either. Your organisation's rules can narrow access further, never widen it.

How do I take access back?

On the Access Policy tab, find the item in File access.
Click Revoke, then Revoke access.

The running project loses access immediately, without a restart. If another shared item still covers the same place (for example, a parent folder), that one still applies.

Items marked Denied cannot be removed here, because removing a denial could give the agent more access.

What if something goes wrong?

Message	What to do
The change was saved, but the running sandbox could not apply it. Stop and start the project to apply it.	Stop the project and start it again.
This project is starting. Try again in a moment.	Wait until the project is running, then try again.
File access changed elsewhere. Review the refreshed list and try again.	The list changed since you opened it. Check it and repeat your change.
File requirement path is not allowed	The item is not on a drive in your computer or on a network share.

For your IT team

Your organisation's file rules still apply on top of what users share, and some accesses may ask the user for approval. See File access beyond the project for the rules, requirements and limits.
Every share and every revoke is recorded in the audit trail before it takes effect (grant.added and grant.removed, shown as FileGranted and FileRevoked in the Activity tab).
The list of shared items is kept by the Levee service in %ProgramData%\Vediram\Levee\grants\<projectId>.json, which only the SYSTEM account can access. Editing project.json in the project folder does not share anything. Items listed there by earlier Levee versions are not used until the user shares them again from the app.

Projects Approvals