Skip to main content
Solved

Deletion of Shared Content

  • March 18, 2026
  • 1 reply
  • 30 views

Forum|alt.badge.img

We recently upgraded to TrendMiner 2025.R3.0-15 and noticed that users with access to shared content can also delete it.

In our previous PI Vision setup, deletion was typically restricted to higher-level accounts. Is it possible in TrendMiner to limit deletion rights to specific roles while still allowing broader create/edit access?

Also, are there recommended best practices (permissions, folder structure, etc.) to prevent accidental deletion of shared content?

Best answer by fvandael

Hi ​@uachegraduate 

 

The reason users can delete shared content comes down to which permission level was assigned when the content was shared. In TrendMiner, deletion rights are not controlled by application roles - they are determined at the individual share level. If users have Manage permission, they can delete. It has nothing to do with whether they are a standard User or an Application Administrator.

Here is how the three permission levels break down:

Permission View Edit Delete / Move / Rename
Read Yes No No
Write Yes Yes No
Manage Yes Yes Yes

 

Write permission allows users to open and edit work items, but explicitly prevents deleting, moving, or renaming folders and items. Source So for most users, Write is the right level - it covers everything they need for day-to-day work without exposing deletion rights.

To get your setup aligned with what you had in PI Vision, a few things are worth doing:

  • Audit your current shares and downgrade users from Manage to Write where deletion rights are not needed.
  • Create a dedicated folder structure for official shared content and share it at the folder level with Write. Permissions cascade down, so you only need to configure it once.
  • Reserve Manage permission for a small group of trusted content owners who are responsible for maintaining the folder structure.
  • For content that should be view-only for everyone, sharing with "Everyone" restricts access to Read permission only. Source

That combination of Write for general users and Manage for a dedicated owners group should give you the same kind of controlled environment you were used to before.

Kind regards

Frederik

1 reply

Forum|alt.badge.img
  • Employee
  • Answer
  • March 19, 2026

Hi ​@uachegraduate 

 

The reason users can delete shared content comes down to which permission level was assigned when the content was shared. In TrendMiner, deletion rights are not controlled by application roles - they are determined at the individual share level. If users have Manage permission, they can delete. It has nothing to do with whether they are a standard User or an Application Administrator.

Here is how the three permission levels break down:

Permission View Edit Delete / Move / Rename
Read Yes No No
Write Yes Yes No
Manage Yes Yes Yes

 

Write permission allows users to open and edit work items, but explicitly prevents deleting, moving, or renaming folders and items. Source So for most users, Write is the right level - it covers everything they need for day-to-day work without exposing deletion rights.

To get your setup aligned with what you had in PI Vision, a few things are worth doing:

  • Audit your current shares and downgrade users from Manage to Write where deletion rights are not needed.
  • Create a dedicated folder structure for official shared content and share it at the folder level with Write. Permissions cascade down, so you only need to configure it once.
  • Reserve Manage permission for a small group of trusted content owners who are responsible for maintaining the folder structure.
  • For content that should be view-only for everyone, sharing with "Everyone" restricts access to Read permission only. Source

That combination of Write for general users and Manage for a dedicated owners group should give you the same kind of controlled environment you were used to before.

Kind regards

Frederik