Start the register before the start date
Open the access register before the assistant's first day. List every system the role will touch, including email, calendar, shared drives, project tools, and client portals. Name the person who owns each account and the approval needed to grant access. Starting early prevents a first week spent waiting on forgotten permissions. Put the register in the same workspace as the role's other operating records.
Record the request date, the approver, and the date access was granted. A register that only lists the final permissions cannot show whether the approval happened before the grant. Keep the register in a system the team already backs up. A spreadsheet is acceptable when it has an owner and a review date. Ask the approver to confirm the entry rather than forwarding an email.
Record the owner of each account
Every account needs a business owner, not only an IT contact. The owner decides who needs access and what level is appropriate. The IT contact performs the change. When those two roles are blurred, access stays active because nobody feels responsible for reviewing it. Write the business reason for each permission in a short note. Keep the reason short enough to read during a review.
Write the owner's role as well as their name so the register survives a team change. Include the client-side owner for any client system. Ask each owner to confirm the entry at least once a quarter. The confirmation is short, but it turns the register from a snapshot into a maintained record. Remove the owner's name when the role changes and record the replacement.
Grant the minimum access the first week requires
Grant only the permissions needed for the tasks assigned in the first week. A new assistant does not need every folder on day one. Add access as the workload ramps and the review record shows the work is stable. This approach limits the damage from a mistake and makes the first access review simpler. Review the first-week list with the client before access is granted.
Use named accounts instead of shared logins wherever the system allows it. A shared login hides who did what and makes revocation difficult when one person leaves. When a shared account is unavoidable, record who else uses it and how the password is rotated. Never place a password in the register itself. Record the date a shared password was last rotated.
Separate shared credentials from named accounts
Keep shared credentials in a password manager with an audit trail. Do not paste them into the access register, a chat message, or a task document. The register should point to the credential's location and owner, not reproduce the secret. This keeps the register useful without turning it into a security risk. Point to the credential's location without copying the secret.
Require a named approver for any shared credential and a plan for rotating it when someone leaves. Limit the number of people who can reveal the secret. Review the list of users at the same time as the account permissions. A shared credential without a rotation plan is a permanent exception. Review the shared credential list whenever someone joins or leaves.
Review access at the end of week one
At the end of the first week, compare the access granted with the access actually used. Remove anything that was granted for a task that did not start. Ask the assistant which permissions are missing or too broad. The review catches both over-provisioning and hidden workarounds. Compare the used permissions with the granted list line by line. Remove anything that no task required.
Record the review date, the reviewer, and the changes made. If a permission is retained for a future task, write the date it will be needed and the owner who requested it. An unused permission with no future date should be removed. The first-week review is the easiest time to correct an over-broad grant. Set a calendar reminder for any permission retained for later.
Remove access the day a role changes
Treat a role change as a revocation event, not a background task. Remove access that no longer matches the new role on the same day the change takes effect. Update the register and note who approved the removal. Delayed revocation is one of the most common gaps in a growing team. Tell the client-side owner when access is removed. Record the confirmation in the register.
Include departure, leave, and client reassignment in the same procedure. A person on extended leave may still need access when they return, but the decision should be explicit. Record the expected return date and the owner who will restore access. The register should show the current state, not the state someone remembers. Keep the procedure in the same document as the register.
Keep evidence of the review
Keep a short evidence trail for each review: the date, the reviewer, the accounts checked, and the changes made. Do not store passwords or full credential details in the evidence. The point is to show that a person with authority looked at the access and made a decision. Store the evidence where the client can retrieve it during an audit.
Use the same evidence format every quarter so the records can be compared. If a review finds no changes, record that result too. A blank entry is not evidence. The trail should let a new operations lead understand why the current access exists. Use one format so the quarters can be compared without translation. Keep the old evidence for the client's retention period.
Hand the register to IT and the client
Give IT and the client-side owner a read-only view or a regular export of the register. Agree on who updates it and how quickly a revocation is recorded. Put the register on the agenda for the first monthly review. Access that nobody outside the assistant's team can see is access that nobody can govern. Agree the export format before the first monthly review.
Ask the client whether their own policy requires a different review cadence or a specific approval record. Adapt the register rather than keeping a parallel list. When the engagement ends, use the register as the checklist for the final revocation. A clean exit depends on a record that was maintained from the start. Run the final revocation as a checklist and record each completed step.
Continue building the workflow
Related support: onboarding operations support, contact us. The NIST Cybersecurity Framework 2.0 a voluntary framework for managing cybersecurity risk, including access control and identity practices.
Related reading
An escalation matrix a virtual assistant can actually use
A usable escalation matrix with observable triggers, named owners, response windows, and a test plan for the first month.
Write a task documentation standard before the VA starts
A documentation standard that gives a virtual assistant the inputs, decisions, examples, and review rules needed to finish work without guessing.
A quality sampling plan for a virtual assistant's first month
A first-month quality sampling plan that sizes reviews by risk, scores with a short rubric, and turns repeat defects into process fixes.
