Is it possible to prevent unauthorized structure changes in R4J?

[Manuel Hernandez]

I would like to know if there is a way to lock or manage permissions to modify the structure in R4J. I faced a situation where a colleague created a new folder in a place where it was not intended to be, so it would be helpful if this kind of modification required approval before being applied. The goal may not be to protect the entire structure, but at least certain parts of the project should be restricted.

Any ideas are welcome :)

[Halina Cudakiewicz_Deviniti_]

Hi @Manuel Hernandez 

R4J doesn't offer approval workflows or fine-grained permissions for modifying the structure. Access control is handled at a high level through Jira and R4J project permissions, which means users who can edit the structure can do so anywhere within the project.

If only certain parts of the hierarchy need protection, a practical workaround is to separate them into a dedicated R4J project. The “core” or governed structure can then be restricted to a small group of editors, while less critical content lives in a separate, more flexible R4J project. This adds some overhead, but it is the most reliable way to prevent unintended structural changes in sensitive areas.

Hope this helps!