RELATED IDEAS
Add inriver permissions for Shared Workareas
Hi inriver,
We and multiple customers would be very happy if you can implement additional permissions related to "Shared work areas". Currently all inriver users can update or delete "Shared work areas" and there is no way to restore them after someone accidently deletes or updates a "Shared work area".
Please add the following permissions:
- AddSharedWorkareas
- UpdateSharedWorkareas
- DeleteSharedWorkareas
Thanks.
Kind regards,
Simon
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +98
86
MERGED
Protecting shared queries / work areas | Lock work area folders
Since queries can be used for many things such as channel rules, link rules and syndication it is important to be able to protect them from being edited or deleted. There should either be a way of locking a query or to introduce a system query (wo...
1
Likely to implement
Very important to secure data quality in downstream systems since channel nodes are configured using shared workareas and queries. For syndications, we also rely on this to choose product assortment for different endpoints. If users by mistake destroy a specific query or workarea, this can have hughe impact on customer experience.
In addition to this we have many custom functions (like notifications to users) that rely on workareas and queries that must be fulfilled to trigger a specific event.
From our point of view it would be good if Administrator users can lock certain workareas and queries for modification while the users are still able to use them. So, it´s not about restricting everything but instead being able to be selective as an Administrator. All workareas and queries does not contain business critical logic while some do.
We urgently need this included as soon as possible. It's critical to secure the system for users who only need read-only access, ensuring they cannot modify any data. If a user with the InRiverEnrich permission updates a Shared Workarea, it could disrupt all Syndications, causing significant issues.
Please reconsider this functionality!
Ideas merged - Add inriver permissions for Shared Workareas (this entry) and Protecting shared queries / work areas | Lock work area folders.
Agree with Rutger - the two tickets seem to be the same. However, as this seems to be "Likely to implement", I will copy my comment from the other ticket:
This is critical in regards to Workflows and multi-tenant solutions. If you put all of your Workflow-queries into a separat "folder" in the Work area, and someone by accident deletes the folder - all of your workflows stop working.
Considering the amount of effort needed to build and implement workflows into an organization, the missing ability to secure your Workflow-queries is a dealbreaker. We cannot realistically sell this to our clients, without any means of restricting, securing or restoring the Workflow-queries.
@inriver team: could this be merged with this idea?
https://partnercommunity.ideas.aha.io/ideas/ENR-I-4