Skip across the chapter
Quota Playbook

Call review folders: 4 limits to check before sharing

Quota Playbook Editorial Team · Published · 10 min read

Before sharing a call review folder, check its owner, member roles, comment deletion rules, and item limit. You add recordings, drop in transcripts, and write coaching notes after each call. The trouble can start when you share it. Each person you add can have a different level of access, and the folder may end up holding more than you planned.

Key takeaways

  • Check the parent folder's owner before creating subfolders.
  • Give each person access based on the work they need to do.
  • Record whom to ask when a comment needs removing.
  • Count items inside subfolders before sharing.

Those files can include customer names, pricing talk, and candid feedback about how a rep handled a hard question. Who can see them, who can change them, and what the folder can hold all matter. This post is written for a front-line manager of a small B2B software sales team who keeps call review recordings and notes in a shared cloud folder, but the questions are the same for anyone who shares that kind of folder.

Before you send the link to your sales team, check four limits. Each one comes from an official help page, and each one affects either who controls the folder or what fits inside it. The limits below come from three vendors: Dropbox, Box, and Microsoft's OneDrive and SharePoint. Your team may use one of them or a different service. The rules differ from one service to the next, so read the page for your own tool before you rely on any of them. Nothing in this post tells you how your current folder is set up, so check that yourself.

Think of these checks as a short routine for each folder, not a one-time task. You will add people, create subfolders, and move files as coaching goes on, and each of those steps can change the answer.

Limit 1: In Dropbox, only one person owns each folder

Under Dropbox's help page on sharing permissions, only one person can be the owner of a folder. Dropbox, "How to manage Dropbox sharing permissions" For a call review folder, decide who that person is before anyone else gets access.

The owner matters for one more reason. The same page says the owner of a shared folder can change the setting the page describes. Know who holds that role before you start inviting people, and write the name down so the answer is not held only in your head.

The page also covers subfolders, and this is where ownership changes without anyone deciding it should. Under Dropbox's rule, if you create a subfolder within someone else's parent folder, then they become the owner of the subfolder. Imagine a sales manager owns a team folder, and you create a subfolder for one quarter's calls inside it. The manager becomes the owner of that subfolder, not you.

Before you create a subfolder, open the parent folder and check who owns it. If that person is not the one who will manage the subfolder, decide that now, not after the calls are filed. A small change at the start is easier to handle than a surprise later.

A simple structure helps. The goal is not a perfect structure. The goal is that you know who owns every folder in the set, so you are never guessing when someone asks about ownership.

Plan for ownership changes too. If the person who owns a folder moves to another team, pick the replacement before the change, not after. Record the handoff in the same owner note, with the date.

Write the owner's name at the top of the folder's first note, along with the date you last checked. It takes a minute, and it gives everyone one place to look when a sharing question comes up.

If you are not sure who owns a folder, look before you add anyone. Checking the owner first is quicker than untangling a sharing change after reps have already started filing calls in the folder. Make the check part of the routine, not something you do only when a problem appears.

Limit 2: In Dropbox, members are editors or viewers

In Dropbox, any member you give Can edit permission to is an editor, and any member you give Can view permission to is a viewer. Dropbox, "How to manage Dropbox sharing permissions"

The same page names these two roles, and they are useful for a call review folder because the people in it do different jobs. A rep who only needs to read the feedback on their own calls fits the viewer role. A manager who files recordings and writes review notes is someone you might make an editor. You know your team, so make the call based on the work each person does.

Build the list before you send any invitation. Write each name next to one role, and ask whether that person needs to change anything or only needs to read. Leave the editor role off anyone who does not need it. Starting with fewer editors is simpler to explain to the team, and you can add an editor later when someone's job actually requires it.

A simple table helps. Use three columns: name, role, and the reason for that role. The reason column is the one people skip, and it is the one that catches mistakes. If you cannot write a reason for an editor role in one sentence, that role is probably wider than the job needs.

Be careful with people outside your team. A coach from another group, a sales operations person, or a senior leader may need to look at a few calls. Decide whether each of them needs to read or to edit, and give only that role. They belong on the list like everyone else, with a name, a role, and a reason.

Review the list when people join or leave the team. The goal is for each name in the folder to match the role that person should have today, not the role they had last quarter. A short review every time the roster changes keeps the list accurate without much effort. When you remove someone, update the list the same day. A name that stays on the list after that person has left makes the list harder to trust, even when nobody has used the access.

Keep the list in the same place as the folder's owner note. When one document holds the owner, the roles, and the check dates, you will not have to hunt through the sharing menu to answer a basic question. Use the team role checks when the setup changes.

Limit 3: In Box, only certain people can delete comments

In Box, comments can be deleted only by the folder owner, co-owner, or the person who created the comment, according to Box's support article on collaborator permission levels. Box, "Understanding Collaborator Permission Levels"

Read that rule against a call review folder. Comments on a call are part of your review record, and sometimes a comment needs to come out. A note may be wrong, may have been posted to the wrong call, or may contain something the team should not keep in a shared place.

Here is an example. A manager adds a coaching comment to the wrong call, and the rep points it out in the next one-on-one. The manager created the comment, so under Box's rule the manager can delete it.

Tell the team where that path lives. A short line in the owner note, saying who removes comments and whom to ask first, means nobody has to search for the answer during a busy week. Review that line when the owner or co-owner changes, so it still names people who hold those roles.

Decide who the owner and any co-owner will be before the folder fills up with feedback. Put those names in the owner note from Limit 1, and tell the team that comment cleanup goes through them if the writer is not available. This is also a reason to be clear about ownership from the start, because the owner has a role in the comment rule.

Think about what goes into a comment before anyone types one. A comment is part of the record, so write feedback about the call and the behavior, not personal remarks about the rep. Keep customer details to what the team needs to coach the call, and leave out anything you would not want a rep to read back to you. Review the call note checks before posting feedback.

This is a Box rule. It does not describe how comments work in Dropbox, Microsoft's services, or any other tool. If your team uses more than one service, check each tool's own help page and write down the answer for each one.

Limit 4: Count sub-items in OneDrive and SharePoint

When you share a folder in OneDrive or SharePoint, you can include up to 50,000 sub-items within that folder and its subfolders, according to Microsoft's support page on restrictions and limitations. Microsoft, "Restrictions and limitations in OneDrive and SharePoint" Count items directly inside the shared folder and inside its subfolders; do not count the shared folder itself as a sub-item.

A call review folder grows steadily. If you keep a recording, a transcript, and a note for each call, the items can add up faster than the top level suggests. Count the items once when you set the folder up, and check again at regular intervals as the folder fills. A quick count is much easier than discovering a problem after the team has already built its routine around the folder.

Count the way the limit is written. A folder that looks small at the top can hold a lot once you open each quarter's folder. Open each subfolder and count what is inside, rather than estimating from the top level.

Watch for batches. If you copy a set of call recordings from a personal drive into the shared folder, the count goes up by the number of items you copied. Move material in one batch, and recount after the batch, so you can see its effect before you add the next one.

Keep a record of the counts too. Write the date and the count in the owner note each time you recount. That way the growth shows up at your next review, instead of arriving as a surprise on the day you try to share the folder.

Do not mix this up with a second number on the same page. Microsoft's page also gives a supported limit for unique permissions in a list or library, which is 50,000 items. That is a separate limit from the sub-item limit above, and it applies to lists and libraries. When you check your numbers, keep the two apart so you do not read one as the other.

If a folder is close to the limit, consider splitting it by period or by team. Each new folder then needs its own owner, its own editor and viewer list, and its own comment rules. Splitting is only a good move if you also repeat the other three checks for each new folder.

Illustrative example: Recount after a batch

An illustrative folder holds 40 items. You copy in 10 recordings, bringing the count to 50 items. Record the new count and the check date in the owner note before adding another batch.

Checklist before you share

Use the opening checklist each time you share a folder, or change the people or subfolders in it.

If one check fails, do not share the folder yet. Fix the owner, the roles, the comment rules, or the count first, then send the link. A short delay is better than sharing a folder with the wrong people or the wrong number of items in it.

Copy the list into the folder's first note today, and go through it again when you add people, create subfolders, or change tools. Sharing a folder is a small decision, but the people and files in it are the record of your team's coaching, so a few minutes of checking now keeps that record under the control of the people who should have it.

Questions before you share

Should you check every service separately?

Yes, check each service's own help page before relying on a sharing rule. Keep the answers with the folder's owner note.

When should you review the access list?

Review it when people join or leave the team. Update the list the same day you remove someone.

Sources

  1. Multicurrency deals: 5 value checks before coaching
  2. Get back an old coaching doc version: 4 tools to check
  3. CASL email opt-outs: 3 checks for sales managers
  4. Predictive opportunity scoring limits
  5. New seller backup setup

More plays