research
Measuring the share of shared mailboxes with a named secondary owner
A method for checking which shared mailboxes have a named backup owner, current delegation, and a review date instead of an unowned inbox.
Use this benchmark to size repeatable IT work, set the review cadence, and decide what stays with the technical owner before assigning the workflow to an IT virtual assistant.
Research playbook
On this pageJump to section
Key stats
Key takeaways
A shared mailbox can keep working long after the person who owned it has moved on. The messages still arrive, but nobody is accountable for the queue, the access list, or the handover. This study counts the shared mailboxes that have a named secondary owner and checks whether that ownership is current. The result is a coverage measure for a service that is easy to leave unattended.
Question and scope
The study asks what share of shared mailboxes have a named secondary owner who can manage the mailbox and its access. The unit is one shared mailbox. The population is every shared mailbox in the company tenant on the audit date. Record the tenant, the export date, and the source of the owner record. Keep the definition with the export so the count can be repeated.
Include mailboxes used by support queues, sales, billing, and office administration. Exclude resource mailboxes for rooms and equipment, and mailboxes that are already scheduled for deletion. Note the mailboxes that are shared across two companies or managed by a vendor. A frame that mixes resource and shared mailboxes will overstate the problem. Record the cross-company mailboxes in a separate list for review.
Define a named secondary owner
Define a secondary owner as a current employee who is accountable for the mailbox and can approve access changes when the primary owner is unavailable. The person must be named in the ownership record and must know that the role is theirs. A group name or a distribution list is not a named owner. Write the definition before collecting so the count is consistent.
Decide whether the primary owner can also be the secondary owner. For coverage, the answer should be no, because one person on leave is the situation the role is meant to cover. Record the decision and apply it to every mailbox. An exception should have a named approver and a review date. Write the decision in the method note and apply it to every mailbox.
Build the mailbox frame
Export the shared mailboxes from the admin center with the address, the display name, the creation date, and the delegation list. Match the list against the ownership register or the service catalogue. Record the mailboxes that appear in the tenant but not in the register. A mailbox with no register entry is the first finding. A mailbox that is missing from the register is the first finding.
Remove the resource mailboxes and the ones marked for deletion, and record the excluded count. Normalise the display names so a renamed mailbox does not appear twice. Note the mailboxes that are nested under another address or used as a catch-all. Keep the raw export and the filter script so the frame is reproducible. Record the excluded count so the frame can be rebuilt.
Collect the delegation data
For each mailbox, capture the users with full access, send-as, and send-on-behalf rights. Note the groups that grant access indirectly. Compare the delegation list with the owner record to see who can actually read the mail. Access that is not reflected in the owner record is a gap in accountability. Access through a group should be listed as indirect delegation.
Record the last time the delegation list changed and who approved the change. Check for accounts that belong to former employees or external contractors. Note the mailboxes with more than five delegates, because a long list is hard to review. The delegation data is evidence of who can act, not only who is named. An old delegate who still has access is a live risk.
Check the owner record
Look for a current primary owner and a current secondary owner in the register. Confirm that both accounts are active and that both people are still in the company. Check whether the secondary owner has the access needed to add or remove delegates. A name without the access is a name that cannot cover the role. A name without access cannot add or remove a delegate.
Compare the recorded owner with the team that actually answers the mailbox. A manager may be named while the daily work sits with an assistant. Record the difference and ask which role owns the queue. The owner record should reflect the work, not only the reporting line. Ask the team which person actually answers the mailbox on a normal day.
Verify with a sample
Select at least ten percent of the mailboxes and ask each named secondary owner to confirm the role in writing. Ask whether they know how to add a delegate and where the access request goes. Record the answer and the date. A register entry that the person has never seen is not real ownership. Record the date and the wording of each confirmation.
Check the delegation list for the sample directly in the admin center. Compare it with the register and note any difference. Ask the primary owner who covers during their next leave. The sample should test both the record and the person's understanding of the role. A difference between the two records is a finding that needs a written explanation from the owner.
Classify the gaps
Group the mailboxes without a secondary owner by reason: no owner assigned, owner left the company, the role is vacant, or the mailbox is no longer needed. Add a category for mailboxes that are owned by a vendor. The reasons point to different fixes, from a simple assignment to a decision to retire the address. The reason should lead to a specific fix, not a general reminder.
Check whether a mailbox with no secondary owner still receives customer or supplier mail. A dormant internal mailbox is a lower risk than a live support queue. Record the message volume and the last received date. The classification should help the team fix the most important mailboxes first. Record the message volume and the date of the last received message.
Measure access risk
Count the mailboxes where a former employee or an unapproved external account still has access. Report that count separately from the ownership gap. Check whether the mailbox forwards mail to an external address. Access risk is more urgent than a missing name in a register. Report the access risk first because it can expose mail today rather than at the next quarterly review.
Look for mailboxes with a single delegate who is also the only owner. That combination creates a key-person dependency and a possible access gap during leave. Note the mailboxes with no delegation at all, because nobody may be reading them. Record the risk level and the evidence beside each mailbox. Record the risk level and the evidence for each mailbox.
Report and assign fixes
Write a short report with the frame, the share with a secondary owner, the access risk count, and the reasons. Group the result by department and by mailbox type. Use mailbox addresses or identifiers rather than personal names in the summary. Attach the export and the sample confirmation. Use mailbox addresses rather than personal names in the report table and the appendix.
Assign an owner and a due date to each fix. Start with live customer queues and mailboxes with unexplained delegate access. Record the new secondary owner and the date the person confirmed. Close a finding only when the register, the delegation list, and the person agree. A finding is closed only when the register, the delegation list, and the person agree.
Interview mailbox users
Ask two people who read a shared mailbox how they know who is responsible for a message. Ask what happens when the usual person is on leave. Record the answer without judging the team. The reply shows whether the ownership is real or only written down. The answer shows whether the ownership is real or only written in a register.
Ask the manager who approves access how they check that the request is valid. Note the route and the time it takes. Ask whether the secondary owner is included in the approval. A clear route prevents a mailbox from becoming a private inbox with a shared address. A clear approval route keeps a shared address from becoming a private inbox.
Repeat after staff changes
Rerun the study after a departure, a team restructure, or a new shared mailbox. A staff change can remove an owner without changing the mailbox address. Compare the new share with the previous one and investigate any drop. Record the event that triggered the rerun beside the new export. Record the trigger event beside the new mailbox export file and the review date.
Run a quarterly check even when no major change occurred. Add the new mailboxes and remove the retired ones. Check the secondary owners against the current staff list. A regular check keeps the register from becoming a list of names that no longer work there. A regular check keeps the register from becoming a list of names who have left.
Limits of the study
The study counts the mailboxes that exist in the tenant and the register. A mailbox that was deleted or never migrated is outside the frame. The measure also cannot prove that the secondary owner reads the queue or has the time to cover it. State these limits when the share is presented as a coverage guarantee. A deleted mailbox is outside the frame and outside the count.
Delegation data can miss access granted through a group or a mail flow rule. The owner record may be out of date even when the mailbox works. The measure describes accountability, not the quality of the service. Use the interviews and the access checks to interpret what the share means in practice. Use the interviews and the access checks to explain the share.
Sources and next step
Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the reopen, laptop order, self-restore, alert acknowledgement, and shared mailbox measures discussed here. The NIST SP 800-53 Rev. 5 supports the access and audit records, the NIST SP 800-34 contingency planning guidance supports the restore measure, and the NIST SP 800-61 incident handling guidance supports the alert review. Apply your own policies, contracts, and system documentation when adapting the method.
Compare this study with the ticket reopen measure and the alert acknowledgement study before combining them into one review cycle. If the measurement work is recurring and your technical owner can define the scope, review the service areas and contact ITVirtualAssistant to discuss a limited pilot.
Benchmark brief
What this research page must produce
A practical estimate for volume, review time, escalation rate, and assistant capacity.
A clear split between routine support, preparation work, and technical ownership.
What the measuring the share of shared mailboxes with a named secondary owner data shows
Treat this as a planning benchmark, not a universal number. Compare the benchmark against your ticket volume, SaaS stack, documentation backlog, and support risk before assigning recurring work.
The useful output is a decision about capacity, not a static statistic. If the workflow is high volume and low judgment, an IT virtual assistant can absorb coordination and upkeep. If the workflow is low volume but high risk, keep it with the technical owner and use the assistant only for preparation, reminders, and documentation.
Workflow
Recommended operating workflow
Collect a baseline
Pull the last 30 to 90 days of examples related to measuring the share of shared mailboxes with a named secondary owner, including completed work and unresolved exceptions.
Classify the work
Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.
Set the operating number
Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.
Refresh the benchmark
Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.
Decision rules
| Metric | Use it to decide | Manager action |
|---|---|---|
| Weekly volume | Whether the workflow is worth assigning as recurring assistant work. | Approve a weekly capacity target and backlog threshold. |
| Access sensitivity | Whether the assistant can work directly or only prepare review notes. | Set least-privilege permissions and removal dates. |
| Escalation rate | Whether the workflow is stable enough to delegate. | Rewrite the SOP when exceptions exceed the agreed threshold. |
Consolidated statistics
| Statistic | Figure | Source |
|---|---|---|
| Unit | One shared mailbox | Study protocol |
| Verification sample | 10 percent | Study protocol |
| Review cadence | Quarterly | Study protocol |
Sources
- Create a shared mailboxDelegation and access model used to define the mailbox frame.
- NIST SP 800-53 Rev. 5, Security and Privacy ControlsAccount management and access enforcement controls for shared mailboxes.
- NIST SP 800-63B, Digital Identity GuidelinesAuthenticator and lifecycle language for delegate accounts.
- CISA Cross-Sector Cybersecurity Performance GoalsAccess review baseline for small organisations.
Measurement checklist
| Field | What to capture | Owner |
|---|---|---|
| Volume | Weekly request count, backlog age, and repeat issue patterns | Assistant prepares, manager reviews |
| Risk | Access level, customer impact, security sensitivity, and approval needs | Technical owner |
| Cadence | Daily, weekly, monthly, or quarterly review rhythm | Manager |
| Evidence | Sample tickets, logs, screenshots, and before-after examples | Assistant collects, owner validates |
| Escalation | Triggers, approval path, response time, and stop-work rules | Technical owner |
How to read the result
A good research page should leave the manager with a working number and a clear boundary: what the assistant can do every week, what the assistant can prepare for review, and what must never move without the accountable technical owner.
Source and refresh note
This planning page is dated for 2026 and should be refreshed quarterly as tool stacks, ticket patterns, and security expectations change.
How should teams use this benchmark?
Use it to define task volume, access limits, review cadence, and escalation rules before assigning work.
Get free benchmark review