Connect your GitHub account

Connecting GitHub to your Streamlit Community Cloud account allows you to deploy apps directly from the files you store in your repos. It also lets the system check for updates to those files and automatically update your app. There are two stages to this authorization: the first happens when you connect your account for the first time and the second happens when you deploy your first app.

Everyone is prompted to connect GitHub when they create an account. If you need to connect GitHub to an existing primary identity, see Manage your GitHub connection.

This page contains additional information about the authorization needed to connect GitHub. If you have just created your account, you are free to skip ahead and Explore your workspace. GitHub's authorization prompts occur automatically as needed.

There are two different authorization prompts to grant access between Streamlit and your GitHub account. The first authorization—"Authorize Streamlit"—happens when you connect your GitHub account to Streamlit. The second authorization—"Streamlit is requesting additional permissions"—happens when you deploy your first app. You must click "Authorize streamlit" on both. If you are a member of any GitHub organizations, read below to understand the extras steps to authorize an organization. Questions about GitHub permissions? Read some frequently asked questions about our GitHub integration.

Authorize your GitHub account
priority_high

Important

You must have admin permissions to your repo in order to deploy apps. If you don't have admin access, talk to the repo's owner or reach out to us on the Community forum.

If you are working in a repository that is owned by an organization, authorization must be granted by that organization. If you are an owner or member of a GitHub organization when you connect your GitHub account, your authorization prompts will include an extra section labeled "Organization access".

For any organization you own, if authorization has not been previously granted or denied you can click "Grant" before you click "Authorize streamlit".

Authorize your Streamlit on a GitHub organization you own

For an organization you don't own, if authorization has not been previously granted or denied you can click "Request" before you click "Authorize streamlit".

Authorize your Streamlit on a GitHub organization owned by others

If someone has already started the process of authorizing Streamlit for your organization, different options and statuses will display accordingly.

Approved access

If an organization has already granted Streamlit access, a green check is shown.

Approved authorization for Streamlit on an organization

Pending access

If a request has been previously sent but not yet approved, a pending status shows.

Pending authorization for Streamlit on an organization

Denied access

If a request has been previously sent and denied, no option to grant or request access is shown. In this case, the organization owner will need to authorize Streamlit from GitHub. See GitHub's documentation on OAuth apps and organizations.

Denied authorization for Streamlit on an organization

Now that you have your account you can Explore your workspace. Or if you're ready to go, jump right in and Deploy your app.

forum

Still have questions?

Our forums are full of helpful information and Streamlit experts.