Box StrawberryEvery collaborator on every Box folder, grouped by person
A companion walks the whole tree in one pass, lists each collaboration and the role behind it, and hands you the view the sharing dialog will not give you.
The diligence room closed eighteen months ago. Two of the bankers have moved firms and one advisor’s engagement ended. Nobody has checked the collaborator list, because checking it means opening each folder, clicking the sharing panel, and typing names into a document.
A companion does the whole tree at once. It lists the collaborations on every folder, the members with access and the role each one holds, then groups them by person instead of by folder. In the same pass it searches by name or content keyword, reads file metadata, creates folders, moves, renames, and uploads by fetching a source URL.
| Box AI and the console | A Strawberry companion | |
|---|---|---|
| Answering “what does this contract say” | Reads content under Box governance | Works the record: where it is, when it changed, who can see it |
| Recording the review where your team will read it | Copy into a document by hand | Filed in the tracker or sheet in the same pass |
| Listing collaborators across a folder tree | One folder at a time in the console | Enumerated in a pass, grouped by person |
| Filing an incoming report into a dated folder | Manual upload and move | Folder created, file fetched from URL, moved; approved first |
| Deleting a file | Yes, with your enterprise retention rules | Possible, permanent, and gated behind explicit approval |
Run a Box access review in one pass
Walk this folder tree, list the collaborators on every folder, and tell me which people appear on folders their team should not touch. It enumerates the collaborations, attaches the role to each entry, and groups the result by person.
Adding access is the write side, and it is deliberately narrow: one person, one role, one file or folder. A companion proposes that with the role spelled out, because editor and viewer are one word apart in a request and very far apart in consequence.
Where do uploads come from?
From a link.
The upload tool takes a source URL, fetches the content, and lands it in the folder you name under the filename you give it. A report published at a URL or an export endpoint uploads cleanly.
The reading side matches: the file tool returns metadata, so a companion tells you that the Q3 contract exists, when it changed and where it lives. Box is the system of record, and a companion works the record.
What happens when you ask it to delete something?
It stops and asks.
The delete tool here is permanent rather than a move to trash, which puts it in a different category from most destructive actions, because there is no undo on the other side of a mistake.
So connect an account with the rights the job needs. An access review needs read. Filing and archiving needs read, create-folder and move.
File the review where your team will read it
The pass does not stop at a list. The same instruction lands the review in the tracker your team reads and records the archive in the sheet finance keeps. Chained across tools that is ordinary operations work; as a one-off it is data extraction with a governance question attached.
Run it quarterly as a routine and the access review stops being the thing an auditor has to ask for twice.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents