Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Access denied pattern #158

Open
mtallamy opened this issue Sep 11, 2018 · 9 comments
Open

Access denied pattern #158

mtallamy opened this issue Sep 11, 2018 · 9 comments
Labels
pattern Goes in the 'Patterns' section of the Design System

Comments

@mtallamy
Copy link

What

Pattern for Access Denied resource page, responding to an HTTP 403

Why

For authenticated sites, particularly for users with different roles/claims, they need to indicate where access to a resource has been forbidden.

Anything else

This is likely to take a similar format to the existing resource not found (404) pattern.

@stevenaproctor
Copy link

stevenaproctor commented Sep 11, 2018

@mtallamy The default one for HMRC is almost identical to the 404. We tried to keep it general rather than too technical.

<h1>You do not have permission to access this service</h1>
<p><a href=“mailto:emailaddress”>Email emailaddress</a> if you think you do have permission to access this service.</p>

@mtallamy
Copy link
Author

Thanks for this @stevenaproctor. I agree that should be non-technical and very close to the 404, which is what we've implemented as a starter for 10 (adapting the 404 pattern). I also agree there should be contact details if the user thinks they should have access.

The example you give appears to assume that a user doesn't have access to the entire service, which in our case at least might not be the case. I'd prefer to see the message relate to a specific resource, rather than the entire service.

From a security perspective, and this moves away from my request for a specific 403 page, I wonder if there should be any differentiation between a 403 and a 404, i.e. should we indicate to a (potentially malicious) user that a resource does exist, even though they don't have access to it. Be interested on opinions on this.

@stevenaproctor
Copy link

@mtallamy Good point about being able to access the service versus the resource. We use "service" because that is the more common case but there would definitely be times when people could not get into specific resources or journeys. But, in our case, this would be handled, generally, without getting a https error.

Our page is almost identical to our 404 but we felt saying 'Page not found' was not the best user experience.

@CharlotteDowns CharlotteDowns added the pattern Goes in the 'Patterns' section of the Design System label Oct 13, 2021
@adyhoran1
Copy link

adyhoran1 commented May 20, 2022

Myself and other DfE content designers have created You do not have access pages for internal services. I think a pattern that gives guidance to Civil Service on whether and how to create You do not have access pages would be very useful 🙂

image

You do not have permission to perform this action

You do not have access

image

image (2)

image (1)

@Huskyteer
Copy link

Example from the Home Office used for 401 and 403 errors.

Screenshot 2022-05-20 at 16 56 11

@Ciandelle
Copy link

Quick question - do we feel like this idea is covered by the There is a problem with the service pages?

@edwardhorsford
Copy link

Quick question - do we feel like this idea is covered by the There is a problem with the service pages?

@Ciandelle they're similar / related, but it's a different content need.

@edwardhorsford
Copy link

@Ciandelle I do think there could possibly be a single section on error pages with a bunch of different examples - you don't necessarily need a 'pattern' on each...

@mtallamy
Copy link
Author

@Ciandelle I do think there could possibly be a single section on error pages with a bunch of different examples - you don't necessarily need a 'pattern' on each...

agreed, sounds good!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pattern Goes in the 'Patterns' section of the Design System
Development

No branches or pull requests

7 participants