Permissions on the View level
planned
Vasken Bakalian
I love the structure of the Permissions on how application permissions can override solution permissions, and also noticed permissions on the field level are coming soon.
Checked for "permissions on the view level" in the community, YouTube and checked if possible in the tool, and couldn't find it.
For example, I have the work logs of my staff in an app, where I need to share different views with different people.
Will hide the "rate" column, and share it with the project manager, need to share the dashboard view with the client, and so on...
Is it possible SS is considering this case or is this topic already discussed in the community?
super thanks!
Nate Montgomery @ SmartSuite
Merged in a post:
user rights for views
Martin Böhmer
Ability to define user right for views. For example if a grid is for printing and export purposes only, it should be possible to hide the plus button and to disallow editing, perhaps even sorting or grouping, since this could potentially destroy the sense of the view.
Jon Darbyshire
planned
Jon Darbyshire
Thank you for posting, Martin Böhmer! I have a few more questions for you:
- Can you provide more details on the different user roles you envision for your application?
- Are there any specific views or features where you'd like to apply these user rights restrictions?
- Could you elaborate on the potential issues that may arise from allowing users to sort or group data in these views?
Martin Böhmer
Jon Darbyshire
- Currently I am developing solutions with PHPRunner and in former years I did the same with FileMaker. There you always could define rights for View, Editing, Deleting, Adding, Importing, Exporting and Printing for every single view. Perhaps I am used to that.
- In my test drive I created a view just for printing a list of transactions. Because of that, I would like to not only hide the toolbar, since the list should be printed just as it is - no other sorting or whatever - but also the New+ button, since here in this print layout no editing is wanted. Furthermore my example list is a transaction list of bank transactions - it should only allow importing of data, no manual editing of existing or adding of data at all. You can´t change your bank account by just adding a million dollars yourself :-)
- If I have designed a report - lets stay with the banking transactions - it may make no sense if the user has all rights to change the settings. If the transactions are a chronological ledger, I don´t want any other sorting. A transaction list with the currency value column hidden, makes no sense. If the sorting is by date, the date field should stay at the beginning. Sadly currently grouping is not printed - voted for that. If I have incorporated grouping I really want to keep this in a report for example.
As to my experience "simple" users have quicker destroyed a solution than you can watch them clicking ... so you have to prohibit many things to be safe for support.
Peter Novosel
under review
Permissions can be applied to Folders that contain views, effectively giving you this capability (a folder could potentially contain just a single view if so required).
I'm going to leave this under review, however, as we're still looking at the application of permissions directly to the views themselves.
Vasken Bakalian
Brian Dollen this one needs a status update, no?
J
Jeff Parsons
So is there any progress on this? Permissions are so robust in SmartSuite I was honestly surprised this is not already in place, as it seemed like an intuitive feature. I'm also running into use cases where this would be very handy. Yes, there are some work arounds, but this would simply things.
Emma Montgomery
Merged in a post:
Permissions on Views
P
Patrick
With the assigned to permissions we have many clients operating in one space.
We also have our staff operating in that same space. Our staff has hidden fields which don't show in the views, but All views show. It would be nice to not show all views.
One good example would be in an application if each client needed a form- that can easily be done, but all those forms would sit in a folder and be viewable.
I believe even if they were private or other member views? and even if private views were not viewable by assigned to permission levels to have staff have to look through each others private views isn't ideal.
The workaround found so far is using dashboards and putting grid views in there which can be in a separate solution. However Dashboard do not operate on mobile.
Open to solutions
Cheyenne at MassiveReach
Looks like we have several that can merge this request in too https://smartsuite.canny.io/feature-requests/p/permissions-on-views
Cheyenne at MassiveReach
Finding this to be a glaring issue with setting up our agency flow. We definitely need to be able to permission out the views or it looks really sloppy. I can do private... but then can't share that with internal team.
I'm afraid this will force us into a Solution per Client... which feels like treading water backwards from keeping similar processes all together.
K
Konstantin Skorodumov
Hiding of Views segmented by the field value (client, warehouse, and so on) could be a nice feature:
If I set some Views with filters by clients - one for each client, I'd like to have the possibility to hide other Views from a particular Client Abc, to not give him to open and view other Views (Xyz, Fds) as well.
Load More
→