Would this be based on the permissions that the user has on the project? For example, if the configuration of the link specifies WRITE permission, then the plugin would show the link only to those users who have WRITE permission on the project.
Alternatively, I imagine the Sidebar Link plugin could define a READ_SIDEBAR_LINK permission, and you could then grant users that permission on projects. However, if you added multiple sidebar links to the same project, then a user would see either all of them or none of them.
Or, do you mean each link should have an access control list? That seems it would be more difficult to implement. AuthorizationStrategy (javadoc) supports ACLs on various things but not on properties of projects.
Would this be based on the permissions that the user has on the project? For example, if the configuration of the link specifies WRITE permission, then the plugin would show the link only to those users who have WRITE permission on the project.
Alternatively, I imagine the Sidebar Link plugin could define a READ_SIDEBAR_LINK permission, and you could then grant users that permission on projects. However, if you added multiple sidebar links to the same project, then a user would see either all of them or none of them.
Or, do you mean each link should have an access control list? That seems it would be more difficult to implement. AuthorizationStrategy (javadoc) supports ACLs on various things but not on properties of projects.