Connecting Projects to Git Providers

Understanding how Git connections work in Atloria projects

In Atloria, a Git connection is part of a project’s source-based setup. You can connect a repository while creating a new project, or return later and add it from the project’s settings. If you already worked through the earlier setup choices in Choosing Between Manual and Connected Project Setup or Connecting Projects to Git and Maintaining Access, this screen is where that choice becomes an active project connection.

The connection happens in two parts. First, you connect Atloria to your Git provider account. That gives Atloria permission to see the repositories your account is allowed to access. Second, you choose the specific repository that belongs to this project. Connecting your provider account does not automatically attach every repository. You still need to pick the repository for the current project and save it.

When you review the project’s source settings, pay attention to three different ideas that can appear in the interface:

• Provider connection: whether your Git account is connected to Atloria
• Repository connection: whether this project is linked to a specific repository
• Current status or health: whether Atloria can still access that repository and use it for source-based actions

These are related, but they are not the same. For example, your provider account can be connected while the project still has no repository selected. Or the repository may be selected, but Atloria may show that access needs attention if permissions changed.

Project Administrators usually connect a repository during initial onboarding when they want documentation or project setup to follow source content from the start. You can also open the project later and update the source connection if the repository changes, ownership moves, or the original connection was skipped.

Preparing your project and Git account for connection

Before you open the Git connection screen, make sure you can complete both sides of the setup: access in Atloria and access in your Git provider. In Atloria, you need Project Administrator rights for the project you want to connect. If you can open the project but do not see the source or repository settings, ask an administrator to update your access first.

You also need enough permission in your Git provider account to authorize Atloria and view the repository you plan to use. If the repository belongs to a team or company account instead of your personal account, the provider may require extra approval before Atloria can list it. That is especially important when you expect to see an organization repository in the picker.

Gather the repository details before you start so you can move through the setup without guessing. The most useful details are:

If the Atloria project does not exist yet, create it first from the project area before looking for source connection settings. If you already have a project, open that project and go to its settings or source connection area.

It also helps to confirm with your team whether this repository is the long-term source for the project. Changing repositories later can affect source-based work already tied to the existing project setup, so it is better to confirm ownership, branch choice, and repository name before you connect.

Authorizing Atloria with your Git provider

1. Open the project you want to connect in Atloria, then go to the project’s source or repository settings. Look for the option to connect a Git provider, such as Connect Git Provider.

2. Click Connect Git Provider to start the authorization flow. Atloria will show the supported provider options. Select the provider that hosts your repository.

3. Atloria sends you to the provider’s sign-in or consent screen. If you have more than one account with that provider, choose the account that can access the repository you need for this project.

4. Review the approval prompts carefully. Depending on the provider, you may be asked to:

   • confirm your account
   • allow Atloria to access repositories
   • choose whether access applies to all available repositories or only approved ones
   • request organization approval if the repository belongs to a company or team account

5. Complete the provider’s approval steps and return to Atloria. After the redirect finishes, go back to the project’s source settings and confirm that the provider account now appears as connected.

If the connection does not appear right away, refresh the page and check the source settings again. A successful provider authorization usually means Atloria can now show repositories available to that account, but you still need to choose the correct repository for this project before the setup is complete.

If you are asked to wait for organization approval, stop here until that approval is granted. Atloria cannot list or connect the organization repository until the provider finishes that approval step.

Selecting the repository and saving the project connection

1. After your provider account shows as connected, stay in the project’s source settings and open the repository picker.

2. If Atloria shows an account or organization selector, choose the owner that contains the repository. This is important when your connected provider account can access both personal repositories and organization repositories.

3. Select the repository you want to attach to the project. Read the repository name carefully before continuing. If your team uses similar names for staging, archived, or forked repositories, double-check that you picked the active one.

4. Complete any source details Atloria shows on the same screen. Depending on the project setup, this may include the branch Atloria should use or another source location setting tied to the repository.

5. Click Save or the project’s connection action to finish linking the repository.

After you save, Atloria may show an immediate status such as connected, pending sync, or another access confirmation message in the source settings area. This status helps you tell the difference between “repository selected” and “repository ready for source-based work.”

Be careful when changing an existing connection. Switching the repository for a live project can redirect future source-based actions to a different codebase or documentation source. That is why Project Administrators should confirm the account, repository name, and branch before saving any change. If you are replacing an older repository, review the project details first so you do not accidentally point the project to the wrong source.

