Authenticating as a {% data variables.product.prodname_github_app %} lets you do a couple of things:

For example, you would authenticate as a {% data variables.product.prodname_github_app %} to retrieve a list of the accounts (organization and personal) that have installed your app. But this authentication method doesn't allow you to do much with the API. To access a repository's data and perform operations on behalf of the installation, you need to authenticate as an installation. To do that, you'll need to authenticate as a {% data variables.product.prodname_github_app %} first to request an installation access token. For more information, see "[AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/about-authentication-with-a-github-app)."

This method accepts two arguments:

Any time a {% data variables.product.prodname_github_app %} receives a webhook, it includes an `installation` object with an `id`. Using the client authenticated as a {% data variables.product.prodname_github_app %}, you pass this ID to the `create_app_installation_access_token` method to generate an access token for each installation. Since you're not passing any options to the method, the options default to an empty hash. The response for `create_app_installation_access_token` includes two fields: `token` and `expired_at`. The template code selects the token in the response and initializes an installation client.

- If you choose **JetBrains Gateway**, the Gateway application will automatically open when you next create or open a codespace.

The first time you open a codespace this way you must give permission to open the application.

1. Click **Save**.

1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see:

{% note %}

If you must use footnotes:

When referring to the product {% data variables.product.prodname_codespaces %}, always include "{% data variables.product.company_short %}", except in these circumstances:

Variables: `{% raw %}{% data variables.product.prodname_github_codespaces %}{% endraw %}` ("GitHub Codespaces") and `{% raw %}{% data variables.product.prodname_codespaces %}{% endraw %}` ("Codespaces").

For tables that use symbols:

Where table data is not truly binary (every value is either "Yes" or "No", for example), text values may be needed in addition to, or instead of, symbols. For example on the page "[AUTOTITLE](/support/learning-about-github-support/about-github-support)", some features are marked as "Available to purchase".

**Notes:**

{% endnote %}

Once you have started editing your tasklist Markdown, you can add new tasks by preceding each new task with `- [ ] ` and then adding either:

If you add a draft task, it must meet these requirements:

Your tasklist will be rendered by {% data variables.product.product_name %} when you preview your changes and when you save the issue. You can then make changes and add issues and draft tasks using the {% data variables.product.product_name %} UI. If you edit the issue description, you will be able to modify the Markdown directly or copy the Markdown to duplicate the tasklist in other issues.

1. Add your draft task, issue, or pull request.


1. Using the context menu, make your changes.

You can move tasks within a tasklist and move tasks to other tasklists in the same issue.

1. Hover your cursor to the left of the task you want to move until a {% octicon "grabber" aria-hidden="true" %} drag handle appears.

1. Click on the {% octicon "grabber" aria-hidden="true" %} drag handle and drag the task to the new destination.

1. In your project, click on an issue that either contains a tasklist or is tracked by a tasklist in another issue.

1. In the issue that opens in the side-bar, you can navigate through the associated issues.



**Notes:**

{% endnote %}