Logic in the dashboard that redirects the user when they don't have permission

[Sboonny]

Describe the feature
I have discussed this with @ojeytonwilliams today about adding status can't access error which turned to redirect users, I am opening an issue to document it (so I don't forget), and get your opinions.

Currently, we are hiding the component that people can't interact with in the dashboard, instead of doing that I thought of displaying "can't access" error in layout, when they don't have permission.

Oilver had a better idea, we can use /dashboard and add logic which direct users to the page they want, or can't access error if they don't have it.

This will make it easier to find the logic and update as it will be in something related to dashboard, and it would remove the need to hide some actions in the component itself.

[gikf]

I'm not sure if I understand how this would work. Any more specific example?

I think, if I'd click on some button and after loading next page, learned that I cannot use that button, because I don't have permission for it, I'd be pretty annoyed.

[Sboonny]

I will be honest, I don't remember what was discussed, and I haven't worked on it because of me taking break on holiday, so what Oliver suggested is completely lost, and we need him to give more context again. 🤦

here is the jest of what I wanted.

---

the layout.tsx has NextError for not logged in users, we can duplicate this and account for permission to view the children in the layout too.

here is the NextError:

chapter/client/src/modules/dashboard/shared/components/Layout.tsx

Lines 52 to 53 in 4cdff00

	if (!isLoggedIn)
	return <NextError statusCode={401} title={'Log in to see this page'} />;

We can add something like this:

const hasPermission = account for permission
 if (!hasPermission) 
   return <NextError statusCode={500} title={`Can't access this page`} />; 

This will clear the need for view permission in the DataTable files

[ojeytonwilliams]

I didn't take notes, so I'm a little hazy on what we discussed. From memory we were talking about redirecting users to a part of the dashboard they have access to, but on reflection I think that could be quite annoying. i.e. if they go to /dashboard/calendar but only have access to /dashboard/events then it'll redirect to the latter.

The current behaviour is okay, I think. We could, as Muhammed suggested, catch the fact a user doesn't have permission when we render the layout. That would give a slightly cleaner display.