...
The standards or specialisms selected for a sub-user will change the visibility of apprentices within EPAPro and reporting. It will also adjust the notifications they receive, so that they will not get notifications for apprentices that are on standards they have not been assigned.
Noteinfo |
---|
Two new permissions have been added to support this:- These two permissions will allow the user to manage the standards and specialisms assigned, providing they also have update permission. Users will not be able to edit their own. |
...
If no apprentices have been assigned to a sub-user, they will continue to see all apprentices, as they do now.
Noteinfo |
---|
Two new permissions have been added to support this; These two options will allow the user to manage the apprentices assigned, providing they also have update permission. Users will not be able to edit their own. Both of these permissions have been given to the |
...
We have extended the roles functionality by introducing two new flags “Assignable by Provider” and “Assignable by Employer”. These can be toggled on for both custom and system roles.
...
Info |
---|
We have also added two new permissions to accommodate this;
Both of these permissions have been given to the |
Users with this role will be able to edit the roles/permissions for the relevant sub-users. If these permissions are given to a provider or employer sub user then the following will happen:
Note |
---|
We do not recommend giving the employer |
If providers are given “Change Role” for provider sub-users then they will able to change the role against their organisation’s users. They will only see roles that have been flagged as “Assignable by Provider”. If the provider is given “Change Role” for employers then they see a similar functionality with employers except they will only see roles that are flagged as “Assignable by Employer”, this is to prevent the provider from assigning provider-level roles to an employer user.
Employers will work in a similar way.
...
To help with organising these new reports, we have created two new reporting categories; “Providers” and “Employers”.
The existing provider and employer reports, which were originally under “Miscellaneous” have been moved to the respective categories:
Provider Details and Provider Standards, have both been moved to the new Provider category
Employer Details has been moved to the Employer category
Bulk Upload
Warning |
---|
TODO |
...
Bulk upload standard to employer/provider sub-users
...
We have added a number of new bulk upload imports for mass assigning apprentices and standards to provider/employer sub-users.
New Provider Import Tab
We have added a new “Import Providers” button to the provider listing screen and also a new “Provider” tab within the bulk upload screen. This is to accommodate the two new bulk upload imports for provider sub-users. The user requires the create permission for providers to see this button, along with the relevant permissions for each import.
Bulk Assign Standards
We have added two new imports for assigning standards to employer sub-users and provider sub-users. The new import is called “Assign Standards to Sub-Users” and can be found under the “Employer” and “Provider” imports. This import has the following columns:
Employer Sub-Users
This requires the Assign Standards and Specialisms
permission for employers.
employer_id - This is the ID of the employer the sub-user belongs to and is required
user_id_username - This is the user ID or username of the employer sub-user, this must be a sub-user of the employer_id given and is required
external_standard_id - This is the
external_standard_id
of the standard you would like to assign to the sub-user and is requiredspecialism_ids - This is a comma-separated list of specialism IDs that should be assigned, these specialisms must be part of the given
external_standard_id
and should be left blank if no specialisms should be assigned or exist for the standard
Provider Sub-Users
This requires the Assign Standards and Specialisms
permission for providers.
user_id_username - This is the user ID or username of the provider sub-user, this must be a sub-user of the provider selected on the screen or logged in and is required
external_standard_id - This is the
external_standard_id
of the standard you would like to assign to the sub-user and is requiredspecialism_ids - This is a comma-separated list of specialism IDs that should be assigned, these specialisms must be part of the given
external_standard_id
and should be left blank if no specialisms should be assigned or exist for the standard
Bulk Assign Apprentices
We have added two new imports for assigning apprentices to employer sub-users and provider sub-users. The new import is called “Assign Apprentices to Sub-Users” and can be found under the “Employer” and “Provider” imports. This import has the following columns:
Employer Sub-Users
This requires the Assign Apprentices
permission for employers.
employer_id - This is the ID of the employer the sub-user belongs to and is required
user_id_username - This is the user ID or username of the employer sub-user, this must be a sub-user of the employer_id given and is required
apprentice_id - The ID of the apprentice to assign to the sub-user. Required if
apprentice_uln
is not providedapprentice_uln - The ULN of the apprentice to assign to the sub-user. Required if
apprentice_id
is not provided
Provider Sub-Users
This requires the Assign Apprentices
permission for providers.
user_id_username - This is the user ID or username of the provider sub-user, this must be a sub-user of the provider selected on the screen or logged in and is required
external_standard_id - This is the external standard ID of the standard you would like to assign to the sub-user and is required
apprentice_id - The ID of the apprentice to assign to the sub-user. Required if
apprentice_uln
is not providedapprentice_uln - The ULN of the apprentice to assign to the sub-user. Required if
apprentice_id
is not provided