Skip to Main Content
Status Likely to implement
Created by Guest
Created on Sep 16, 2019
Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit INSE-I-54 Add inriver permissions for Shared Workareas.

Protecting shared queries / work areas | Lock work area folders Merged

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 (work area) type.


Originates from Community:
https://community.inriver.com/hc/en-us/community/posts/360005130359-Protecting-shared-queries-work-areas-Lock-work-area-folders

Thomas Sjöberg

  • September 17, 2019 04:53

request #50156

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 (work area) type.

77

Comments

9 comments

Sort by

  • official commentThomas Sjöberg

    • September 27, 2019 12:16

    This will be the main post, the other duplicate will be removed in a week. Please vote and comment on this.

  • Dennie Ovenberger (ICP)

    • September 24, 2019 14:57

    Yes! This! I'm having a syndication demo on monday. All worked well. Managed to delete my only workarea. Now nothing works.

    Either have the posibility to have a new Workarea with System searches, where only some roles have access. Or have access control on each Workarea, so you can create trees that are available to all, but only editable/deletable by some.

    This are is very much in need of update.

    1

  • Mathieu Kittel Hudon

    • September 26, 2019 14:00

    We also create template queries that are save in the Common Shared folder for enabling each role/user to access the products in the different steps of the lifecycle workflow.

    We want users to be able to use these queries, adjust some conditions and save them to their personal folder, but not update/overwrite the template query from the Common Shared folder.

    5

  • Jeremy Peterson (ICP) inriver champion

    • September 26, 2019 16:30

    This is very similar to this other thread which already has votes and comments. Can these be combined?

    https://servicecenter.inriver.com/hc/en-us/community/posts/360005544700-General-Lock-workarea-folders

    2

  • Galina Melnick

    • February 25, 2020 20:56

    This would be a good idea.

    3

  • Andrea Hughes

    • March 31, 2020 19:11

    We at New Balance would also like to request tighter restrictions on common share folders and queries. Today we reported to InRiver that we had a user accidentally delete a common share folder - containing subfolders and 15+ queries...by accident. It is good to know that InRiver can restore them, but it would ideal if there was a way to prevent accidental deletions since so many other things are tied to those queries. We had a lot of confused users today...looking for the common shared folder that had suddenly disappeared.

    If there are any updates as to when a change may be implemented to protect common shared queries and folders, that would be very much appreciated.

    Thank you,

    Andrea

    2

  • Bruce Leduc

    • April 24, 2020 15:27

    This will be really appreciated on Moet Hennessy side as well.

    Thanks

    Bruce

    2

  • Steven Mann

    • May 12, 2020 17:05

    One of our largest clients has requested the need for this as well. Will this be on the roadmap?

    2

  • Beth Ryan

    • June 23, 2023 17:40

    This would be great

    0


  • Guest
    Reply
    |
    Sep 26, 2024

    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.

  • +77