When a user encounters an authorisation-based error, RapidFTR currently gives a generic error message You are not authorised to perform this action This is sufficient to let the user know that the issue they are facing is related to permissions. However they are unable to tell exactly which permission they do not have (or which action they are unable to perform). For example, if this error occurs when the user attempted a sync, they may not know if this is because they have no permissions to create new child or enquiry records, or update them - since all these operations occur during a sync.
This enhancement adds more fine-grain notifications to ensure that the users know exactly which permissions are required (but which they do not have) when an authorisation-based error occurs
When a user encounters an authorisation-based error, RapidFTR currently gives a generic error message
You are not authorised to perform this actionThis is sufficient to let the user know that the issue they are facing is related to permissions. However they are unable to tell exactly which permission they do not have (or which action they are unable to perform). For example, if this error occurs when the user attempted a sync, they may not know if this is because they have no permissions to create new child or enquiry records, or update them - since all these operations occur during a sync.This enhancement adds more fine-grain notifications to ensure that the users know exactly which permissions are required (but which they do not have) when an authorisation-based error occurs