thinking of this in the context of using the CLI or the API directly, "page" doesn't make a ton of sense

I know theoretically we're now always settingDetail for 403 responses, but what if it comes back undefined from some endpoint that doesn't usehttpapi.Forbidden when it should? do we care about handling that? maybe we don't and it's fine 🤷‍♀️

Nit: I don't know your opinion on ternaries, but I feel like the typical React way of doing this would be to inline everything into a single return statement:

return(<Alertseverity="error"{...alterProps}>{status===403      ?(<--JSX-->)      :detail ?(<--JSX-->)      :(message)</Alert>);

Prettier/Biome should be able to format the ternaries to make them more readable than this, but you get the idea

I'm usually pro ternary but I've been trying to match other general vibes of the code base. Generally though I think I've started to learn towards if the logic is more than an "if/else" it's more readable being broken out

I'm okay with this as a baseline solution, but do you know if there are ever cases where it makes sense to redirect the user to a page more relevant to what they were trying to access?

Yeah I agree, and I'm actually working on a PR right now that will makeRequirePermissions a bit more user friendly in that way. But this change is still relevant in the cases where we don't wrap a portion of the page inRequirePermissions