Published: October 5, 2026
A new virtual assistant may need a calendar, shared inbox, task board, file library, CRM, and several vendor portals. Treating that list as one request creates two problems. The assistant may wait for an essential account while receiving broader access elsewhere, and no one can tell which permission supports which task. An access request matrix turns the list into a set of decisions. Each row connects a work outcome to the minimum permission, an approver, a readiness date, and evidence that the account works.
Start with work, not applications
Write down the first two weeks of expected work before naming any tools. "Help with the inbox" is too vague. A better description might be: label new messages, prepare draft replies from an approved template, and route refund requests to the account owner. Those actions imply different permissions. Reading a queue does not automatically require sending mail, changing mailbox rules, exporting contacts, or deleting messages.
Repeat the exercise for each recurring responsibility. Ask what the assistant must view, create, edit, approve, export, or remove. If the answer includes an approval or a permanent deletion, confirm that the role should own that action at all. Many onboarding delays blamed on IT begin as unresolved role questions. The matrix makes those questions visible while there is still time to change the first-week plan.
Give every row a business owner
The person requesting an assistant should own the business reason for access. A system administrator can explain available permission levels, but should not have to guess whether the assistant needs customer records or financial reports. Put the business owner and the technical fulfiller in separate columns. Add a security, privacy, HR, finance, or legal reviewer only where the organization's rules require one.
This split prevents a common handoff failure. A manager submits "same access as Jordan," IT copies an old profile, and everyone assumes someone else checked the fit. A named business owner must instead describe the task and accept the proposed permission. The fulfiller records what was actually granted. Where the requested and available permission differ, the row remains open until the owner accepts a narrower workflow or an authorized reviewer approves an exception.
Use permission levels people can verify
Avoid entries such as "CRM access" or "Drive access." Record the workspace, role, group, folders, queues, or objects involved. For a CRM, the row might allow viewing assigned accounts and adding activity notes while withholding bulk export, user administration, and record deletion. For a file library, name the folder rather than granting the root drive because it is faster.
Include the environment. Training in a sandbox is a separate decision from using production customer data. If a realistic practice task is needed, create fictional or appropriately protected records instead of widening production access. The assistant should be able to read the matrix and understand what the permission is for, where it applies, and which actions remain outside the role.
Sequence access around supervised work
Not every account must be active at the opening minute of day one. Build a sequence that matches the onboarding plan. Communication and training tools may be needed first. A task system can follow once the manager explains its conventions. A sensitive operational system may wait until the assistant has completed a supervised example and the reviewer is available.
For each row, record a needed-by time in the site's working time zone. Add prerequisites such as signed agreements, required training, device enrollment, or manager confirmation only when they are real organizational requirements. Do not mark a row complete because someone sent an invitation. Completion means the intended person authenticated through the approved method and reached the correct scope without borrowing another person's account.
Test the account with a harmless task
The safest readiness check proves enough without changing live data. Ask the assistant to open a named training record, locate a specific field, or create a draft in a designated practice area. The checker records the account used, observed role, test time, and result. Screenshots should avoid secrets and personal information. A failed test returns to the row with a reason: invitation expired, identity mismatch, wrong group, missing license, or permission too narrow for the planned exercise.
Testing also catches accidental excess. If the assistant can see an executive folder while checking a training file, stop and correct the scope. Do not treat extra access as a harmless bonus. Record the mismatch, remove it through the approved route, and repeat the check. The evidence should show the final state, not merely the first attempt.
Plan expiration and removal at approval time
Temporary training roles need an end time. Permanent role access still needs a review trigger, such as a role change, manager transfer, extended absence, or end of engagement. Put the trigger and removal owner in the same row as the approval. This avoids a second investigation months later when nobody remembers why the permission was granted.
When access ends, verify the target system rather than closing a ticket on assumption. Check direct assignments, inherited groups, active sessions, API credentials, shared vault entries, and locally exported material where those items apply. The organization should follow its own retention, security, and employment rules. The matrix is an operational record, not a substitute for those policies.
A compact matrix that managers will use
Useful columns are: task outcome, system and environment, requested action, proposed permission, business owner, fulfiller, required reviewer, needed-by time, prerequisite, test step, observed result, expiration or review trigger, and removal evidence. Add a short status field with values people can distinguish, such as awaiting decision, approved, provisioned, tested, blocked, or removed.
Keep exceptions beside the affected row. If the CRM license will arrive late, name the safe first-week substitute and who approved it. Do not hide the gap behind an overall green onboarding status. A manager can then move training without pretending the assistant is ready for work that remains inaccessible.
The NIST definition of least privilege provides a useful control principle, but it does not decide the correct role for a particular company. That decision belongs to the authorized business and system owners. OnboardingEmployees can help teams map those decisions into a repeatable onboarding operations workflow and carry the final matrix into the first-week plan.
Continue building the workflow
Related support: virtual assistant role brief, virtual assistant onboarding checklist. The U.S. Equal Employment Opportunity Commission explains that employment selection procedures should be job related and consistent with business necessity.
Related reading

Run a First-Day Readiness Check for a Virtual Assistant
A practical virtual assistant first day readiness check for making evidence, ownership, decision boundaries, and handoffs visible.

Plan a Virtual Assistant's First Week Around Real Work
A practical virtual assistant first week manager plan for making evidence, ownership, decision boundaries, and handoffs visible.

Use a 30-Day Review to Strengthen Virtual Assistant Retention
A practical virtual assistant 30-day retention review for making evidence, ownership, decision boundaries, and handoffs visible.