Reviewing Git Connection Status and Access Health

Opening the Git connections view for your project

Before you review connection health in Atloria, make sure you are signed in with a role that can manage project settings. If you can open the project workspace but do not see connection or integration settings, you may need Project Administrator access. If access itself is the issue, use Signing In to Atloria and Solving Access Problems. If you still need to connect a repository for the first time, use Connecting Projects to Git Providers.

1. Sign in to Atloria and open the project you want to review.
2. Go to the project area where connected services and repository links are managed. Depending on your workspace setup, this may appear under project settings, integrations, or the repository connection area.
3. Open the Git connection details for that project.

On this screen, look for the section that shows the current linked source. This is the area you will use to confirm whether the project is still connected correctly. You should expect to see details such as the Git provider, the connected account, and the repository that Atloria is using for documentation sync.

Some projects show a single project-level connection. Others may display more than one linked repository or source entry. If your project has multiple connected repositories, review each one separately instead of assuming the overall project is healthy. A single broken repository link can still interrupt imports, updates, or branch-based documentation work for part of the project.

If you are unsure how your project was originally linked, refer back to Connecting Projects to Git Providers for Source Based Workflows. For this review, stay focused on what the connection screen currently shows rather than reconnecting anything yet.

Reviewing which Git account and repository are currently connected

Once you are on the Git connection screen, start by confirming that Atloria is pointing to the correct source. The most important items to review are the connected account, the Git provider, and the repository details shown in the connection panel.

1. Find the connected account section and read the account name exactly as shown.
2. Check the Git provider listed for the connection.
3. Review the repository owner and repository name.
4. Confirm the branch or sync target shown for the project.

These details help you catch a common problem: a project that is technically connected, but connected to the wrong place. For example, the repository name may look familiar while the owner or organization is different from the one your team expects. That can lead to imports from the wrong source or missing updates from the right one.

Use any visible account labels to tell similar connections apart. Atloria may show identifying details such as a username, organization name, or installation label. These clues are especially useful when your team has both personal and organization-managed Git access. If the connected account belongs to an individual when your team expects a shared organization connection, that is worth reviewing before it causes access problems later.

A quick comparison table can help during this check:

If any of these details do not match your team’s expected setup, treat that as a connection health issue even if the status still appears connected.

Checking whether access is still valid

After confirming the connection points to the right repository, check whether Atloria can still use that connection successfully. A connection can look correct but still fail because access has expired, permissions changed, or the repository is no longer available to the linked account.

1. Locate the connection status area on the Git connection screen.
2. Read the current status shown for the linked account and repository.
3. Review any timing details shown nearby, such as the last successful sync, last access check, or authorization time.
4. Click the available action to refresh, recheck, or test the connection.
5. Wait for the status to update and read the result carefully.

A healthy connection usually shows a clear connected or active state. If Atloria displays a recent successful sync or access check, that is a good sign that the link is still working. If the last successful activity is old, the connection may need attention even before a full error appears.

When you run a fresh check, focus on the exact result message shown on screen. Common outcomes include:

• Connected: Atloria can still reach the linked repository with the current account.
• Authorization expired: The linked account needs to be reauthorized.
• Repository not found: The repository may have been removed, renamed, transferred, or the account may no longer have access.
• Insufficient permissions: The account is still linked, but it no longer has the access Atloria needs.

If the status changes after you run the check, trust the latest result rather than an older status label. This is the fastest way to confirm whether the project is healthy right now, especially after team changes, repository moves, or provider-side permission updates.

Spotting warning signs that the connection needs attention

Not every problem appears as a full disconnection right away. In Atloria, early warning signs often show up before documentation workflows stop completely. Reviewing these signs regularly helps you fix access issues before authors notice missing updates or failed imports.

Watch the Git connection screen for visual indicators such as warning badges, alert banners, degraded status labels, or messages that call out limited access. These usually mean the project is still linked, but something about the connection is no longer fully healthy.

Pay close attention to issues like:

• Missing branch access
• Revoked or removed installation access
• Expired account authorization
• Repository transfer or rename messages
• Failed sync notices
• Repeated import errors
• A last synced time that is much older than expected
• A connected account that no longer matches the current team setup

A stale sync timestamp is one of the easiest warning signs to miss. If your team expects regular updates from Git but the last sync is old, Atloria may no longer be receiving changes even if the connection has not fully failed. The same is true if the repository owner shown on screen no longer matches your organization after a team restructure or repository move.

Also review whether the connected identity still makes sense. A project may still be linked through a former administrator’s account or an outdated organization installation. That can leave the project vulnerable to sudden failure when that person loses access or the installation is removed.

