Several content and layout improvements to setting up and managing organisational and user permissions.
Setting up organisational permissions
Welcome screen
We combined the first and second pages of the onboarding flow into one as shown below.
On the one hand we worry about users not reading the content because there’s a lot of it. On the other hand we know that the current content doesn’t give enough information for some users to understand how permissions work.
So we decided it’s better to provide more verbose content so that users at least have the opportunity to fully understand how permissions work.
Permissions form
When some users submitted a form when the next page loaded they couldn’t tell the page had changed to the next relationship. We think this is partly because of the large and long page headings.
So we reduced the size and length of the headings as shown below.
We also found that even though there was content to explain organisations can view applications without setting permissions for this, that some users weren’t reading it.
So we decided to lay out the content like the other permissions. We used check icons instead of disabled checkboxes because disabled controls are not focusable by keyboard.
Check answers
The previous design made it hard to see which relationships related to which organisation. So we decided to use the card component as shown below.
And we added a note to explain why view permissions cannot be changed.
Managing organisational permissions
List page
In the previous design we labelled the page ‘Organisations’ but the section only lets you manage organisational permissions so we updated the heading.
And it didn’t give users any context as to what they could do in this section. So we added some guidance too.
Details page
We originally planned to roll out permissions such that all users with ‘Manage org’ permissions would be prompted to set up organisational permissions. But we accidentally launched the feature without doing this.
This meant that some users couldn’t do the things they needed like seeing safeguarding information even though they themselves had the permission. The organisational permissions weren’t set up.
When a user with ‘manage org’ permissions went to the details screen there was just a blank space to signify that there was no organisations with that permission.
So we decided to write content to make it clear that these permissions hadn’t been set up.
If you belong to the training provider you can set them up. But if you belong to the accredited body you can’t. So there’s different content depending on the situation.
And when setting up user permissions we decided to make it clear which organisations the permission is not applicable to. This should clarify why users with the right permission still cannot see or do things.
User permissions
In the previous design, when setting (or changing) user permissions we explained that all users get access to view applications without setting up the permission explicitly.
But not all users seem to spot this content. So we’re going to try the following design where users have to specify explicitly that they want to give this user view-only permission or otherwise.
