Philippines staffing guide · Published

On this page

Build a quarterly access review for a delegated inbox

A quarterly routine for reviewing who can read, send, and delegate from a shared client inbox, with evidence for removals, recovery paths, and owner sign-off.

Build a quarterly access review for a delegated inbox

A delegated inbox accumulates access quietly. An assistant joins to cover a busy month, a former contractor keeps a forwarding rule, and a client contact is added as a delegate for one project. None of those changes looks risky alone, but together they leave a mailbox that several people can read and send from without a current reason. A quarterly review replaces that drift with a dated record of who has access and why.

The review is not an audit of individual trust. It is a check that access still matches the work the team has today. Keep it narrow enough to finish in an afternoon and concrete enough that the owner can approve or remove each entry. The output should be a short list, a set of decisions, and a next review date rather than a general promise to be more careful.

List every mailbox and delegated permission

Start with the mailbox address and the platform that hosts it. Export the full delegate list, including people who can read, people who can send on behalf of the mailbox, and people who can manage permissions. Add shared rules, forwarding addresses, and connected apps, because those can move mail without appearing as a delegate. Save the export with the review date so the next cycle has a baseline.

Include the accounts that are not named people, such as help desk tools, booking systems, and archived integrations. Note the owner of each account and the last time someone confirmed it was still needed. An integration nobody recognizes is a finding, not a technical detail. The list should show the mailbox as clients experience it, including every route by which a message can leave.

Compare access to current duties

For each entry, write the task that justifies the access and the client or team it serves. A scheduling assistant may need calendar access but not the finance folder, and a document assistant may need read access but not send permission. If the justification is a project that ended, mark the access for removal. If nobody can explain the access, treat it as unowned and escalate rather than guessing.

Review the combinations as well as the single permissions. Read access plus send permission plus mailbox rule control is a powerful set, even when each item looks reasonable on its own. Flag any account that can change its own permissions or delete another delegate. The reviewer should be able to see the highest-risk combination without opening four separate screens.

Keep a separate line for access the client controls. Many client portals grant their own user accounts, and removing a delegate from the mailbox does not remove that portal user. Ask the client to confirm which accounts they created for the assistant and whether those should stay active. Record the client contact who made the change and the date. Without that step, the review can show a clean mailbox while an old portal login still reaches client data, and the next review should recheck both sides rather than assuming the mailbox record is complete.

Check shared credentials and recovery paths

Confirm where the mailbox password or passkey is stored and who can retrieve it. A shared password in a chat message is not a recovery plan, even if it is convenient during a shift change. Check the recovery email and phone number, and make sure they reach the business rather than a former employee. The review should record that the recovery route was tested, not merely that one exists.

Look for forwarding rules that send client mail to a personal address or an unmanaged inbox. These rules survive password changes and are easy to forget. Remove anything that cannot be tied to an approved workflow, and confirm with the mailbox owner before changing a client-facing rule. Record the removal date and the person who approved it so a later reviewer can reconstruct the change.

Test removal and reassignment

Do not assume that removing a delegate removes their access in every connected tool. After the change, ask the affected person to reopen the mailbox and confirm what they can still see. Check mobile clients, calendar invites, and any desktop app that cached the account. A removal that leaves a signed-in session active is not complete, and the review should say so plainly.

When access moves from one assistant to another, confirm that the new person can perform the task before the old access is withdrawn. Overlap the change by at least one working day for client-facing mailboxes. Document the handoff date, the tasks transferred, and any message sent to the client. The goal is continuous service with a smaller access list, not a fast removal that breaks the queue.

Record the review and next date

Write a short summary with the mailbox, the review date, the reviewer, the entries removed, the entries retained, and the owner who approved the result. Attach the permission export so the evidence does not depend on memory. Note any exception with an expiry date rather than leaving it open-ended. A review that produces no removals can still be useful if it records that every entry has a current reason.

Set the next review date before closing this one, and put it on the same calendar as the other recurring controls. Send the summary to the mailbox owner and the person who manages assistant access. If the review found a gap that needs a system change, assign it to a named owner with a due date. The next cycle should start from that list of open actions rather than from scratch.

Questions and operating boundary

How often should a delegated inbox be reviewed?

Quarterly is enough for a stable team, but review sooner after a role change, a departure, or a client request that adds new delegates.

Should the assistant perform the review alone?

The assistant can prepare the export and evidence, but the mailbox owner or access manager should approve removals and sign the summary.

What counts as sufficient evidence of removal?

A dated permission export after the change, plus confirmation from the affected person that the mailbox no longer opens in their apps.

Source

csrc.nist.gov provides authoritative background and does not endorse this service.

Explore services · Browse guides · Plan a controlled lane

Philippines staffing

Build a clearer work lane.

Share the role, tools, schedule, and approval needs. Those details help shape a practical Philippines staffing request.

Contact Us