Managing connected repositories during project maintenance

Project Administrators can return to the project’s Git connection settings at any time to review the current provider account, reconnect access, switch repositories, or refresh authorization after a permission change. This is useful when the original connection is still listed in Atloria, but the repository owner, team access, or provider approval has changed since the project was first set up.

Common maintenance situations include:

• Permissions changed in the provider account: a repository may stop appearing or Atloria may no longer confirm access
• Provider consent was revoked: Atloria may still show the previous connection details, but source-linked actions can stop working until you reconnect
• The project moved to a different repository: you can reopen the source settings and select the new repository for the project
• An organization repository now requires approval: reconnecting may be necessary after the provider updates organization access rules

Source-based workflows in Atloria depend on the active repository connection. If your project uses repository-linked updates, imports, or other source-driven actions, those actions rely on the current connection remaining valid. When access breaks, the project may still exist normally in Atloria, but repository-based actions will not continue until the connection is restored.

If you remove the repository connection entirely, Atloria no longer has a source repository attached to that project. The project itself remains available, but source-linked actions are unavailable until you connect a repository again. For teams that regularly maintain repository access, it helps to review this screen after any provider-side permission change or repository transfer.

For broader project maintenance after connection, see Managing Project Administration from the Project Home.

Verifying your setup

Once the repository is saved, open the source settings again and confirm the details shown on screen. You should see the connected provider account, the selected repository name, and a current status that indicates whether Atloria recognizes the connection. This is the fastest way to catch a wrong account or similarly named repository before your team starts using source-based project actions.

Next, look for the first source-linked action available in the project. Depending on the project, Atloria may show an initial sync, import, or another repository-based action. Use that first action, or watch for its status, to confirm Atloria can actually read the repository rather than only display the saved connection. If the project screen shows a pending state, wait for that first repository check to complete and then refresh the page if needed.

Also verify that the selected branch or source location matches the structure your project is supposed to use. A project connected to the right repository but the wrong branch can still produce confusing results. Compare what you see in Atloria with the branch your team expects to use for the project’s source-based workflow.

If the repository does not appear in the picker, check these items before trying again:

• the correct provider account is connected
• Atloria was granted repository access during authorization
• organization approval has been completed for team-owned repositories
• your Git account can view the repository directly in the provider
• the repository belongs to the selected account or organization in the picker

If access still looks wrong, reconnect the provider account from the same settings screen and repeat the repository selection.

Overview

Connecting a project to a Git provider in Atloria means linking two things: your provider account and the repository that belongs to the project. You start from the project’s source or repository settings, connect the provider account through the authorization screen, return to Atloria, and then choose the repository from the available list. After that, you save the connection and confirm the status shown in the project settings.

The most important detail to remember is that provider access and repository selection are separate steps. Seeing a connected provider account does not mean the project is fully connected yet. The project is only ready for source-based work after the correct repository is selected and saved.

During setup, pay close attention to:

• the provider account you authorize
• whether the repository is personal or organization-owned
• the repository name shown in the picker
• the branch or source location selected for the project
• the connection status shown after saving

This screen is also where you return later if access changes. If a repository stops appearing, permissions are updated, or provider approval is revoked, Project Administrators can reopen the same settings and reconnect or switch repositories as needed.

If you have already connected a provider and saved the repository, the next step is checking whether Atloria continues to recognize that connection over time. Continue with Reviewing Git Connection Status and Access Health.

Prerequisites

Before you connect a repository to a project in Atloria, make sure these items are in place:

• You can open the target project in Atloria
• You have Project Administrator access for that project
• You know whether the project should use a personal repository or an organization repository
• You can sign in to the correct Git provider account
• Your Git provider account can view the repository you want to connect
• You know the repository name your team expects Atloria to use
• You know the branch or source location the project should follow, if Atloria asks for it during setup

It is also helpful to confirm these details with your team before you click Save:

• which provider account owns the repository
• whether the repository has been moved, renamed, or transferred recently
• whether organization approval is required before Atloria can access team-owned repositories
• whether this is a first-time connection or a replacement for an existing repository

If you still need to create the project itself, use Creating Projects and Completing Onboarding. If your team is deciding whether to connect a repository now or continue with a manual setup, review Connecting Projects to Git and Maintaining Access.

These checks keep the connection process simple and reduce the chance of selecting the wrong repository or running into missing-permission issues halfway through authorization.