Define the cover task
Does the person need to read contact context, respond to a queue, edit records or manage forms? Those needs are different. Write the task before choosing permissions. Access to all form submissions may expose more information than access to the specific contacts a person needs. LACRM documents several form permission levels; check the current account behavior.
Keep access changes deliberate
Use your organization’s authorized account process to create or change access. Do not share credentials or disable a protection because the handover is urgent. Include the duration of cover and the person responsible for reviewing access afterwards. The site does not grant permissions or certify that a configuration is safe.
Check usability as well as the label
A role name in settings is not proof the person can complete the required task. Verify an appropriate non-sensitive sample and identify any legitimate restriction that blocks it. If a task needs broader access, route that decision to the authorized owner. Do not work around a restriction by exporting the whole database.
Worked scope
A fictional cover person only needs to review assigned enquiries. They do not need to redesign the public intake form or view every submission. The account owner chooses the narrow relevant access, confirms the workflow and includes a review date. Any paid-seat implication belongs in the budget rather than being hidden.
Check both allowed work and excluded work
A useful cover test includes one action the person should be able to perform and one area they should not need. Use an authorized non-sensitive sample and the provider’s supported account process; do not deliberately expose private records to test a restriction. Record any mismatch for the account owner. Once cover ends, the appropriate owner reviews continuing access according to the organization’s policy. Removing or changing access is a separate administrative action, not something a worksheet or handover note performs automatically.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- LACRM form permissions — Merchant documentation · lessannoyingcrm.com · Merchant-controlled · checked 2026-10-01
- LACRM pricing — Merchant documentation · lessannoyingcrm.com · Merchant-controlled · checked 2026-10-01