> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/risk-management/threat-model-coverage/shadow-apps/github-playbooks-for-shadow-apps.md).

# GitHub playbooks for shadow apps

To mitigate the risk associated with shadow apps in GitHub, you can define automated workflows for these use cases: 

## Notify on GitHub app installation

When someone installs a GitHub app on your organizational GitHub, the Security Ops team is automatically notified by email.

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to shadow apps, and select the **Notify on GitHub app installation** playbook. 
3. Give an action name.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FUpAk1BwMzXjgavnrUPqW%2FIT%20playbook%20GitHub.png?alt=media&amp;token=19f36516-51fa-4120-a2fb-8fce6933375a" alt=""><figcaption></figcaption></figure>
4. Under the **GitHub app installation** event, define the condition:\
   `Get repository selection` contains `all`
5. Add any relevant conditions.
6. Customize the **Notify by email** step to send an email to the Security Ops team, notifying them that:\
   `A new app was installed on the org-wide GitHub.` \
   `App name is: <app name>.`

   `This app has access to all repositories.`

   `You can visit the app installation here: <link>.`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docontrol.io/docontrol-user-guide/risk-management/threat-model-coverage/shadow-apps/github-playbooks-for-shadow-apps.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.