You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is one are that is currently only doable on the back-end in a development environment for setup. Which currently doesn't allow final users (admin) to have the ability to add new permissionName or edit one (rename or disable for example), check the existing joins between template (or stages specific), permissions and users in the system.
The proposed solution to start with could be another Menu to be accessible by users - given the allowed preferences (which can be admin to start - and display at the "Configuration" top Menu. When clicked the user can be displayed to a page with:
A dropdown to select one of the existing permissions
A plus button to add a new permissionName
A table displaying existing users and templates/stages connected to the selected permission
The page could also allow the user to edit the selected permissionName and view details regarding the associated permissionPolicy, although editing a permissionPolicy in this page shouldn't be added due to the complexity of this task.
As agreed on previous team discussions, the existing set of permissionPolicies should cover most use cases. If a new one is required it should be done as part of the initial database reset on a development environment.
The text was updated successfully, but these errors were encountered:
Something that can be done also as part of this issue - perhaps in a separated one - is to also allow company's manager to check the staff permissions on the current company. This would require that the company listed is also filtered in the URL and that someone without full-admin permission only has access to a specific company that they are logged in to
This is one are that is currently only doable on the back-end in a development environment for setup. Which currently doesn't allow final users (admin) to have the ability to add new permissionName or edit one (rename or disable for example), check the existing joins between template (or stages specific), permissions and users in the system.
The proposed solution to start with could be another Menu to be accessible by users - given the allowed preferences (which can be
admin
to start - and display at the "Configuration" top Menu. When clicked the user can be displayed to a page with:The page could also allow the user to edit the selected permissionName and view details regarding the associated permissionPolicy, although editing a permissionPolicy in this page shouldn't be added due to the complexity of this task.
As agreed on previous team discussions, the existing set of permissionPolicies should cover most use cases. If a new one is required it should be done as part of the initial database reset on a development environment.
The text was updated successfully, but these errors were encountered: