Custom user role creation for more granular permissions control
F
Francesco B.
There are only 6 roles available. However, I would like to be able to break it out more granularly. For example be able to create a role that can create/update/flag documentation, but not share. Allowing custom role creations would likely satisfy a few feature quests here by getting the permissions broken down more granularly and allowing us to choose which permission get applied to the custom role.
Jürgen Van Meerhaeghe
This is a dealbreaker for us. The external portal is useless for us since we have to give every employee admin access to add assets to the external portal?
J
Jay V.
To add to this, I think having the option to have admin which are restricted to a company would be helpful. Which would allow them to create assets/list only for that company and export data for bulk edits.
Kristen W.
Merged in a post:
Roll editing
F
Felix B.
It would be nice if you could edit the roles.
For example, we would need the ability to give an editor the delete rights.
Kristen W.
Merged in a post:
User Role Permissions
P
Peter F
Allow Editor Role to delete and create all items for their company (passwords, kb, create folders, delete folders, etc). The Author role can only have write role permission.
That way an Editor can be a 'local admin' for their company OR allow for Admin role to be added to a group.
We need a 'company' Admin with full permissions to overview company documentation. Super Admin keeps access to All.
Kristen W.
Merged in a post:
Customizable Permissions for User Accounts
R
Rob R.
We would like to give our help desk engineers the ability to "flag" out of date documentation, but not actually update it themselves. Currently, this is not possible as you have to have write ability in order to flag. Seems like an easy change that could be useful for MSP's concerned with ensuring documentation accuracy.
T
Taylor A.
I would like users to be able to move synced cards without having to be an admin!
T
Tanner M.
This is a large hurdle we are having to work around right now for our Hudu implementation. For a engineer to be able to create assets, but also be able to retire the entire company doesn't make sense. If I want to give someone the ability to search for assets globally, I also have to give them the ability to change security permissions, edit integration settings, setup API access, etc.
P
Paul s. G.
We have discovered that normal users can't duplicate assets. We'd like to do that because we try to have rich and consistent documentation for assets.
You shouldn't need to have full admin (able to delete content) just to duplicate an existing record.
Similarly, creating sharing links shouldn't be tied to some of the advanced permission groups.
More granular permissions would be greatly appreciated.
P
Paul s. G.
Agreed.
Specifically we'd like to see control granting asset duplication and folder creation without the actual Admin role. Sorry, no deleting, just creating.
We've got techs who are expected to create and maintain documentation and it seems obvious for the people who design the structure of our stuff to create templates for techs to clone and adjust to specifics.
Part of this is that we're not using the native assets for a couple things because we want additional values in them. It would be really nice to be able to let techs duplicate assets that have time-consuming structure.
A
Adam G.
I can't believe that more people are not requesting this. We would like to get technicians the ability to share passwords in the portal but not have access to some passwords that our leadership team has. We would also like to give bulk edit permissions to users.
Load More
→