How can I limit access to a project to certain add-ons?

[Jevgeni Võssotski]

As far as I understand, every installed Atlassian Connect application (add-ons) is granted a special role "atlassian-addons-project-access". Through this role, project permissions can be configured, enabling a set for authorized actions for all installed add-ons. What we'd like to find out is whether this configuration could be more specific about what add-ons can access what projects. 

Let's imagine we have two Jira projects P1 and P2, and let's say we want to use 2 add-ons A and B, that both have authorization scope allowing them to edit issues.

Can I limit the the access for add-on A only to issues of project P1, while I still need the add-on B to access both projects P1 and P2?

[Bharat Kalia]

@Joe Pitt - Is this still the same? We are looking to install "OKR board for Jira" but I just want to restrict it's access to some projects? Are we able to do that?

Thanks,

Bharat

[Joe Pitt]

Yes. the plugin must support it. 

[Joe Pitt]

This has been asked before. The specific add-on/plugin must support level of authorization.