Choosing And Maintaining External Connections For Project Wo

Deciding Which External Connection Fits Each Project

When you open a project in Atloria and move to its integration or connection area, the most important choice is the External connection selector. This choice determines which outside account the project can use and what linked project details you can add afterward. If you need help creating or managing those shared connections first, use Connecting and Managing External Integrations.

Choose the connection that matches the real workspace where your team already works. For example, if your project needs to link to a specific repository, board, folder, or external project record, pick the connection that already has access to that exact location. After you choose it, Atloria can show project-level fields such as an external project ID, workspace, board, repository, folder, or sync scope. If you choose the wrong connection, those follow-up fields may point to the wrong account or may not match the records your team expects to use.

A shared connection works best when several Atloria projects should use the same outside account and the same ownership model. This is usually easier to maintain because updates such as credential changes happen once and continue to support every linked project. A dedicated connection is better when one project needs separate ownership, separate permissions, or its own external account.

Think beyond setup. The connection you choose affects who maintains access later, who updates credentials, and whether sync activity continues smoothly after staffing changes. If a connection belongs to one person and that person loses access, every project tied to it can be affected. A well-chosen connection keeps project mapping stable and reduces rework when teams change.

Reviewing What You Need Before Assigning a Connection

Before you assign an external connection to a project, make sure you can actually edit the project and view the available connections. In Atloria, open the project and confirm that you can reach the project settings or integration area and interact with the External connection list. If the list is visible but you cannot change it, ask an administrator who manages organization settings or user access. Related guidance is available in Managing User Access and Administrative Permissions.

You should also gather the details the connection may rely on. Atloria can support project mappings that depend on information such as an account URL, workspace name, tenant name, API key, client ID, service account details, repository name, board name, folder name, or an external project ID. You may not need every item for every connection, but you should know which values your team expects to use before you start filling in the project form.

Check the outside workspace before assigning the connection. Confirm that the target project, customer area, task board, repository, or folder already exists if your workflow depends on linking to an existing record. If the outside structure is missing or named differently, you can end up saving a project with incomplete mapping details or linking it to the wrong destination.

It also helps to decide ownership before setup is finished. Identify:

• Who will maintain the shared connection
• Who can update credentials if access changes
• Who watches for sync failures or mapping problems
• Where your team records project-specific connection notes

This preparation prevents delays when the project is already active and someone needs to fix a broken link quickly.

Connecting a Project to an External System

1. Open the project you want to connect in Atloria.

2. Go to the project’s integration or connection area, then find the External connection dropdown or picker.

3. Select the correct connection from the list. Use the connection name that matches the outside account your team intends to use for this project.

4. Complete any project-level fields that appear after you make the selection. Depending on the connection, Atloria may show fields for:

   • External project ID
   • Workspace
   • Board
   • Repository
   • Folder
   • Synchronization scope

5. Review each value carefully before saving. These fields control which outside record Atloria links to for this specific project.

6. Click Save.

After saving, look for confirmation on the project screen. Atloria may show a connection status indicator, the linked account name, or a last sync detail that confirms the project is tied to the selected external connection. If those details do not appear, reopen the connection area and confirm that all required mapping fields were completed.

Record any exceptions while the setup is still fresh. For example, note whether this project uses manual sync instead of automatic updates, whether the mapping is read-only, or whether certain project details should stay in Atloria and not be pushed out. Keep those notes with the project so the next administrator does not assume the workflow behaves like every other connected project.

If you are connecting a newly created project, this step usually fits naturally after the onboarding work described in Creating Projects and Completing Onboarding.

Understanding How the Connection Affects Project Setup and Ongoing Work

Once you attach an External connection to a project, Atloria may change what the project requires before it can be saved or used normally. Fields such as External project ID, Workspace, Repository, Board, or Folder can become part of the project’s required setup. In some cases, choosing the connection also narrows the list of linked resources you can select, because Atloria is now working within one outside account instead of showing unrelated options.

That connection choice can also shape how the project behaves over time. Project creation details, task-related updates, status changes, or file activity may be sent to the linked outside workspace or pulled back into Atloria, depending on how the project mapping was set up. If your team expects synchronization, the project’s linked resource details need to stay accurate. A renamed workspace, moved folder, or replaced repository in the outside tool can interrupt the workflow even if the project itself still looks complete in Atloria.

Connection rules also matter when you reuse project structure. If your team creates projects from templates or copies existing projects, check whether the external mapping fields were copied too. Reused values can accidentally point a new project to an old external record. The same caution applies to archived projects and child records created after the connection is in place.

