A shared folder is enough when the right people can open the right files, find the current version and work with the permissions you agreed. Someone on your team also has to be able to keep those settings right as the review changes.
Before you shop for another tool, rehearse the job with sample files and separate recipient accounts. Check the documents people should see and the ones they shouldn't be able to open. The results tell you whether to keep your setup, fix it or look elsewhere.
Start with the review you actually have
Say an operations manager sends a monthly pack to an outside accountant. The same two people get the same approved reports every month, they need to download them, and the manager checks the pack before it goes. A well-kept shared folder may be all that job needs.
Now the business brings in an outside advisor who needs selected contracts, plus a specialist who needs only the technical reports. Both need the company overview. Every time the overview changes, someone has to keep both audiences current while the internal working notes stay private. The question becomes how easily your team can keep those separate views straight.
Adding people doesn't settle it on its own. What matters is how differently they need access, how often documents change and whether one person can keep the arrangement easy to follow.
Write down your next real handover: who receives it, what they're deciding, which files they need and when you'll review their access. Use that handover for every check below.
Check what your current tool can do
Google Drive lets you share with named people as a viewer, commenter or editor. Its documentation also explains how folder access passes down to files, and how subfolders with limited access can keep audiences apart. Check the account and folder setup you actually use. Google Drive sharing guidance.
OneDrive offers links that only work for specific people, though existing permissions can also give someone access. Your organization's administrators can limit which sharing options appear. So what the recipient actually experiences tells you more than the name of a button. Microsoft's OneDrive sharing guidance.
Check downloads on their own. Microsoft documents a Block Download option for supported view-only sharing in work or school accounts, depending on administrator settings and file type. Google documents controls for downloading, printing and copying, and says plainly that recipients can still share content in other ways. View-only can't stop someone taking a screenshot or a photo of the screen. Microsoft download controls, Google sharing restrictions.
Turn what you need into checks you can watch happen
Pick the rows your review needs from this table. Mark a row optional when it has no bearing on the job.
| Requirement | What to check | What to record |
|---|---|---|
| The right recipients | A named reviewer can sign in and open the agreed files | Account used, sign-in steps, any help needed |
| Different selections | Each reviewer sees the shared files plus their own | One allowed and one excluded file per audience |
| Current versions | A revised sample shows up where the recipient usually looks | Where you updated it and what the reviewer reopened |
| Downloads | Each file type behaves as agreed | Download allowed or blocked, plus any limit |
| Ending access | With every grant removed, the reviewer can't open it fresh | Links, direct permissions and groups checked |
| Oversight | The owner can find the records the review needs | An example record and who can see it |
| Easy to maintain | A backup colleague can repeat a routine change | Steps needed, confusing settings, who's next |
When a required check fails, work out why. The cause might be a setting to fix, an administrator policy to clarify or a process that's too hard to keep up. Keep those apart when you decide what to change.
Test with four sample files
Make a test collection with a common brief, an advisor-only sample, a specialist-only sample and an internal note. Use plain made-up content with an obvious revision label. Keep real customer, employee and deal information out of it.
Ask two colleagues to play ordinary outside recipients, using approved separate accounts without owner or administrator rights. Give them separate browser profiles so an administrator's session can't quietly supply extra access. Where your organization allows it, test with a real external account, since an internal colleague's experience may differ.
- Check the starting view. Both recipients open the common brief. Each opens their own sample and can't open the other audience's file or the internal note. Try a direct link to an excluded sample, and check whether it shows up in the list.
- Change the common brief. Replace it the way you normally would. Ask both recipients to reopen or refresh where they usually look and tell you which revision they see. Note any duplicate copy someone had to update by hand.
- Check a download decision. Try each file type you expect to share, from the recipient account. If a copy gets downloaded, note that it's now a separate copy on their device, and later changes can't recall or update it.
- End one recipient's access. Look at every grant, including group membership, folder access and old links. Remove the test recipient's access and try opening the file fresh from that account. Content already on screen and downloaded copies sit outside this check.
- Hand the routine to a backup. Ask a colleague to find the current document, who it's for and when the next access review is due. Note anywhere the answer depends on the original organizer's memory.
Record the results in the free shared folder decision worksheet. It's a manual record that works with any sharing tool. These checks tell you about the process you tested. They don't show that a service meets every security, contractual or industry requirement.
Decide from what you saw
Take the monthly accounting review. Say it passes its required checks: the manager can maintain the folder, the accountant can get the approved pack and a backup can repeat the handover. Keeping that setup is a perfectly good outcome.
In the advisor review, imagine the specialist can open the internal note through an old, broad folder grant. Pause real sharing, fix that grant and repeat the checks it affects. A new tool wouldn't spare you the job of deciding which documents each person should get.
If the permissions work but every shared revision means rebuilding several packs by hand, write that down. A different setup may earn its place by making the next update and the next access review easier.
Pick one outcome and name who owns it:
- Keep the current setup: the required checks pass and a colleague can maintain it. Set the next review date.
- Adjust and retest: a setting, account policy or procedure needs work. Record the change and which checks to repeat before using real documents.
- Look at an alternative: something you need is missing, or the recurring work is too much. Run each candidate through the same sample exercise and compare what you saw.
Keep any required certification, data location, retention terms or contractual commitments on a separate list. A tidy folder or a passing sample test isn't enough evidence for those. Confirm them with the people responsible before you share anything that depends on them.
Where a library and separate rooms help
Aurora keeps your documents in a library and lets each room share the files you pick from it. In the advisor example, one room could hold the common brief and approved contracts, and another the common brief and technical material. The internal working notes stay out of both rooms.
When people in the same room need different access, access groups and individual permissions narrow who can see or download its documents. They can't reveal anything you left out of that room. Replace a file in the library and each room using it shows the new version once participants reopen or refresh. Downloaded copies stay as they were.
That's worth trying when keeping several audiences current is the hard part of your work. If your participants mostly need to write a document together, put your existing co-authoring process into the comparison as well. Go with whatever helps people finish the review.
Try one realistic handover
Start by filling in the worksheet for your current setup. Record one required check, its result and who will make any change. Then pass that record to the colleague who'd cover the review if you were away.
To see the library-and-room approach, take the Aurora product tour. In a 30-day free trial, use one library and two rooms to repeat the four-file exercise with non-confidential samples. The trial includes one organization, unlimited libraries, two rooms, three internal users, 25 external users and 10 GB of storage, with no card required. See how easily you and your backup can keep both audiences current before you decide.
Shared folder decision worksheet
Free to use and adapt. Keep your completed worksheet in your own project files.
Download Worksheet (.md)A free working record for testing one external handover in your current tool or a service you're considering. Keep it internal, because it may describe access gaps and confidential material. Use sample files throughout.
Describe the review
- Review or project:
- What the recipients need to decide:
- Who looks after the source documents:
- Who can approve sharing:
- Backup organizer:
- Tool, account type and any administrator policies that apply:
- Must-have capabilities:
- Nice-to-have capabilities:
- Separate security, contractual or industry requirements, and who will check them:
- Test date, time and timezone:
Set the access you expect before testing
These entries are a starting example. Change the audience names and download decisions to match your review before you test.
| Test file | Advisor account | Specialist account | Organizer |
|---|---|---|---|
| Common brief, revision 1 | View | View | Maintain source |
| Advisor sample | View and download | No access | Maintain source |
| Specialist sample | No access | View and download | Maintain source |
| Internal note | No access | No access | Keep internal |
Test accounts should be approved for the exercise and have ordinary recipient permissions. Write down their roles, never their passwords or access tokens. Use a real external test account where you're allowed to, because an internal account may follow a different sign-in policy.
Record what actually happened
Status options: Pass, Needs change, Untested or Optional. A file opening for the owner doesn't prove the recipient has the right access. Test excluded files through direct sample links as well as the file list.
| Check | Required? | Expected result | What you saw and evidence | Status | Who fixes it |
|---|---|---|---|---|---|
| Named recipient can open the common brief | Yes | Correct account can open | To record | Untested | To assign |
| Advisor can open only their permitted samples | Yes | Common and advisor samples open | To record | Untested | To assign |
| Specialist cannot open advisor sample or internal note | Yes | Both blocked, including direct links | To record | Untested | To assign |
| Both recipients find revision 2 after reopening | Yes | Same revised common brief | To record | Untested | To assign |
| Downloads match the agreed file-type decisions | To decide | Use the access table | To record | Untested | To assign |
| Ended access prevents a fresh open | Yes | Former recipient cannot open the sample | To record | Untested | To assign |
| Required review record can be found | To decide | Define the event and fields first | To record | Untested | To assign |
| Backup can maintain an audience and update a file | Yes | Procedure can be repeated | To record | Untested | To assign |
Evidence can be a dated note of what you saw or a screenshot of test files. Leave out tokens, real private documents and personal details you don't need. Store any screenshot with this record and limit who can see it.
Example: a failure and a retest
Example result: the specialist opens the internal sample through an old folder link. The specialist account also belongs to a group with access to that folder.
What changed: the organizer fixes the broad group grant, reviews direct permissions and any remaining links, then repeats the internal-file, advisor-file and common-brief checks. Expected result: the excluded samples won't open and the common brief still does.
Retest result: leave this blank until someone actually runs it. Record who checked, when and which account they used. A corrected setting isn't a passed recipient check.
Updates and ending access
- Source revision before and after the update:
- Places you had to update by hand, if any:
- How each recipient found the revised file:
- Downloaded or already-viewed copies that later changes can't reach:
- Permissions, group memberships and links reviewed when access ended:
- Result of a fresh open after access was removed:
Choose the next step and own it
- Decision: Keep the current setup / Adjust and retest / Look at an alternative.
- Evidence behind the decision:
- Required check or commitment still open:
- Who makes the change, and by when:
- Handover notes for the backup organizer:
- Next review date or trigger, such as a new audience or a changed administrator policy:
This is a process exercise. It doesn't certify a service, assess every security risk or confirm you meet a contract, so check those separately. Removing online access doesn't recall downloaded copies or erase what someone has already seen.
