Context & pb
Currently, users with the User role do not have permission to:
- Create or delete occlusion masks.
- Annotate alerts.
When they attempt one of these actions, they only receive a generic error toaster, which does not explain why the action failed.
The error message should be more explicit, for example:
Your role does not grant you permission to perform this action.
This improvement should apply to:
- Alert annotation.
- Occlusion mask creation/deletion.
Livestream is already handeled
Notes
We should first verify the error messages currently returned by the API.Depending on the API behavior, the change may need to be implemented: on the frontend (mapping generic errors to user-friendly messages),on the API (returning explicit authorization errors),or on both.
Context & pb
Currently, users with the User role do not have permission to:
When they attempt one of these actions, they only receive a generic error toaster, which does not explain why the action failed.
The error message should be more explicit, for example:
This improvement should apply to:
Livestream is already handeled
Notes
We should first verify the error messages currently returned by the API.Depending on the API behavior, the change may need to be implemented: on the frontend (mapping generic errors to user-friendly messages),on the API (returning explicit authorization errors),or on both.