How to restrict access rights within the Assets confluence plug-in

[Johan Eltes]

I want to use the Assets confluence plug-in to allow any employee with confluence access to view data rendered by the plug-.in, but not to edit the plug-in on a page. Only JIRA users with Service management privileges should be able to configure the plug-in on a confluence page. With our current set-up anyone who can view the content rendered by the plug-in can change and save the plug-in configuration, regardless of whether you have edit rights on the wiki page hosting the plug-in. Even if you had write access to the hosting page I don't want none-Service management users to be able to alter the configuration of a plugin configuration on any hosting confluence page. Any guidance on how this can be achieved would be greatly appreciated. Thanks.

[Kris Dewachter]

Hi @Johan Eltes ,

The easiest solution would probably be to set "Restrictions" on that specific page.

https://support.atlassian.com/confluence-cloud/docs/add-or-remove-page-restrictions/

That way, you can define who is able to edit the page, and who is able to read-only.

Best regards,

Kris

[Johan Eltes]

Thanks for the suggestion! It may work in settings different from ours. Everyone should be able to edit the page. We have a company policy for the concerned space set to all may view and edit, so that option is not available. This is also not something we would like to do. We would like a plug.-in that is a content plug-in following the semantics of other content plug-ins, so that the config of the plug-in (schema, AQL, attributes etc) are set in edit mode of the page, and that the plgu-in just renders content in the page view mode. But I do now realize that the idea of this plug-in is to plu-in the application itself rather than the data. I think it kind of breaks the idea of a wiki by introducing the idea of a wiki morphing into an application portal.