> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/code-scanning/connect-your-source-code/connect-github-enterprise/transferring-ownership-of-the-aikido-app-in-github-enterprise.md).
# Transferring Ownership of the Aikido App in Github Enterprise (Cloud & Server)
When you create the Aikido GitHub App inside your GitHub Enterprise environment, it is set up under the account of the user performing the installation. This follows the default GitHub flow when no prior ownership choice is known.
You can transfer the app to any other user or organization in your GitHub Enterprise Server environment at any time. This has no impact on how the app operates.
To transfer ownership, follow the steps below.
{% stepper %}
{% step %}
**Go to the Github App's developer Settings page**
In your GitHub Server environment, navigate to Settings > Developer Settings > GitHub Apps.\
Click on "Edit".
{% endstep %}
{% step %}
**Go to Advanced settings**
In the left-hand navigation, go to the "Advanced" settings and scroll all the way down on the page until you see this section.\
\
Click on "Transfer ownership"
{% endstep %}
{% step %}
**Transfer ownership**
Once you've clicked the button, you need to confirm the name of the App, and then you can select the organization or user to which you want to transfer the ownership.
{% endstep %}
{% step %}
**Success**
The App is now transferred to the new owner.
{% endstep %}
{% endstepper %}
---
# 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://help.aikido.dev/code-scanning/connect-your-source-code/connect-github-enterprise/transferring-ownership-of-the-aikido-app-in-github-enterprise.md?ask=&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.
