Managing Project Setup Decisions After Onboarding

Finding the project setup choices you can still change

After onboarding, you can return to a project’s setup decisions from the project workspace rather than starting over. In Atloria, open the project from your project list or dashboard, then go to the project’s settings area or project administration area where configuration details are shown. This is the place to review the choices made during onboarding and confirm whether they still match how the team plans to document the project.

Look for the saved setup information in the project details view. Atloria surfaces the current project configuration so you can check what is already in place before editing anything. For this document, the setup decisions that matter most are:

• Project type
• Connected source or repository-related setup
• Other saved project details that help you understand how the project was originally configured

Before changing anything, compare the current values shown on screen with the setup approach your team intended to use. If you need a refresher on the original setup paths, refer back to Choosing Between Manual and Connected Project Setup.

Some setup choices have a direct effect on later documentation work. In practice, project type and connected source choices can shape how documentation is organized, what guidance appears during authoring, and how imported structure influences planning. Other project details may simply describe the project and help teammates understand its context without changing documentation behavior in a major way.

A quick review in the project details screen helps you avoid unnecessary changes. If the current values already match the team’s documentation plan, leave them as they are. If they no longer fit the project, update them from the same settings area so the rest of the documentation workflow stays aligned.

Reviewing and changing the project type

The Project type setting is one of the most important onboarding choices to revisit because it influences how your team structures documentation work. In Atloria, open the project’s setup or settings screen and find the field that shows the current project type selected during onboarding. Review the current value first so you know whether you are refining the setup or making a larger shift in direction.

When you open the project type selection, compare the available options against the kind of documentation your team is actually building. A project that started with one documentation approach may later need a different structure if the audience, source material, or publishing goals have changed. The selected project type can affect the kind of documentation organization Atloria expects, including the shape of planning work and the guidance documentation managers see when creating content.

To change it:

1. Open the project’s settings or setup screen.
2. Find the Project type field.
3. Select the new project type from the available options.
4. Review the rest of the visible setup details to make sure they still fit the new choice.
5. Click Save or the available update action.

After saving, watch for any on-screen confirmation, updated field value, or change in related setup information. If Atloria refreshes the project view or updates planning behavior afterward, treat that as a sign that the new project type is now active.

Because project type can influence templates, expected sections, and generated guidance, change it carefully when documentation work has already started. A different project type may cause documentation managers to see a different structure or set of expectations in later screens. If your team is already drafting pages, review those areas after saving so you can confirm the new setup still supports the documentation plan.

Reassessing connected sources before updating setup

If your project was set up with a connected source, review that connection before changing any setup choices tied to it. In Atloria, the current connected source is typically shown in the project settings or related project configuration area. Start by checking what source is currently linked so you can confirm whether the original connection still reflects the project your team is documenting.

A connected source can shape how Atloria understands the project and how your team approaches authoring. If the source has changed significantly since onboarding, the original setup may no longer be the best fit. For example, the connected source may now have a different structure, incomplete content, or access limitations that make imported or detected information less reliable for documentation planning.

Before updating source-related setup, verify these points in the project settings and related source views:

• The correct source is connected to the project
• The source is complete enough to support documentation work
• The branch or workspace selection still matches the material your team wants to document
• The connection is ready for sync or refresh if Atloria uses source information in the project workspace
• The team still has the access needed to keep using that source

These checks matter because source-related setup decisions can influence later documentation work. Imported content, detected structure, and source-driven planning cues may shape what documentation managers expect to see when they begin organizing pages. If the connected source no longer matches the project’s real scope, those expectations can drift away from the actual documentation goal.

Make source changes only after confirming what the team needs from the project. If you are unsure whether to keep the current connection or move to a different setup path, compare your current project with the setup guidance in Choosing Between Manual and Connected Project Setup.

Understanding how setup changes affect documentation work

Changing setup after onboarding does more than update a field in project settings. In Atloria, these choices can flow into the documentation workspace and influence how the team plans, drafts, and reviews content. That is why project administrators should connect every setup change to the work documentation managers are already doing.

A revised Project type can change the expected shape of documentation. Depending on the selected type, Atloria may guide the team toward different content areas, planning assumptions, or page structures. Documentation managers may notice changes in how they organize content, what sections seem necessary, or what guidance appears when they begin creating documentation. If the team has already agreed on a structure, even a small setup change can shift those expectations.

Changes to the connected source can also affect downstream work. If Atloria uses source information to shape planning, imported structure, or suggested content direction, updating the source setup may change what appears relevant in the project workspace. Existing drafts may still be present, but the context around them can change. Teams may need to revisit page plans, section groupings, or assumptions about what the source covers.

Pay special attention to these areas after a setup update:

• Project organization in the documentation workspace
• Recommended content areas or planning views
• Guidance shown during documentation creation
• Existing drafts that were based on earlier setup assumptions
• Team workflows that depend on source-driven structure