Be especially careful when changing a connection on an active project. Switching the External connection after work has already started can require remapping the project to a different external project ID, board, repository, or folder. If you skip that review, Atloria may continue using outdated links or create duplicate links in the outside workspace. For active projects, treat connection changes as a controlled update rather than a quick dropdown change.

Keeping External Connections Reliable Over Time

A project connection is not something you set once and forget. In Atloria, review connected projects on a regular schedule and look for visible health signals such as connection status, last successful sync, and any recent error message shown in the project’s integration area. A quick review helps you catch problems before a team member notices that updates are no longer reaching the linked workspace.

Credential updates need a planned process. If your organization rotates API keys, tokens, or service account access, update the shared connection in a way that protects active project mappings. The goal is to refresh access without changing the project-level fields such as External project ID, Workspace, Repository, Board, or Folder unless those records truly changed. If you manage shared connections centrally, one update can keep many projects working without editing each project individually.

Regular audits are also useful after team or organization changes. Review projects for:

• Stale external project IDs
• Renamed workspaces
• Deleted folders or repositories
• Connections still owned by someone who changed roles
• Projects linked to a connection that is no longer the team standard

Consistency matters just as much as repair work. Standardize how your team names connections, who owns them, and when a project should use a shared connection versus a dedicated one. When new projects follow the same connection rules from the start, setup is faster and troubleshooting is easier.

For broader project maintenance habits, pair this work with Managing Project Settings and Website Options, especially if several administrators share responsibility for long-running projects.

Fixing Common Connection Problems in Project Workflows

When a project will not save after you select an external connection, start with the connection itself. In the project’s integration area, confirm that the chosen item still appears in the External connection list and has not been removed or made inactive. If the connection exists but the project still cannot be saved, review whether required mapping fields such as External project ID, Workspace, Board, Repository, or Folder are blank.

If sync activity fails after the project was already working, compare the current project mapping with the outside workspace. Check whether the linked project, board, repository, or folder still exists and still uses the same name or identifier. A moved or deleted record outside Atloria can break the link even when the project’s saved values look unchanged.

When updates are reaching the wrong external record, review how the project was created. This often happens when someone copied a project template or duplicated an existing project and left the old external identifier in place. Open the project, inspect every mapping field, and confirm that each value belongs only to this project. If two projects share the same external project ID or folder by mistake, correct the mapping before more updates are sent.

Permission errors usually point to the account behind the selected connection. Confirm that the linked account still has access to the external project area your workflow depends on. If the owner changed roles or lost access, the project may still show the connection name while sync actions fail behind the scenes.

If the problem is wider than one project, review the shared connection first using Connecting and Managing External Integrations. If the issue is tied to project setup, compare the project’s mapping details with similar working projects in Atloria.

Overview

This guide focuses on the project-level side of external integrations in Atloria: choosing the right External connection for a project, filling in the mapping details that appear after selection, and keeping those links dependable as projects change over time. It assumes the connection itself already exists in Atloria. If you still need to add, authorize, or manage the shared connection record, start with Connecting and Managing External Integrations.

The main decision point is the External connection selector inside a project. That single choice affects which account the project uses, which mapping fields become available, and how the project connects to outside records such as repositories, boards, folders, workspaces, or external project entries. Because of that, connection setup is not just an admin formality. It directly affects project onboarding, template reuse, sync reliability, and long-term maintenance.

You will also see how to prepare before assigning a connection, what to verify after saving, and what to review when a project starts failing to sync correctly. The guide stays focused on what project administrators do on project screens rather than on organization-wide connection creation.

Use this document when you are:

• Assigning an external connection to a new project
• Reviewing whether a project should use a shared or dedicated connection
• Updating project mapping details after outside workspace changes
• Troubleshooting a project that no longer syncs as expected

For related project setup decisions, continue with Choosing Between Manual and Connected Project Setup.

Prerequisites

Before you work through project connection setup in Atloria, make sure the basic access and project details are already in place. This guide does not cover account sign-in or creating shared connections from scratch.

You should have:

• Access to sign in to Atloria and open the target project
• Permission to edit the project’s settings, integration area, or connection settings
• At least one available item in the External connection list
• The correct outside workspace details for the project you are linking
• A clear owner for ongoing connection maintenance

It is also helpful to confirm the following before you begin:

If you still need help getting into Atloria, see Signing In to Atloria and Solving Access Problems. If you need to create the project first, use Creating Projects and Completing Onboarding. If the shared connection has not been added yet, return to Connecting and Managing External Integrations.