Philippines staffing research · Published
On this page
Access review evidence in delegated mailbox support
A documentary review of what a quarterly mailbox access review can prove, which permission changes leave no usable record, and how to report the gaps honestly.
Methodology
This review defines a documentary protocol for testing whether a delegated client mailbox has current, owner-approved access; the unit is one mailbox plus the permission export, delegate list, and removal confirmations available for its last review. The protocol compares those records with public guidance from the National Institute of Standards and Technology and the U. S. Small Business Administration, which describe access control and small-business recordkeeping in general rather than the performance of any particular team. Inclusion rules are fixed before inspection so a mailbox with a clean recent review cannot be selected after the fact. The review reports documented entries, missing evidence, and open exceptions, not a security score or an estimate of risk. It does not judge whether an individual should be trusted with access, because that decision belongs to the mailbox owner.
Key Stats
- 4: record layers required per reviewed mailbox
- 3: public references used as background
- 0: security ratings assigned to people
Key Takeaways
- Separate the permission export, the business reason, the removal confirmation, and the owner approval into distinct evidence layers.
- Treat forwarding rules and connected apps as access entries even when they do not appear on the delegate list.
- Test removal in the user's actual mail client, because a disabled account can leave a signed-in session active.
- Record exceptions with an expiry date instead of leaving an unexplained permission open-ended.
Question and scope
This review asks whether a delegated client mailbox can be shown to have current, owner-approved access from its records alone. The population is mailboxes used by overseas assistants for client correspondence, and the unit is one mailbox with its most recent permission export and review summary. Freeze the inclusion rule before inspection so a mailbox with a recent clean-up is not favored over one with no review. Record the platform, the review date, and the person who approved the result beside each case. The record is the object of study, never the trustworthiness of an individual assistant. A mailbox with no review is counted as unevidenced rather than insecure, because the absence of a record cannot support either conclusion.
| Scope | One client mailbox used by delegated staff |
|---|---|
| Unit | Permission export plus review and removal evidence |
What the permission record shows
A permission export shows which accounts held which roles at the moment the export was taken. It can prove that a delegate was listed, that send-on-behalf permission existed, or that a forwarding address was configured. It cannot show whether the person used the access, whether they understood it, or whether the client approved it. Read the export as a snapshot, not a history. Compare it with the review summary to see whether every listed entry received a decision. An export with no decisions is inventory, not evidence of review.
| Shown | Accounts, roles, rules, and apps at export time |
|---|---|
| Not shown | Use, intent, client approval, or prior access |
Joiner, mover, and leaver events
Most access drift enters through three events: a person joins a client team, changes role, or leaves. The review should look for a dated record of each event and the permission change that followed. A mover is the hardest case, because old access often remains while new access is added. Check whether the old scope was removed on the same day or left for a later clean-up. A leaver with no removal date is an open finding regardless of how long ago the departure occurred. The record should name the person who confirmed the removal, not only the system that processed it.
| Joiner | New access with a dated business reason |
|---|---|
| Leaver | Removal confirmed by a named owner |
Shared credentials and recovery
Shared credentials break the clean relationship between a named person and an access entry. If several assistants use one stored password, the permission export cannot show who read a message. The review should record where the credential is stored, who can retrieve it, and when the recovery route was last tested. A recovery email that reaches a former employee is a finding even if every named delegate is current. Record the test date and the person who performed it. Without that evidence, the recovery plan is an assumption rather than a control.
| Recorded | Credential store, retrieval role, recovery test date |
|---|---|
| Omitted | Individual use of a shared credential |
Evidence gaps
Some access changes leave no usable record. A rule may be deleted without a screenshot, a mobile session may remain signed in after removal, or a client may grant access directly in their own portal. The review should list these gaps beside the result rather than hiding them in a general note. State which systems were covered and which were outside the reviewer's reach. A narrow claim about the covered mailbox is more credible than a broad claim about all client data. The gaps also tell the owner where the next control should be added.
| Covered | Reviewed mailbox and exported permissions |
|---|---|
| Uncovered | Client-side grants, cached sessions, deleted rules |
Review cadence and ownership
A quarterly review is a reasonable default for a stable team, but the cadence should follow the rate of change. A mailbox with frequent role changes needs a review after each event, not only at the quarter boundary. Name the owner who approves removals and the assistant who prepares the evidence as separate roles. Record the next review date before closing the current one. A cadence without an owner tends to slip, and a review without a next date is difficult to distinguish from a one-time clean-up.
| Default | Quarterly, plus after role changes |
|---|---|
| Owner | Named approver for removals and exceptions |
Sampling access between review cycles
A quarterly review can miss a change that happened last week, so sample a few mailboxes between cycles. Choose the sample from change events rather than convenience: a new assistant, a client contact who left, or a role that gained send permission. Three mailboxes are enough for a small team, provided the reason for each selection is recorded. The sample is not a substitute for the full review, and the summary should say so. Its purpose is to catch drift early and to test whether the joiner and leaver records are working.
| Trigger | Sample and timing |
|---|---|
| New assistant or role change | One mailbox within five working days |
| Client contact departure | One mailbox plus portal confirmation |
What the sample should collect
For each sampled mailbox, pull a current permission export and compare it with the last approved list. Check the delegate list, send-on-behalf settings, forwarding rules, and any client portal account that the team knows about. Ask the person who manages the mailbox to confirm the entries that changed since the last review. Save the export and the confirmation together, with the date and the reviewer's name. A sample that finds no difference still produces useful evidence that the control is operating.
| Record | What to compare |
|---|---|
| Permission export | Delegate, send, forwarding, and portal entries |
| Owner confirmation | Dated approval for each changed entry |
Following up on a sample finding
Record the sample in the same log as the quarterly review, using a separate row so the two activities do not blur. If the sample finds an unexplained entry, treat it as a full finding and escalate it through the normal removal path. Do not wait for the next quarter to correct access that no longer has a business reason. At the next quarterly review, check whether the sampled mailbox received a proper decision. This follow-through turns a quick check into a feedback loop rather than a one-time inspection.
| Finding | Next step |
|---|---|
| Unexplained access | Escalate through the removal path |
| No difference | Record the sample as operating evidence |
Limits of the record
The review cannot prove that no unauthorized reading occurred between exports. It also cannot show whether a client understood who could see their messages. Those limits should appear in the summary rather than being implied away. Report the mailbox, the export date, the decisions taken, and the known gaps. Avoid language that suggests the mailbox is secure or that every access path has been found. A modest, well-bounded claim gives the owner something they can act on and gives the next reviewer a fair starting point.
| Claimed | Documented access decisions for one mailbox |
|---|---|
| Not claimed | Absence of unauthorized use or complete coverage |
Client-side grants and portals
Some clients grant access through their own portal, outside the team's permission export. The review should list those portals, the client contact who manages access, and the date the team last confirmed the grant. A portal grant may be invisible to the mailbox administrator while still allowing a person to read client messages. Record the portal owner and the evidence of confirmation rather than assuming the two access systems stay aligned. When the client controls removal, note the request date and the expected response time.
| Portal | Client-managed grant with a named contact |
|---|---|
| Gap | Not visible in the internal permission export |
Reporting the review to the client
A client does not need the full internal access list, but they do need to know that the review happened and who can see their mail. Share a short summary with the mailbox owner and the client contact when the agreement calls for it. State the review period, the decisions taken, and any access that remains as an approved exception. Avoid naming every individual unless the client agreement requires it. A clear summary builds confidence without turning a routine control into a lengthy disclosure.
| Shared | Review period, decisions, approved exceptions |
|---|---|
| Withheld | Unnecessary personal detail or internal notes |
When to shorten the cycle
The quarterly cadence should shorten after a departure, a role change, or a client request that adds a delegate. Those events change the access list faster than the calendar anticipates. Run a focused review of the affected mailbox rather than a full program review. Record the trigger and the date so the next cycle can explain why an extra review occurred. If the same trigger appears repeatedly, the underlying onboarding or offboarding step needs repair. The cadence is a default, not a reason to wait when the facts change.
| Trigger | Departure, role change, or new delegate |
|---|---|
| Response | Focused review of the affected mailbox |
The review uses public access-control and small-business guidance only as background. It does not claim that the cited sources endorse this protocol or that their material predicts the security of any company's mailbox.
Sources
- National Institute of Standards and Technology: Publishes security and privacy controls, including access control guidance.
- U. S. Small Business Administration: Provides general guidance on managing small-business operations.
- Cybersecurity and Infrastructure Security Agency: Explains phishing risks that affect shared and delegated mailboxes.
FAQs
Does a disabled account prove access was removed?
No. Check the actual mail client and connected apps as well, because a signed-in session can survive the account change.
Should client-approved delegates be exempt from review?
No. Record the client's approval and still confirm the delegate is current and limited to the work they perform.
Can the assistant approve removals?
The assistant can prepare the evidence, but the mailbox owner or access manager should approve client-facing removals.
Related Research
Plan the next step
Bring one workflow and its recent records to a bounded review of evidence, gaps, and the next control to test.
Plan the next stepRead the daily blog guides · Explore service workflows · Plan your staffing routine
Take one delegated mailbox, export its current permissions, and pair every entry with a business reason and an owner decision before the next quarterly review.