Skip to article content

Who can access your website? How to review users and permissions

Identify the accounts on your website, who uses them and what each can do. Organise access without removing necessary functions or locking out your team.

Start by identifying who is responsible for each account

Your website’s user list may include employees, former providers and unfamiliar names. An access review establishes the purpose of each account and the permissions it needs. It does not have to begin by deleting everything you do not recognise.

Identify a responsible person or service and a current function for every account. “Manages orders”, “publishes content” or “synchronises the catalogue” is more useful than “has access”. If nobody knows its purpose, record the question and agree who will investigate.

The review needs authorisation and suitable access. Observing a website externally cannot confirm all its internal users or permissions.

Distinguish signing in from administering the website

Someone may need to edit content without needing to install plugins or manage other users. In WordPress, these permission sets are called roles. The official roles and capabilities documentation explains how permitted actions are assigned.

A role name provides guidance rather than a complete finding. Components and configuration can add or change permissions. Check the actions available in that installation, particularly where orders, customer information or configuration are involved.

The useful question is “What does this person need to do for their work?” Assess the necessary permission from there. After adjusting permissions, check that each person can still perform their assigned tasks.

Use an inventory that contains no passwords

A record for reviewing each account
FieldRecordPurpose
Account and systemIdentifier and panel it accesses.Distinguish accounts across services.
Responsible personPerson, team or service using it.Find someone who can explain its use.
FunctionCurrent task.Assess whether it remains necessary.
PermissionsRole and checked relevant actions.Compare them with the agreed task.
ProtectionSecond factor and prepared recovery.Identify outstanding checks.
DecisionKeep, adjust or prepare removal.Assign responsibility and a review date.

Keep this information somewhere with restricted access. Do not include passwords, recovery codes, application keys or screenshots showing them. The inventory identifies access; it should not become another way to use it.

Include service accounts and access outside WordPress

Some accounts let a tool import products, prepare reports or connect the website to another system. They do not necessarily belong to someone signing in every day. Identify the connection and whoever maintains it before removing them.

The hosting panel, domain registration, email and payment services may have separate access. Record which systems need their own review. Changing a WordPress password should not be presented as reviewing all those accounts.

If a handover is planned, use the website provider handover worksheet too. This article focuses on accounts and permissions; a complete handover also covers documentation, services and continuity.

Check login protection and recovery

Discuss giving each person an identifiable account rather than passing a shared password around. This makes it easier to arrange access, role changes and departures without having to remember who still holds a copy.

Check which accounts support a second authentication factor: an additional check beyond a password, such as an app or security key. The WordPress two-step authentication guide explains the concept. Availability and configuration depend on the service and installation.

Prepare how access would be recovered if responsibilities change or a device is lost. Recovery should remain under the business’s authorised control, without disabling protections or storing codes in the user inventory.

Prepare removals without interrupting necessary tasks

Before withdrawing an account, confirm that its function has ended or has a replacement. Review associated content, processes and connections and agree how to preserve them. The effects of deleting an account depend on the system and selected options.

Fictional example: an account bears a former provider’s name. It might no longer be used, or it could be associated with a catalogue import. Establish its use and responsible person rather than assuming it is redundant or must stay forever.

Record any adjustment and check the affected functions afterwards. A lack of recorded activity does not by itself mean an account is unused: the system may not retain that information or may record only some actions.

Leave a clear process for future access changes

The review is useful when it leaves clear responsibility for approving accounts, assigning task-appropriate permissions and reporting the end of a relationship. Revisit the inventory when teams, providers or important connections change.

It can also help answer a client security questionnaire accurately. Describe what has actually been checked without presenting the inventory as a security certification.

Nodo91 can review your website’s users and permissions within an agreed scope. Internal checks require authorised access; any subsequent changes are agreed before implementation.