If you see any mismatch between the displayed account, repository owner, branch access, or recent sync activity, treat it as a sign that the connection needs review rather than waiting for a complete break.

Understanding how connection health affects documentation workflows

Git connection health directly affects how current your project documentation stays in Atloria. When the linked account loses access or the repository connection becomes unstable, Atloria may no longer be able to pull in source changes, follow branch updates, or keep connected documentation workflows current.

A broken or degraded connection can affect several parts of your team’s work:

• Repository sync may stop updating project content
• Imports from the connected source may fail
• Branch-based documentation updates may stop appearing
• Review work may continue against outdated content
• Publishing decisions may be made using stale project information

This does not always happen all at once. Some issues are informational and give you time to act. For example, a warning about aging authorization or an account mismatch may not block work immediately, but it signals that the connection is at risk. Other issues need immediate attention, especially messages that say authorization expired, repository not found, or insufficient permissions. Those usually mean Atloria cannot reliably access the source your project depends on.

For project administrators, the goal is to catch these problems early. A quick status review can prevent confusion later when authors expect new content to appear and it does not. It also helps avoid delays in review and release work, since documentation versions may depend on current source content being available.

If your team uses connected project workflows heavily, make connection checks part of routine project administration. This is especially important after repository ownership changes, team membership updates, or provider-side access changes. Early review on the Git connection screen is often enough to spot a problem before it turns into a visible documentation gap.

Common connection health issues and how to fix them

Most Git connection problems in Atloria fall into a small set of patterns. The fix depends on what the connection screen is showing, so start with the exact status message or warning banner before making changes.

1. Authorization expired
   Open the project’s Git connection settings and use the reconnect or reauthorize option shown on that page. After reauthorizing, run the connection check again and confirm the status returns to a healthy state.

2. Repository access removed
   Confirm that the linked account still has access to the repository your project uses. If your team uses organization-managed access, make sure the repository is still included there. Then return to Atloria and run a fresh connection check.

3. Repository moved or renamed
   If the repository owner or repository path changed, update the project connection so it points to the current location. A repository that has been transferred to a different owner may appear connected at first but fail validation until the link is updated.

4. Sync status stays stale after reconnecting
   Run the refresh or test action again and verify that the project is using the correct linked account. If the account is valid but the wrong repository or branch is selected, Atloria may still show old sync activity.

Use this quick reference while reviewing the status:

If you need to replace the connection entirely, the next guide covers that process: Reauthorizing and Disconnecting Git Integrations.

Overview

Reviewing Git connection health in Atloria is a quick administrative check that helps you confirm a project is still linked to the right source and that Atloria can still reach it. The most useful information is all on the Git connection screen: the provider, connected account, repository owner, repository name, branch or sync target, and the current status result.

This review is not the same as creating a new connection. You are verifying an existing one and looking for signs that it may no longer be reliable. A project can appear connected while still having a hidden problem, such as an expired authorization, a renamed repository, outdated branch access, or a linked account that no longer belongs to the right team setup.

As you review the screen, focus on three questions:

• Is this the correct Git account for the project?
• Is this the correct repository and branch?
• Does Atloria show that access is still valid right now?

If the answer to all three is yes, your project’s connected documentation workflow is in a healthy state. If any answer is unclear, use the status check tools on the page before authors begin reporting missing updates.

This guide fits after the initial connection setup covered in Connecting Projects to Git and Maintaining Access. It is especially useful for project administrators who manage ongoing access, team changes, or repository ownership changes. The goal is simple: confirm that the project’s Git link is still healthy before it affects sync, review, or publishing work.

Prerequisites

Before you review Git connection status in Atloria, make sure these conditions are true:

• You can sign in to Atloria successfully.
• You have access to the project whose Git connection you want to review.
• Your role includes permission to open project settings or integration settings.
• The project has already been connected to a Git provider.
• You know which repository, owner, and branch your team expects the project to use.

It also helps to have basic context from the earlier setup guides, especially if you are checking a project you did not originally connect:

• Connecting Projects to Git Providers for Source Based Workflows
• Connecting Projects to Git Providers

If you are reviewing access after an internal team change, repository transfer, or provider-side permission update, be ready to compare what Atloria shows against your team’s current expected source. That includes the connected account name, repository owner, repository name, and branch. Without that reference point, it is easy to miss a connection that is valid technically but pointed at the wrong source.

You do not need to make changes before starting this review. The goal is to inspect the current connection first, run a fresh status check, and only then decide whether reauthorization or reconnection is needed. If the review shows that the connection needs to be replaced or removed, continue with Reauthorizing and Disconnecting Git Integrations.