Agents

How to scope file access for an agent using Suite

Turn an agent’s assignment into focused file access and a clear output path using Suite’s supported permissions.

Give the agent the files it needs to do useful work

Give the agent the files it needs to do useful work

Suite’s administrator-managed file and folder access can support a focused assignment for an authorized agent on a supported host. Define the inputs it needs, the outputs it may create and any existing files it may modify. Map that scope to the available permissions and verify it as the identity doing the work, so the agent can contribute with a clear, reviewable brief.

Suite’s administrator-managed file and folder access can support a focused assignment for an authorized agent on a supported host. Define the inputs it needs, the outputs it may create and any existing files it may modify. Map that scope to the available permissions and verify it as the identity doing the work, so the agent can contribute with a clear, reviewable brief.

Use Suite’s documented permissions and setup flow, with the administrator approving the agent’s access brief.

Use Suite’s documented permissions and setup flow, with the administrator approving the agent’s access brief.

Make a small access brief

Make a small access brief

Consider a proposed task that reads approved source clips and writes analysis reports. Its brief could contain:

Consider a proposed task that reads approved source clips and writes analysis reports. Its brief could contain:

  • Input area: the approved clips needed by this job, including any required sidecar files.

  • Output area: a designated location for new reports, with a naming convention that avoids existing deliverables.

  • Allowed changes: whether the task may only create new outputs or also replace specific existing outputs.

  • Excluded actions: unrelated browsing, deleting source clips, renaming shared folders or creating external transfer links unless separately required.

  • Operating identity: the Suite user and host process that will run the job.

  • End condition: who reviews the outputs and when temporary access should be reconsidered.

  • Input area: the approved clips needed by this job, including any required sidecar files.

  • Output area: a designated location for new reports, with a naming convention that avoids existing deliverables.

  • Allowed changes: whether the task may only create new outputs or also replace specific existing outputs.

  • Excluded actions: unrelated browsing, deleting source clips, renaming shared folders or creating external transfer links unless separately required.

  • Operating identity: the Suite user and host process that will run the job.

  • End condition: who reviews the outputs and when temporary access should be reconsidered.

These are requested boundaries. Confirm which controls enforce them in the actual environment; writing a restriction in a prompt does not establish a filesystem permission.

These are requested boundaries. Confirm which controls enforce them in the actual environment; writing a restriction in a prompt does not establish a filesystem permission.

Check what Suite permissions actually cover

Set up the approved folder access in Suite

An authorized agent using the Suite drive needs access through the Suite member identity running its host process. Have the team administrator apply the agreed assignment scope using Suite’s User Permissions guide:

Suite's User Permissions guide describes file and folder access for team members, with separate controls for creating external transfer links. It also says administrators have access to the entire drive by default. An administrative identity is therefore a poor default for a narrowly scoped file-processing evaluation.

  1. Find the member. In Suite, open Team Settings and select Manage beside the intended team member. Administrators already have access to the whole drive; use the intended member identity when checking a limited assignment.

  2. Select the working files. Choose +Add File Permissions and select the approved files or folders. A selected folder includes its contents and subfolders, so choose a project area that matches the assignment.

  3. Keep transfer links a separate decision. Upload Links and Download Links control whether the member can create external transfer links. File processing alone does not establish a need for that capability.

  4. Verify from the working identity. On the intended host, confirm the designated input is visible and open an approved sample before starting the job.

If a non-admin member sees an empty drive, check assigned permissions before moving or uploading another copy of the media. Suite’s empty-drive troubleshooting guide explains this setup condition. Renaming a permitted file or folder changes its path; have the administrator re-add its permissions.

These controls establish access to selected files and folders. Confirm the required read and write behavior with the administrator; the guide does not document a special write-only output mode or independent restrictions for every operation.

Include the host process in the check

An agent application may run under a different host identity from the person who installed Suite. Check the intended process, path and access together. On Linux, the CLI configuration reference documents a setting that allows other local users to access the drive; its default limits access to the user who started the service. Treat widening that access as an administrator decision, not a routine workaround for a failing job.

For customer-owned storage, have the owner confirm the supported connection policy as well. Suite user permissions and the storage-provider connection are different parts of the setup. Do not invent a bucket policy or infer it from the agent's task description.

Verify the boundary with harmless samples

Before processing real material, ask the administrator to prepare an allowed sample and an out-of-scope sample for a controlled access check. Confirm the expected result for each. Do not use unrelated private files as test targets or modify original material merely to prove a restriction.

Record the identity, approved scope, observed result and unresolved controls. Review the scope when inputs, output destinations or responsibilities change. When the task ends, return the access brief and results to the owner so temporary access can be reviewed through the normal supported process.

The same guide explains that access to a selected folder includes its contents and subfolders, and that renaming a file or folder changes its path and requires permissions to be added again. Choose a stable test area and recheck access after a path change. Do not assume a folder restriction stays correct as the workflow changes.

Confirm the required read and write behavior with the administrator rather than inferring a detailed permission model from a short overview. In particular, this guide does not establish a special write-only output mode or promise that every requested action can be restricted independently.

Include the host process in the check

An agent application may run under a different host identity from the person who installed Suite. Check the intended process, path and access together. On Linux, the CLI configuration reference documents a setting that allows other local users to access the drive; its default limits access to the user who started the service. Treat widening that access as an administrator decision, not a routine workaround for a failing job.

For customer-owned storage, have the owner confirm the supported connection policy as well. Suite user permissions and the storage-provider connection are different parts of the setup. Do not invent a bucket policy or infer it from the agent's task description.

Turn a broad AI request into a concrete assignment

“Analyze our media library” is difficult to scope. A more useful first assignment is: “Read the approved interview clips for Project A, produce a transcript for each in the designated reports area, and preserve the source clips.” Name the approved tool or processing destination separately, because permission to read a file does not automatically authorize uploading its contents to an external AI service.

Include how the user will consume the result: the editor should be able to open each transcript, identify its source clip, and understand which portion was processed. Give the agent a defined stopping point, such as completing the approved list and reporting unresolved inputs.

Ask the administrator to map this assignment to the controls the deployment actually provides. If the agent needs broader inputs later, update the assignment and access decision before expanding the run. A narrow first task demonstrates the value of shared file access and creates a repeatable pattern for the next authorized workload.

Verify the boundary with harmless samples

Before processing real material, ask the administrator to prepare an allowed sample and an out-of-scope sample for a controlled access check. Confirm the expected result for each. Do not use unrelated private files as test targets or modify original material merely to prove a restriction.

Record the identity, approved scope, observed result and unresolved controls. Review the scope when inputs, output destinations or responsibilities change. When the task ends, return the access brief and results to the owner so temporary access can be reviewed through the normal supported process.

Put the idea to work

Start with your workflow.

Bring shared files into your familiar applications with Suite Managed, or connect your own supported storage with S3 Native. S3 Native requires at least 20 TB of active storage.