Allow users to set Service Dependencies of dependencies that their team does not "own"

Current Behavior

Business Services, and Technical Services, allow the linking of Service Dependencies that a team owns. Dependencies can only be linked if a user has proper permissions to edit that dependency.

Use Case

Our business practices a decentralized structure where each team is free to act independently of another. However, these teams own technical services that may be dependent on a different technical service owned by a different team. As such, they want to have that visibility when an upstream dependency is experiencing issues.

Teams want to be able to set Service Dependencies from other teams without needing high-level permissions either globally, or on any team that they do not belong.

So far, we’ve had to let our PagerDuty administrators be the ones to link these dependencies, which is a bottleneck to our users.

Feature Request

A permission level, or scheme, that allows users to set Service Dependencies from any team that they are not part of so that they can fully model their dependencies within their Business Service without having an overkill of other permissions.

More specifically, I want to be able to grant a user permissions that allow them to set Service Dependencies from dependencies that their team does not own.

2 Likes