When active documentation work is already underway, coordinate setup changes with the people managing content. A project administrator may be able to save the new configuration quickly, but the documentation team may need to adjust outlines, templates, or page priorities afterward. If you change setup without warning, teams can end up revising work they already started. For broader project administration context, see Managing Project Administration from the Project Home.

Updating setup safely in active projects

When a project is already in use, treat setup changes as controlled updates rather than quick edits. In Atloria, start by checking whether documentation work is already in progress. Open the project workspace and review whether the team has begun planning pages, drafting content, or organizing documentation structure. If work is active, make sure the people responsible for that content know a setup change is being considered.

Use this approach to reduce disruption:

1. Review the current Project type and Connected source values in the project settings screen.
2. Record the current selections somewhere your team can reference during review.
3. Decide which single change is most important to make first.
4. Update only that one field and click Save.
5. Reopen the project details and documentation areas to see what changed before editing anything else.
6. Share the updated setup with documentation managers so they can confirm whether templates, sections, or planning guidance still make sense.

Making one change at a time is especially important when both project type and source setup may need adjustment. If you change several fields together, it becomes much harder to tell which update caused a shift in documentation behavior.

It also helps to compare the old and new setup states directly. Even a simple note of the previous project type and previous connected source can save time if the team later notices unexpected differences in planning views or authoring guidance.

If your project has active contributors, communicate clearly before and after the change. Documentation managers need to know when setup updates may affect expected sections, source-driven planning, or content structure. That coordination is often the difference between a smooth update and unnecessary rework.

Verifying the updated setup

After saving any setup change, return to the project settings or details screen and confirm that the new values are actually stored. In Atloria, the first check is simple: make sure the Project type field now shows the updated selection and that the Connected source area reflects the current source choice. If the old values still appear, the change may not have been saved.

Next, move beyond the settings screen and verify that the update is reflected where documentation work happens. Open the project overview, documentation workspace, or any planning view available in the project. Look for signs that the new setup is influencing downstream behavior. Depending on what changed, this may include updated guidance, a different planning emphasis, or documentation expectations that better match the revised project direction.

If the project uses a connected source, also confirm that source-related information still works after the update. Check whether the source remains accessible and whether any visible sync or imported structure indicators still look correct. You are not just confirming that the connection exists—you are confirming that it still supports the documentation workflow your team expects.

A practical final check is to open an existing documentation item or start a new one and compare what you see with the revised setup. Review whether the structure, guidance, or expected sections now align with the updated project type and source choice. If something still looks out of place, return to the project settings and compare the saved values again before making further changes.

This verification step is worth taking every time. It confirms that the project configuration and the documentation workspace are still moving in the same direction.

Overview

This guide focuses on the setup decisions that project administrators can revisit after onboarding is complete. In Atloria, the most important editable choices discussed here are the project’s Project type and its Connected source setup. These are not just descriptive settings. They can influence how a project is organized for documentation, what planning guidance appears, and how source-linked information shapes later authoring work.

Use this guide when a project has changed since onboarding, such as when the team chose the wrong setup path initially, the connected source no longer reflects the real project, or the documentation plan has shifted. Instead of repeating the onboarding flow, you return to the project settings or project details area, review the saved configuration, and update only the fields that still need adjustment.

This document builds on Choosing Between Manual and Connected Project Setup rather than repeating it. If you are still deciding between setup approaches, read that guide first. Here, the focus is on what happens after those initial choices have already been saved and the project is moving into documentation work.

The sections above walk through four practical tasks:

• Finding the saved setup values in the project
• Changing the project type carefully
• Rechecking connected source decisions before updating them
• Verifying how those changes affect the documentation workspace

Because setup changes can affect templates, expected sections, and source-driven planning, this guide also emphasizes coordination with documentation managers. That is especially important in active projects where drafts or content plans already exist.

The next step in this workflow is Planning Project Structure Before Document Authoring, where you turn the confirmed setup into a workable documentation structure.

Prerequisites

Before you update onboarding decisions in Atloria, make sure you have access to the project and can open its settings or project administration area. You need to be able to review the current project details and save changes to setup fields. If you cannot reach those areas, resolve your access first through the appropriate project or administrative workflow.

Have these items ready before you begin:

• A project that has already completed onboarding
• Access to the project workspace and its settings or configuration area
• A clear understanding of the project’s current documentation goal
• Agreement from the team on whether the Project type or Connected source should change
• Awareness of any documentation work already in progress

It also helps to gather a few details in advance so you can compare the current setup with the intended one:

• The currently saved Project type
• The currently displayed connected source information
• Whether the connected source still has the right content, structure, and access
• Whether documentation managers have already created outlines, drafts, or planning work based on the old setup

If your team is still deciding whether the project should use a manual setup or a connected source approach, review Choosing Between Manual and Connected Project Setup before making changes here.

For active projects, plan a short review with the people managing documentation so they can confirm the impact of any update. That is especially useful when setup changes may alter templates, expected sections, or source-driven planning. A small amount of coordination before editing the project settings can prevent larger cleanup work later.