Users

Use this screen to add, edit, deactivate, and remove accounts connected to the website.

For an ordinary article correction, you do not need this screen. Ask the website administrator to manage access. A user account controls what someone can do in the admin; a team member describes someone on the public website.

Admin path: Website > Users
Routes: /users and /user/{id}

Find an account

The list shows each account’s state, Email, Name, and Permissions. The permissions column lists the account’s role codes, such as admin or manager. Select an email address to open the account.

Account types

The list can contain admin accounts and public Website accounts. Website accounts (permission code website) belong to public website functions. Their edit screen hides the password field, the Active account switch, and every role switch, and the list has no delete icon for them.

Add an admin account

Select Add user.
Enter the Email address. It is required.
Enter the Name colleagues should see. It is required.
Enter a Password. A new account cannot be saved without one.
Check that Active account is on.
Assign only the required roles.
Select Save.

After the first save, the screen opens the new account. The email address is now read-only. To use another address, create a separate account and retire the old one.

Check the address with the person before the first save. Use their own account rather than sharing another editor’s login. The name helps colleagues recognise them; it is not a substitute for the login email.

For the password, use the organisation’s approved password-sharing process.

🚫

Caution

Do not put the password in a screenshot or public support message.

Saving the account does not send an invitation or password email. Arrange the handover with the person and check that they can sign in.

Reset a password

Open the account from the list.
Type the replacement in New password. The field hint explains that a filled-in value replaces the current password.
Select Save.
Give the person the new password through the approved process.

Leave New password empty to keep the current password. Saving other changes, such as roles, does not touch the password while this field is empty.

Roles

The edit screen groups the switches into boxes. Each switch has a hint that summarises its effect.

Box	Switch	Effect
Website permissions	Active account	The account can sign in and use the login-only functions of the public website. Turned off, it cannot sign in with its password.
Editor permissions	Editor	Can open and save articles but not publish them. The switch is read-only and shows as on for Admin accounts.
	Publisher	Can publish content and edit pages. Use it when articles need approval before publication.
Admin permissions	Website manager	Can change the website’s basic settings.
	Admin	Can use the admin and change or delete content and users.
	Super admin	Has access to every function, including the website’s basic settings. The switch is read-only on this screen.

Note

The Editor permissions box, with both Editor and Publisher, appears only when Publisher Role is enabled.

On a Super admin account, the Active account, Website manager, and Admin switches are locked. A listed role does not guarantee access to every action. Ask the website administrator to confirm the permissions needed for the person’s actual tasks rather than enabling every editable switch.

If Publisher Role is enabled, someone who can write articles may still need an authorised publisher to make them public. Agree who reviews and publishes before changing this feature or a user’s roles.

The Newsletters menu appears for Super admins and for accounts with the newsletter-manager role. Ask the JORD team if someone needs this role to prepare and send newsletters.

Deactivate an account

Turn off Active account to stop a normal admin account from signing in without deleting it.

Open the correct user and check the email.
Turn off Active account.
Select Save.

This keeps the account record and its roles. Ask an administrator to review urgent access removal, including any existing sessions, rather than assuming the switch ends every active session immediately.

Delete an account

Delete an account only after confirming that the person no longer needs access.

In the Users list, find the account’s row.
Select the bin icon, Delete.
Confirm in the Confirm deletion dialog. It warns that the action cannot be undone.

The edit screen has no delete button. Website accounts have no bin icon, so they cannot be deleted here.

Check a new person’s access

Have them sign in with their own account and open the content screens needed for their work. Check the task they actually need, such as saving an article, rather than judging access from whether the dashboard opens.

If a menu is missing, check both their roles and the website’s Features. The login account and the public team profile are separate records, so changing one does not change the other.

Check your work

The email and name identify the intended person.
The account has the fewest roles needed for its work.
Publisher access is limited to approved reviewers.
Unused accounts are inactive or removed.