Inbox access protocol

How it works

Named owner. No shared password. Delegation instead of forwarded personal Gmail. Vacation coverage is a time-boxed delegate, not a screenshot of the password. For a U.S. company hiring one Filipino teammate, write this into the brief, the employment contract, and the peso payroll file before the start date. Slack habits do not override the Labor Code, BIR, or NPC. If the local employer of record holds the paper, they run the statutory step; you still owe a clean operating definition so the seat does not fail in week three. Put a number on the example when you budget loaded cost, because a nameless allowance always returns as a December surprise or a missed SLA.

Example: Ana owns founder@, delegate for sick days is Ben for 48 hours, then revoke. Log shows the window.

How it differs

Inbox owner is the role. Access provisioning is the broader checklist. Customer PII is what sits inside.

Common errors

Printing the password on a sticky in a family house.

In practice

Treat Inbox access protocol as a week-one operating object. Name the system of record, the device, and who can still log in on the last day. If the answer is a shared password, stop. Write an owner - founder, local employer, or worker - and a date you will look at it again: first cutoff, first holiday, or first miss. If nobody can show a contract clause, a payslip line, a calendar block, or a checklist box, you do not have inbox access protocol yet. You have a conversation. Convert the conversation before the person starts, while changing the deal still costs a paragraph rather than a resignation. Re-read the worked example above against the actual hire in front of you. If the numbers in that example cannot be swapped for this seat’s pesos, hours, and start date, the brief is still unfinished.