Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Practical guides

    Manage accounts, permissions and access recovery

    Account security covers creation, permitted actions, recovery and closure. A successful sign-in screen does not show that a former collaborator has lost access or that recovery is properly controlled.

    Go to the method

    Security key, notebook and laptop
    AI-generated illustration

    Define the actions actually required

    List actions by role: read an enquiry, draft a page, publish, export or administer. Separate responsibilities where the context permits. Ask each participant to validate normal tasks and actions they should not be able to perform.

    Maintain an inventory of team and integration accounts with an owner and purpose. Secrets do not belong in this shared document. The inventory should establish who can act without turning a project spreadsheet into a password store.

    Review sign-in and sensitive actions

    OWASP covers authentication and associated controls, including attempts, protected transport, recovery and reauthentication for sensitive operations. Use a maintained solution and assess additional protection according to the risk.

    Prepare acceptance tests using an authorised account, a restricted role and an expired session. Test a sensitive operation through its direct address as well as its menu. Hiding a button alone does not enforce server-side permissions.

    Authorization applies to an action and resource, not just a successful login. The server must check the request even when it comes from a direct address or an asynchronous call. A hard-to-guess identifier does not replace that check. Deny by default when the applicable rule does not explicitly grant the required permission.

    The matrix proposes a fictitious policy: an editor may edit their draft DEMO-A1, but may neither edit another editor’s DEMO-B1 nor publish. After permission is effectively revoked, an already open page must not authorize a new edit. Repeat these cases with test accounts and records; check the response and absence of forbidden data effects, not merely the message or disappearance of a button.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Fictitious policy: check each action against the correct record
    Test account actionDecision defined for this scenarioEvidence to check
    Edit their draft DEMO-A1Allow the permitted edit.The expected change is saved to this draft alone.
    Edit another editor’s draft DEMO-B1Deny access to this action.No data from the forbidden record are disclosed or changed.
    Publish their draft DEMO-A1Deny because this role lacks that permission.Publication does not occur, even through a direct request.
    Edit from an old page after effective permission revocationDeny the new operation.The server applies current permissions; displayed state is not authorization.
    • OWASP : Authorization

      Consulted on 22 October 2026; least privilege, deny by default and permission checks on every request and resource.

    Rehearse recovery using test data

    In a test environment, simulate loss of a sign-in method, an expired link and a repeated attempt. Check messages, the recipient and the end of the procedure. Support needs a written method for exceptional cases.

    Decide how earlier sessions are revoked and how other access is reviewed after recovery. Do not ask someone to send a secret through an ordinary form as proof of ownership. Review the procedure with the solution’s security owner.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Rehearse account recovery
    Situation or settingWhat it meansUseful check
    Unknown or known addressCompare public messages without needlessly revealing whether an account exists.Use dedicated test accounts and check what actually arrives.
    Expired or already-used linkReject the old link and offer a clear way to request another.Also check that a new link does not reactivate the old one.
    A colleague leavesRemove permissions and review sessions that remain open.Check with the test account that previous access no longer permits protected actions.

    Plan onboarding, departures and handover

    Assign owners for creating, reviewing and closing access. A departure may affect the site, hosting, domain, connected services and authorised devices. Emergency access needs control, awareness among authorised staff and a test that does not expose it publicly.

    Keep a record of granted and removed permissions and the review date. Repeat representative tasks after a role or software change. This method helps find omissions but does not replace a security assessment suited to the service.

    Primary documentation : OWASP : Authentication Cheat Sheet.

    Reference documents

    Content updated on

    Acceptance matrix to adapt to your project

    These proposed checks use synthetic cases. Decide the required behaviour with the team, record the result and assign unresolved gaps before release.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Test cases, expected outcomes and useful evidence
    CaseExpected outcomeEvidence to retain
    Restricted accountThe protected operation remains refused even through its direct address.Synthetic account role, operation URL and server refusal status independently of the interface.
    Expired recoveryAn old link cannot restore access and a new request remains possible.Steps and displayed message, without retaining an actual recovery token.
    Contributor leavesAffected access and sessions are revoked under the agreed procedure.Checked tools and outcomes using synthetic accounts with known permissions.
    Administrator unavailableThe designated person can understand the planned recovery route.Documented recovery exercise in the test environment, including unresolved gaps.

    Frequently asked questions

    Is multifactor authentication enough?

    It can strengthen sign-in, but permissions, sessions, recovery, integrations and departures still need review. Also test what a restricted account can actually read or change.

    What should the next administrator receive?

    A list of services, owners, roles, recovery procedures and completed tests. Transfer secrets using the organisation’s secure mechanism, separately from editorial documentation or the project brief.