Reauthorizing and Disconnecting Git Integrations

Checking whether your Git connection needs reauthorization

In Atloria, start from the project workspace and open the area where the project’s Git connection is shown. This is the same project-level connection area you used when reviewing connection health in Reviewing Git Connection Status and Access Health. Look for the connected provider name first so you can confirm whether the project is linked to the expected Git account and source.

If the project already has a Git provider connected, Atloria shows that provider in the source connection section along with its current status. A healthy connection appears as connected. A connection that needs attention is typically shown as expired, invalid, disconnected, or with a prompt such as Reauthorize, Reconnect, or a similar action. If you see one of those prompts beside the current provider, Atloria is telling you that the project remembers the connection, but access is no longer valid.

This is different from a project that has never been connected. If there is no provider listed and no existing connection details, you are not reauthorizing an expired connection—you are dealing with a project that does not currently have a Git source linked at all.

Before you change anything, review what this project depends on. If the project uses a selected repository, a branch, or source-based update actions, those workflows rely on the current Git connection being active. Reauthorizing usually restores those actions. Disconnecting stops Atloria from using that linked source for the project.

Confirming you can update the project's source connection

Before you click Reauthorize or Disconnect, make sure you are signed in with the right Atloria access level for this project. You need Project Administrator access to manage the project’s Git integration settings. If you can open the project settings area but do not see controls for changing the source connection, your access may be limited, or the page may still be loading the current connection details.

Next, confirm which Git provider account you intend to use. This matters most when you have more than one provider account signed in within the same browser. During reauthorization, the provider’s sign-in or consent screen may automatically pick the account already active in that browser tab. If that is the wrong one, Atloria may reconnect the project to an account that does not have access to the repository you expect.

It also helps to review the project’s current source details before making changes. Check whether the project is tied to a specific repository and branch. If you disconnect the provider, repository-based actions in that project can stop until the connection is restored or replaced. If you are only refreshing access for the same account, those settings usually remain in place, but you should still note them before proceeding.

When you are ready, expect Atloria to open a provider approval screen, a pop-up window, or a redirect page outside the project workspace. That external step is where you confirm access for Atloria. Keep the Atloria project tab open so you can return and verify the result immediately after approval.

• Confirm you are in the correct project.
• Confirm you have Project Administrator access.
• Confirm which Git account should be used.
• Review the current repository and branch details before changing the connection.

Reauthorizing an expired Git provider connection

1. Open the project’s Git integration settings and find the connected provider shown for the project. If Atloria marks the connection as expired, invalid, or disconnected, click Reauthorize, Reconnect, or the similar action displayed next to that provider.

2. Atloria sends you to the provider’s approval screen. If the provider asks you to sign in, choose the account that should manage this project’s repository access. If more than one account appears, take a moment to verify you are selecting the one that already has access to the repository used by this project.

3. Review the access request on the provider screen and approve it so Atloria can regain repository access. Complete every step in that flow until you are returned to Atloria. If you close the provider window too early, Atloria may continue to show the connection as expired.

4. After you return to Atloria, go back to the project’s source connection area and check the status again. The provider should now show as connected rather than expired or disconnected. If the page still shows the old state, refresh the page once and review the status again.

5. Finally, confirm that the project still points to the expected repository and branch. Reauthorization is meant to restore access to the existing connection, not create a brand-new setup. If the provider is connected but the repository details no longer match what the project should use, review the source settings before continuing with repository-based work.

If you need help recognizing the normal connected state after this step, refer back to Reviewing Git Connection Status and Access Health.

Disconnecting a Git provider without losing track of project impact

1. Open the project’s source connection settings in Atloria and locate the current provider. To remove the link safely, use the Disconnect, Remove connection, or similar action shown in Atloria. Start here rather than removing access only from the provider side first, because Atloria’s own disconnect action updates the project record and makes the change visible in the project workspace.

2. Read the confirmation message carefully before you continue. Atloria may warn that disconnecting the provider will stop repository access and source-based actions for this project. This is the point to pause and confirm whether anyone on your team is currently relying on repository-linked work in the same project.

3. Confirm the disconnect action. Once the provider is removed, Atloria updates the project from a connected source state to a disconnected state. The provider name may disappear from the active connection area, or the status may change to show that no active Git connection is available.

4. After disconnecting, review the project workspace so you understand what changed. Existing project content, documentation records, and previously created project items remain in Atloria. What stops working is the live link to the repository. Any action that depends on Atloria reaching the connected Git source will remain unavailable until you reconnect a provider or set up a new source connection.

