Minor updates and code changes occur every day. Only significant or noteworthy updates are shown here. Updates shown with a gold background are (or were at the time) only available to Advanced HOPS members.

You are NOT currently subscribed to HOPS compliance system updates. More info

You are NOT currently subscribed to HOPS retail system updates. More info

Search: Clear


Time DateSystem Updates
Update 1473
14 May 2026

User Addresses

UNRELIABLE ADDRESSES

A new 'mark as unreliable' box has been added to users' postal addresses.

This is shown only to users with P407, and can be used to indicate when a user's address is suspected to be incorrect, eg if post has been returned. A details box is provided to enter details, and this is shown on the Address History tab.

The address gains an 'address unreliable' label next to it. This is shown in several places around the system, where addresses are shown, such as on staff lists.

Addresses that are unreliable have a 'Remove Unreliable Mark' button, for users with P407 only. Again, a details box is provided. The old and new records, including the record of it being marked unreliable and then that mark removed, are retained in the Address History.

This is also starting to be automatically populated by HOPS if ID cards, membership cards, or shareholder cards are returned undelivered.

---

MAP LINK

Did you know that a user's address on their profile is a link to Google Maps?

No?

Nor did I!

Well I probably did in the past but the link blends in a bit too well it wasn't obvious. This has been changed to a map pin icon to make it more obvious.

---

ADDRESS HISTORY

An 'Address History' tab has been added to user's profiles. It is visible to users with permission 407 and the user themselves.

Information back to 2020 is shown where we have it or have been able to infer it. Some information, such as who approves the change, hasn't been recorded in the past but is recorded from now on.

This has been requested following some examples of fraudulent / illegal activity by heritage railway workers and the address history becoming relevant in identifying people.

Available advice isn't consistent on how long this data should be kept for. Data in order to identify a worker who might subsequently suffer from an illness related to exposure to hazardous substances, eg, Mesothelioma, has to be kept for 40 years, or until they turn 80, whichever is longer - so the question we will seek to clarify is whether it is appropriate to retain all the user's addresses while they worked for the company, or only the address at the time they left. Like so many things, it seems to be there is no 'official' line, but if you get it wrong then you're wrong...

---

Thank you

Danny Scroggins
Update 1407
9 May 2026

System Updates

We have resurrected the System Updates system.

https://www.hops.org.uk/updates

I stopped posting updates to this a couple of months ago as some users received the email notifications more than once. I think we have fixed this now, and the test update (about the reinstatement of postcode lookup) seemed to go ok.

Receiving email updates is no longer controlled by a permission (was 168), it is now something that any user can subscribe to / unsubscribe from at any time. The option to do this is at the top of the System Updates page.
We will trickle out notifications of updates that have taken place in the last couple of months to avoid bombarding everyone.

When this change took place I automatically subscribed everyone who had the old permission.

Thank you
Update 700
12 December 2020

We recently undertook development work to make the VIEW permissions of user details more configurable, to meet the growing granularity with which clients want to control access. We have now deployed equivalent development to the EDIT permissions.

The large, coloured numbers in the table below are the new permissions, and the colours indicate the former equivalent permissions. 068, 069 and 405 have been split into 17 new permissions (407-423). We have altered all existing permissions allocations to groups and individuals so that everyone who had the old permissions has now obtained all the new ones. Ie, everyone who had 069 for a particular department has obtained 411, 412, 413, 414, 416, 420 for that department. So, in the majority of cases, if you take no action there will be no change.

EXCEPT..... we have straightened out some anomalies in permissions relating to viewing and editing custom fields and users' HOPS Account data. This may have introduced some non-backwards-sympathetic changes, ie, users who could previously edit a custom field or HOPS Account field might now not be able to. If this occurs, please either consult the table to see the new permission number required, or contact us if you have any problems.

<img style="width: 100%;" src="/public_docs/permissions_2020-12-12.png">

The number of grey tabs on a user's profile has been reduced by one, with the removal of the tab with the client company's initials. The information on this tab has been moved to the 'General' tab where it relates to the user at the organisation and the 'HOPS Account' tab where it relates to the user's HOPS Account.

We will, next, tackle the permissions for users editing their own details.
Please let us know if you find any problems.
Update 407
3 November 2016

Apologies the monthly Competence Expiry emails didn't work as planned on 1st November. These emails were upgraded to include more information about competence elements causing competences to expire during October and and error there caused them to not be sent at all!

They were all sent on 2nd November. Some users may have received two copies of the same email, apologies for this.

Just in case you're ever stuck, the list of competences expiring is always available as a list in a tab of the Competence Matrix. (The email is only really a prompt and, like any email, shouldn't be <i>relied</i> on.)