Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review Azure Devops permissions #10252

Open
ackernaut opened this issue Sep 18, 2024 · 1 comment
Open

Review Azure Devops permissions #10252

ackernaut opened this issue Sep 18, 2024 · 1 comment
Labels

Comments

@ackernaut
Copy link
Member

ackernaut commented Sep 18, 2024

A user 🔒 wrote in:

We are trying to do an ADO integration for running Sprint Planning sessions. ADO is managed by the company and the Scrum Masters are provided admin rights only to certain projects. Due to this constraint, we are not able to integrate Parabol with ADO, and it prevents us from bringing User Stories in for Sprint Poker.

Is it possible to change the permissions so that a user doesn’t need admin rights to add the integration for use with Sprint Poker?

Would this be appropriate from a security standpoint? Do we have any options here?

@Dschoordsch
Copy link
Contributor

I assume this is a limitation of how we publish this integration. Because each client needs to add a custom app to their ADO organization, the setup needs admin rights.
I'm not deep enough in the ADO world to be sure, but I would assume that if we would publish a proper app in the ADO marketplace, that this could reduce the necessary permissions to set it up (unless their admin forbids running apps in general).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

2 participants