I want to provide a folder where files are accessed by our authors, but they cannot modify (write-to) the files that are in it. We've had issues with modifications being made to our keydef files and we want to limit who can modify these files.
I was informed by SDL support that this is possible, but I'm not sure how to get started.
Hi, a follow-up question to this old thread. Is it possible to set folder "owners" and "read access" for existing folders using IshRemote?
Hi Pia,
The user interface, like Organize Space, and in turn API all share the same business logic.
So in the user interface you can change the "read access", and that is what you can also do in ISHRemote Set-IShFolder cmdlet.
The "owner" however comes with more complicated rules and cannot be done in one-stop. Depending on your security setup, you As Administrator, can set up a new folder with new owner setup and then you can move objects into that new folder. If that holds the desired results, you can automate that using the cmdlets Move-IShFolder and Move-IShDocumentObj.
As always, better to experiment on a TEST environment before moving your repository items around in an automated way.
Best wishes,
Dave
Hi Pia,
The user interface, like Organize Space, and in turn API all share the same business logic.
So in the user interface you can change the "read access", and that is what you can also do in ISHRemote Set-IShFolder cmdlet.
The "owner" however comes with more complicated rules and cannot be done in one-stop. Depending on your security setup, you As Administrator, can set up a new folder with new owner setup and then you can move objects into that new folder. If that holds the desired results, you can automate that using the cmdlets Move-IShFolder and Move-IShDocumentObj.
As always, better to experiment on a TEST environment before moving your repository items around in an automated way.
Best wishes,
Dave
Thanks for clarifying Dave! Will will definitely test first, if we even decide that it is worth the effort.
Translate
