Philippines staffing guide · Published

On this page

Set up a shared mailbox rule register for client coverage

A register for forwarding, filtering, and auto-reply rules in shared client mailboxes, with owners, test evidence, review dates, and a safe removal path.

Set up a shared mailbox rule register for client coverage

A shared client mailbox collects rules the way a desk collects sticky notes. One assistant forwards invoices to the bookkeeping folder, another adds a filter for a new client, and a temporary auto-reply stays active long after the holiday. None of those rules looks dangerous alone, but together they decide which messages reach a person and which disappear into a folder. A rule register gives the team a current list to review.

The register is not a copy of every setting in the mail platform. It records the rules that change where client mail goes, who can see it, or what a sender receives in reply. Each entry needs a purpose, an owner, and a review date. The goal is a short document the mailbox owner can scan before approving a change. Start with the rules that affect client-facing mail and expand only when the register proves useful.

List rules by mailbox and purpose

Create one section for each shared mailbox and list its active rules beneath it. Include forwarding addresses, folder filters, auto-replies, and rules that mark messages as read or move them to another account. Write the purpose in plain language rather than repeating the rule name. A purpose such as route supplier invoices to the accounts folder tells a reviewer what the rule is meant to protect. Note the date the rule was created and the last time someone confirmed it.

Include rules that were created by the client or by a former team member. Those are often the hardest to find and the easiest to forget. Check connected apps and integrations that can move mail without appearing in the rule list. Add them to the register with the same owner and review fields. A register that covers only rules the current team remembers will miss the drift that matters most.

Name the owner and review date

Give every rule a named owner who can explain why it exists. The owner does not have to be the person who created it, but they must be able to confirm that the rule still serves current work. Add a review date and a status of active, expiring, or remove. A temporary rule should carry the date it is due to end. When the date passes without action, the register shows the rule as overdue rather than silently keeping it.

Keep the register in the same place as the mailbox access record so reviewers see both together. The person who approves access changes can then check whether a rule moves mail outside the approved scope. If the client owns the mailbox, send them a short summary of rule changes at each review. Record their approval or their request to remove the rule. Ownership without a visible record is difficult to rely on later.

Test rules that move client mail

Send a test message that matches each forwarding or filter rule and confirm where it lands. Check the original mailbox, the destination folder, and any account that receives a copy. A rule can appear correct in the settings screen while a second rule intercepts the same message. Test with a subject line and sender that resemble real client mail, not an obvious test label. Delete the test messages and note the result in the register.

Test auto-replies separately because they speak to clients without a person reviewing each message. Confirm the text, the dates, and the recipients, and check whether the reply loops when two automated addresses write to each other. Turn the auto-reply off after the test unless it is meant to stay active. Record the test date and the person who checked it. A rule that has never been tested is a setting, not a control.

Remove or renew at each review

At the review, mark each rule as keep, change, or remove. Remove rules whose purpose has ended and confirm the change in the mail platform rather than only in the register. For rules that stay, update the review date and note anything that changed. Ask the owner to explain any rule that cannot be tied to current client work. An unexplained forwarding rule deserves a prompt removal and a short note about who approved it.

Check the register after a staff change, a client change, or a platform migration. Those events create new rules and leave old ones behind. Review the affected mailbox within a few working days rather than waiting for the quarterly cycle. Record the trigger so the next review can see why an extra check happened. Repeated triggers point to an onboarding or offboarding step that needs repair. The review should name the event and the person who reported it.

Keep the register beside the access record

The register and the access review answer different questions about the same mailbox. Access says who can open the mail, while rules say where the mail goes and who receives a copy. Review them together so a removed delegate does not leave a forwarding rule behind. Store both records under the same mailbox name and review date. A reader should be able to move from one to the other without searching.

Give the client a short summary of the rules that affect their mail when the agreement calls for it. State the purpose, the destination, and the review date without exposing internal notes. If the client asks for a rule that sends mail outside their organization, confirm the request in writing before making the change. Record the approval with the register entry. Clear client consent makes the next review much easier.

Review the register format after the first two cycles. Drop fields nobody uses and add a field only when a real decision needed it. Keep the document short enough to finish in one sitting. A register that grows into a second job will be abandoned, and the mailbox will return to its old drift. A short register that people use beats a detailed one they avoid.

Questions and operating boundary

Does every filter rule belong in the register?

Include rules that move client mail, forward it, change who sees it, or send an automatic reply. A simple label rule with no effect on delivery can stay out.

Who should own a client-created rule?

The client contact who requested it owns the purpose, while the team records the review date and confirms the rule still matches the agreement.

How often should the register be reviewed?

Quarterly works for a stable mailbox, with an extra review after a staff change, client change, or platform migration.

Source

cisa.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