Lock down integration templates

• ADMIN RESPONSE

  Jun 20, 2019

  Thanks for the idea!

  A workaround would be to limit access to the product where the the template integration lives. If you want a user to be able to select the template from their own product settings but not edit the template itself, you need to change their role to the product where the template lives to either contributor, reviewer, or viewer.

  As this workaround exists today, we are unlikely to implement this additional lock down approach at this time. However, we will continue to monitor this idea for community feedback and company goal alignment.

• Comments 1
• Votes 15
• Merged ideas 1

Add a comment
• Attach files

  Enter a subject
• 
  Guest

  Reply

  | Jun 20, 2019

  I agree that the current method is not sustainable.  One individual not following instructions is able to bring down the integrations Enterprise wide.  If the majority of users that currently have PO licenses are changed to contributors they will only lose the ability to create new products or change the integration.then we could allow select people from each Alliance to retain PO licenses so that they may assist in the integrations so they do not all have to go through the Admins.  

  0 reply Hide replies

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

2 MERGED

Need ability to lock down "Configure Account" page for Aha/JIRA integrations

Merged

We have almost 200 integrations based on 1 template. Users are going in and mistakenly modifying the template which is causing for all integrations to break at an enterprise level. We have attempted to limit the number of Product Owners in the too...

Cindy Datlof over 5 years ago in Jira 0 Unlikely to implement