Please refer the attachment for proper understanding. It has pictures for better description.
Current access options are:
No access – Prevents the user from selecting the item or using it.
Modify – Allows a user to access an item, change it and then save it.
Create – Allows a user to create new files.
Delete – Allows a user to delete items in the system.
'Read' option should allow a user to access a property and change it but then not save the changes they have made. This would be exceptionally useful for ourselves with giving users a default table format view that they can modify but then are unable to save when they close the application, thus not affecting other users.
The current set up seems bizarre to go from no access at all, to being able to modify and save changes. There needs to be an intermediate level.
This functionality would be very helpful in our organisation and system set up.
Currently we are stuck with allowing everyone to change the incidents table view for everyone else or not allowing them to change the incidents table view at all.
Due to the wide ranging customer base, users need the ability to arrange data in the way they need but then not affect other users when they close the system which is what 'Modify' currently gives them.
This is a great idea that would benefit the way we set up users in our system. Due to the large customer base, the users need the ability to rearrange data in different ways without it changing the way another user has set up their information.
Since our go live date, this has always been an issue.
There have been many discussions and work arounds put in place but it should really be fixed at source.
We have hundreds of users that expect to log in and see today things how they left them yesterday.
To me, this should be fundamental functionality.