Accepting new permissions for the GitHub OpsLevel application
As part of new feature rollouts at OpsLevel, we may occasionally request new permissions for the OpsLevel GitHub application.
After that, you will receive a notification via email, and visible in the Installed GitHub applications listing for your organization, requesting you accept the updated permissions.
A note will be attached to the notification informing you why we are requesting the changes.
Accepting Changes
GitHub will send emails to organization administrators when an application requests changes. An example of this is below – we have redacted the Organization name and installation ID as these will be dependent on your organization.
An alternative way to view the request is to go to your GitHub organization settings and select “GitHub Apps” under “Integrations”.
This will take you to the Installed GitHub Application listing, where you will see the OpsLevel application requesting new permissions
Whichever path you choose, you will end up on the following page showing the changes in permissions and a note from OpsLevel with a link to further details:
When you are satisfied with the new permissions, you will be taken to the existing Application page with a banner indicating the changes were applied.
Latest Update to Permissions
- Administration (Read/Write) - To allow OpsLevel to initialize services directly, we need to be able to create repositories within your organization.
- Pull Requests (Read/Write) - To allow OpsLevel to create updates to current service repositories (e.g., when service templates change over time)