Use disconnect when you intentionally want to remove the project’s current Git link. If your goal is only to refresh expired access, reauthorization is usually the better choice because it keeps the same project connection in place.

Understanding what changes at the project level after reauthorizing or disconnecting

Reauthorizing and disconnecting may look similar because both start in the project’s Git connection area, but they affect the project very differently.

When you reauthorize the same provider connection, Atloria restores access to the repository that was already linked to the project. In most cases, this means the project keeps its existing source setup, including the selected repository and branch. You are not starting over—you are renewing Atloria’s permission to use the connection that the project already knows about.

Disconnecting does the opposite. It breaks the active link between the project and its Git provider. After that, Atloria still keeps the project itself and its existing documentation records, but repository-backed actions for that project stop because there is no longer an approved source connection behind them.

If you reconnect using a different provider account, review the source details carefully. Even if the provider name is the same, a different account may not have access to the same repository, or it may expose a different set of repositories and branches. After reconnecting with a different account, check that the project still points to the correct repository and branch before resuming source-based work.

A helpful way to think about it is:

If you are unsure whether you need a simple access refresh or a full replacement of the project’s source connection, compare the current connection state first and then decide which action matches your goal.

Fixing common problems with reauthorization and disconnecting

If you complete the provider approval flow and Atloria still shows the connection as expired, start by refreshing the project integration page. In some cases, the provider approval finished successfully, but the project screen has not yet updated. If the status still does not change, repeat the reauthorization flow and make sure you completed the provider’s final consent step before returning to Atloria.

If the wrong Git account becomes connected after reauthorization, the issue is usually caused by an existing provider session in your browser. Sign out of the provider account you do not want to use, return to the project’s Git connection settings in Atloria, and start the reauthorization flow again. When the provider asks you to continue, choose the correct account explicitly rather than accepting the default account automatically.

If the Disconnect option is missing or does not respond, first confirm that you are signed in as a Project Administrator for that project. Then wait a moment and make sure the project settings page has fully loaded the current source connection details. If the connection area is still loading, Atloria may not yet show the correct actions.

If project features stop working after disconnecting, that is usually expected for any repository-dependent workflow. The project still exists, but source-linked actions remain unavailable until you reconnect the provider or set up a new source connection for that project.

Common checks:

• Refresh the project connection page after reauthorization.
• Confirm the provider approval flow was fully completed.
• Retry with the correct Git account if the wrong one was used.
• Verify Project Administrator access if connection actions are unavailable.
• Reconnect the provider if the project needs repository-based features again.

Overview

This guide focuses on two project-level actions in Atloria: restoring access to an existing Git connection and removing that connection from a project. Use it when a project already has a Git provider listed, but the connection is no longer valid, or when you intentionally want to stop using that provider for the project.

The most important distinction is the difference between a connection that needs reauthorization and a project that has no active Git connection at all. Reauthorization is for a project that still shows a remembered provider but has lost valid access. Disconnecting is for removing the active link between the project and that provider. If you need help understanding the normal connection status indicators before making changes, review Reviewing Git Connection Status and Access Health.

This guide stays focused on what you do in the project’s source connection area: checking the provider status, confirming you have the right access, completing the provider approval flow, and understanding what changes in the project after you disconnect. It also explains what usually remains in place, such as existing project records, and what stops working, such as repository-backed actions.

Use this guide when you need to:

• restore an expired or invalid Git connection
• confirm you are reconnecting with the correct provider account
• safely disconnect a provider from a project
• understand the effect of that change on repository-linked project workflows

Prerequisites

Before you reauthorize or disconnect a Git integration in Atloria, make sure these conditions are true:

• You are signed in to Atloria and can open the correct project workspace.
• You have Project Administrator access for that project.
• The project already has, or previously had, a Git provider connection shown in its source connection settings.
• You know which Git provider account should be used for this project.
• You are ready to complete the provider’s sign-in or approval screen outside Atloria if reauthorization is required.

It is also helpful to confirm a few project details before you begin:

• Review the current provider name shown in the project’s Git connection area.
• Check whether the project is tied to a specific repository and branch.
• Make sure you understand whether your goal is to refresh access or fully remove the connection.
• If multiple Git accounts are signed in within your browser, decide which one should be used before starting the approval flow.

If you are not yet comfortable finding the project connection status or identifying whether access is healthy, read Reviewing Git Connection Status and Access Health first. If you need broader help with project setup and project-level controls, Managing Project Administration from the Project Home gives useful context around where these settings fit inside the project workspace.