For more information on the authentication process for Humanitarian ID see our separate blog on HID. HFU in each country needs to decide if they want to do a broadcast or training for IPs. The HID guidance from the blog can be used for this purpose.
From 7 November onwards using the HID authentication mechanism will become mandatory for all users. Users without an HID will be migrated automatically, there account will be created and they will receive a link to reset their password. Single-Sign-On will no longer be available.
How about IP users?
They will be seeing the same screens. If they are no on HID, we will push them automatically on HID. A user account is created with exactly the same profile as is there in GMS and a password reset link will be sent to the e-mail ID used in GMS.
Partners who have created a HID to access OPS can use the same HID to access GMS. One profile to access multiple applications and HID will decide where you are coming from.
For new users we discourage the use of Single Sign-On. Please ask them to go to HID and register an account there and use that to log in to GMS.
Existing allocations have been migrated so when you open an allocation, you will be shown which scorecards were linked to this allocation.
Once an allocation has been updated and linked and a project is linked, you will no longer be able to change the data (scorecard linkages cannot be changed anymore). Changes can only be made before a project is created against this allocation. This will help us to ensure that all parameters (e.g. abbreviation code, scorecard, etc.) are matching across that allocation. In the past we have seen that people made changes in these values mid-allocation which resulted in conflicts in project codes and other areas.
In the ‘Project status info’ matrix (under the Fund Project Allocations – System Setup -> Allocation Management -> Manage Allocations Types) you will be able to see which projects are linked to this allocation and what their status is.
The Cluster-users who are logging into the system, when filtering for an allocation type will be able to only see the scorecard linked to that allocation.
HFU can see this when approving the user and adapt the profile according to what has been requested. This means in our example that they HFU while approving the user will change the 'Other' profile for the HFU profile before saving the profile.