Awareness and understanding of permissions. Increase site security. Minimize friction.
team
UX Team lead, PM , UX Writer, CS Rep, BI.
Role
Product designer
web app
discoverability
security
cms
+10% in security settings usage
CONTEXT
Permissions control who can view or submit content on your site.
Collection permissions let the site builder control who can read and write content to the CMS on their site. They should set up the currect permissions for each collection.
problems
60% unaware of collection permissions
(01)
+50% don't understand permissions
(02)
25% don't know how to change them
(03)
Why is that a problem?
👁️
Exposing sensitive user data
🚫
Failing to collect user data
💰
Cost in support
The database permissions modal was so bad that it caused so much extra work for me
user interview quote 😥
Mapping Issues
in the flow - before
Low discoverability
✗ Hidden in a tab
✗ Tab name irrelevant to user intent
in the flow - before
Unexpected
✗ After choosing “Custom use” the main CTA of the modal changes
✗ Users don’t notice it
✗ It’s bad practice
in the flow - before
Weird behavior
✗ Can’t save the permissions without creating the collection
✗ Modal inside a modal
I started by mapping out the user flow for issues, looking for:
-
Discoverability
-
Affordance
-
UX writing
Design
final design
A permissions tab
✓ Relate to user intent
✓ Standard, consistent, behavior
✓ Discoverable and prominent
✓ Better mapping and recognition
before
.webp)
after
After sketching out a few different options, I prototyped the the most suitable one to test it a flow. Once I was happy with the result I delivered a production a ready design to the dev team and moved to support their work when needed.
insights
Teach through using in context
(01)
Eggplants are berries
(02)
results
10% Increase in Collection permissions usage
(01)
Decline in related support tickets
(02)
