Announcements
Notice: Upload of PDF documents is currently unavailable across the Community due to an ongoing issue.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Hide attachments files in Thin Client (and on ITEM level)

Hide attachments files in Thin Client (and on ITEM level)

Hello.

 

It would be great to be able to hide attachments files in Thin Client (and on ITEM level).

 

Currently users do not have permission to "download" those files, so they cannot download and open them.

We know that permissions can be set "read disabled" that they will not be seen, but the problem is that permissions are set from ITEM level and "read" is needed otherwise users will not see the ITEM and their DWF files.

 

On FILE level "hiding" files exist.

 

ReneRepina_2-1789477765681.png

 

ReneRepina_3-1789477803675.png

 

 

Best regards,

Rene Repina

7 Comments
ihayesjr
Community Manager

@ReneRepina

Do you have lifecycle states on these files at the file level?

ReneRepina
Collaborator

@ihayesjr 

Yes, but they are controlled with their ITEM, which also contains their source files. So regardless what is on FILE level, ITEM overrides them.

ihayesjr
Community Manager

@ReneRepina 

Are you saying that the Item Lifecycle state overrides the security of the file-level lifecycle state? If so, why?

ReneRepina
Collaborator

@ihayesjr 

Of course.

Well the ITEM is a container of all data / files we need and we lock/unlock them together when there is a need of the change.

Otherwise we would need to lock/unlock all files separately.

Or what do you suggest it should be handled?

ihayesjr
Community Manager

@ReneRepina 

Ok, it sounds like you are not using file lifecycle states. Correct?

You are only using Item lifecycle states and applying security to the file via the Item lifecycle state. Correct?

ihayesjr
Community Manager

@ReneRepina 

In other words, you have checked the box "Security for associated files of items".

ihayesjr_0-1790012591337.png

 

ReneRepina
Collaborator

@ihayesjr 

We have a lifecycle for files (but it is just 1 state), after that, ITEM is used to control permissions on those files (yes that option you sent the image).

 

I know that we could not attach them to ITEM and use FILE level, but those files need to be connected to those source files.

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea