Configuring Project Delivery Options and Connected Services

Opening Project Settings and Understanding What Can Be Changed

After you finish project onboarding, the next place to work is the project’s Settings area. Open your project from the main workspace, then use the project navigation to go to Settings. This is where Atloria keeps the project options that can still be adjusted after the initial setup. If you already planned your project structure and content organization, keep that work in mind as you review settings here. For structure decisions, refer back to Managing Project Structure and Content Planning.

Inside Settings, look for grouped sections related to:

1. Connected Services or other connection-related options
2. Website settings for publishing destination and site behavior
3. Operational or control settings that affect syncing, publishing, and linked actions

These sections are different from onboarding-only decisions. Onboarding helps you create the project and choose its starting setup path, but the Settings screen is where project administrators return later to update live behavior. If a choice is visible here as a field, switch, selector, or saved section, you can usually change it without recreating the project.

As you move through the page, pay attention to how each setting is presented:

• Text fields and dropdowns usually need Save
• Toggles or switches may apply right away or may still require Save
• Connection changes may require you to reconnect or reauthorize the linked service
• Website changes may not be visible publicly until the project is published again

Before changing anything, read the current values carefully. In Atloria, project settings often affect publishing destinations, connected accounts, and service behavior, so it helps to understand which section controls which part of the project before you start editing.

Choosing Connected Setup Options for External Services

Open the Connected Services or Integrations section in the project’s Settings area and review each listed connection one at a time. This section is where you manage how the project links to outside services used for publishing, syncing, or project-related workflows. Each connection may show its own status, selected account, workspace, endpoint, or authorization state.

Use the available fields exactly as they appear on screen. Depending on what has been enabled for your project, you may see options such as a linked account selector, workspace selection, endpoint details, or other mapping choices that determine where the project sends or receives information. If a service is already connected, review the current values before changing them so you do not accidentally point the project to the wrong destination.

1. Open Settings in the project.
2. Select the Connected Services or similar connection section.
3. Click the service you want to review or edit.
4. Update the available fields, such as the linked account, workspace, or connection target.
5. Turn the connection on or off if that option is available.
6. Click Save if the section includes a save action.

After saving, check the visible status on the same screen. Atloria may show a connection state such as connected, authorized, or another clear indicator that the service is ready. If the connection no longer shows as active after your change, reopen it and confirm that all required fields were selected correctly.

When you disable one service, that should only affect that specific connection. You do not need to reconfigure unrelated project settings unless Atloria shows a warning that another linked option depends on it.

If you need broader guidance on organization-wide connections, see Connecting and Managing External Integrations.

Configuring Website-Related Project Behavior

To control where your project publishes on the web, open the Website section inside the project’s Settings area. This is where Atloria shows the options that connect the project to its website presence and determine how documentation changes move from the project workspace to the published destination.

Look for fields that identify the project’s web target. Depending on what your project uses, the screen may include a selected site, a publishing destination, a URL-related field, or environment-style choices that separate one web target from another. Use the values shown in the interface to confirm that this project is linked to the correct website location before you change publishing behavior.

1. Open the project and go to Settings.
2. Select the Website section.
3. Review the current site or publishing destination shown on the page.
4. Update the available website fields, such as the selected site or target destination.
5. Choose the publishing behavior shown in the available options.
6. Click Save to keep the changes.

As you review publishing behavior, pay special attention to whether changes:

• publish automatically
• wait for review
• remain unpublished until someone takes a separate publishing action

Those choices affect how quickly project updates appear on the website. If your team uses approval steps or staged releases, make sure the website settings match that process. A project connected to the wrong site or set to the wrong publishing mode can send content to an unintended destination or make updates visible sooner than expected.

After saving, stay on the page long enough to confirm the updated website value appears correctly. If Atloria shows the selected site, destination, or publishing state in a summary area, verify that it matches what you intended.

For more detail on broader website and publishing setup, see Managing Project Settings and Website Options.

Setting Operational Controls That Affect Publishing and Integrations

The Operational settings in a project’s Settings area control how Atloria behaves when publishing, syncing, or responding to connected services. These controls are especially important when your project is linked to a live website or to services that can trigger updates automatically.

Open the section that contains switches, checkboxes, or policy-style options related to publishing and syncing. Read each label carefully before changing it. Even a single toggle can change whether Atloria publishes automatically, waits for a manual step, or reacts to updates coming from a connected service.

1. Go to the project’s Settings page.
2. Open the operational control section.
3. Review each toggle, checkbox, or policy field before making changes.
4. Update only the controls related to the behavior you want to change.
5. Click Save if the section requires it.
6. Recheck the displayed state after saving.

These controls often work together with your connected services and website settings. For example:

• A service may be connected and authorized, but project controls may still prevent automatic actions
• A website destination may be selected, but publishing may remain manual
• A sync option may be available, but project rules may limit when updates are sent

Because of that, do not assume a connected status means content will publish or sync immediately. Always compare the connection state with the project’s operational settings.

If your project supports live publishing or external updates, coordinate changes with the people who manage documentation releases. A small change in operational behavior can affect when content appears publicly or when linked services begin acting on project updates.

If your project uses event-based connections, pair this review with Configuring Project Webhooks and Related Controls.

Managing Permissions and Safe Change Practices

Before editing Connected Services, Website, or operational settings, make sure you have project administrator access. In Atloria, these settings affect how the project connects to outside services and how documentation may be published, so they should only be changed by people responsible for project-level administration. If you can open the project but cannot edit fields or save changes, your access level may not include these controls. In that case, work with someone who manages project permissions. For access guidance, see Managing User Access and Administrative Permissions.

When you are working on a live project, use a staged approach instead of changing several settings at once. Update one section, save it, and confirm the result before moving to the next. This makes it much easier to spot which change affected publishing or syncing behavior.

Good change habits in Atloria include:

• Write down the current values before you edit them
• Change one connection or website option at a time
• Save after each meaningful update instead of batching unrelated edits
• Coordinate with other administrators so settings are not overwritten
• Choose a low-impact time if the project is connected to a live site or active service

A simple record can help a lot when multiple administrators work in the same project. Note the current connected account, selected site, publishing mode, and any operational toggles before saving new values. If the result is not what you expected, you can quickly compare the new setup with the previous one.

If a change could trigger syncing, republishing, or other downstream activity, tell the documentation manager before saving it. This is especially important when the project is already in active use and the published site is visible to readers.

Verifying the Configuration After Saving Changes

After you save any project setting, reopen the same Settings page and confirm the new values are still there. This is the quickest way to make sure Atloria accepted the update. Check each section you changed—Connected Services, Website, and operational controls—and compare the displayed values with the choices you intended to save.

1. Return to the project’s Settings page after saving.
2. Reopen each section you edited.
3. Confirm the saved values match your intended setup.
4. Review any visible status labels or indicators.
5. Perform a safe test action if your team allows it.
6. Confirm the result without changing unrelated settings.

Look for visible status indicators that help confirm the project’s state. Depending on the section, Atloria may show signs such as:

• connected
• authorized
• unpublished
• pending sync
• publish-ready

These labels are useful because they tell you whether the project is merely configured or actually ready for the next action. For example, a service may be saved but still need reconnection, or a website target may be selected while the project remains unpublished.

If possible, run a low-risk test. That might mean checking whether a small publishing action follows the selected behavior or confirming that a connected service reflects the updated project link. Keep the test narrow so you do not affect unrelated project settings or release work.

If something does not look right:

• check whether you clicked Save
• reopen the section and confirm no field was left incomplete
• reconnect the affected service if the authorization state changed
• verify the project is linked to the correct website or destination

For broader publishing validation, continue with Publishing a Project from Setup to Public Release.

Overview

This document focuses on the project settings you manage after onboarding is complete. In Atloria, those settings are centered around three practical areas: Connected Services, Website, and operational controls that influence publishing and sync behavior. The goal is not to repeat project creation or structure planning, but to help project administrators safely adjust the live configuration that controls where documentation goes and how linked services behave.

You will use these settings when a project needs to point to a different website destination, when a connected service must be updated or reauthorized, or when publishing behavior needs to change from automatic to manual review. These are ongoing administration tasks, not one-time onboarding choices. If you need help with the earlier setup path that led to this point, refer to Creating Projects and Completing Onboarding and Choosing Between Manual and Connected Project Setup.

This guide also emphasizes safe change practices. In many teams, project settings are shared responsibilities, and a small update can affect public publishing, background syncs, or service-triggered actions. Because of that, the guide shows how to review current values, save changes carefully, and confirm visible status indicators after each update.

Use this page when you need to:

• update a project’s connected service details
• review or change website publishing targets
• adjust project-level publishing or sync controls
• verify that saved settings are active and behaving as expected

If you are already comfortable with project structure and content planning, this guide is the next step in getting the project ready for controlled delivery and connected workflows.

Prerequisites

Before working through these settings in Atloria, make sure the project has already been created and onboarding is complete. This guide assumes you are no longer choosing the initial setup path and are now managing the project’s ongoing configuration. If you still need to finish those earlier steps, start with Creating Projects and Completing Onboarding and Managing Project Setup Decisions After Onboarding.

You should also have:

• access to the correct project workspace
• project administrator permission to edit Settings
• a clear understanding of the project’s intended website or publishing destination
• confirmation of which connected services the project is expected to use
• awareness of any team process for review, approval, or scheduled publishing changes

It also helps if you have already completed the planning work covered in Managing Project Structure and Content Planning. That earlier planning does not control delivery settings directly, but it gives useful context when you decide how the project should publish and which connected services it should rely on.

Before making changes, gather the information you will need from the current project setup screen itself. Review the existing connected account, selected website destination, and any visible publishing or sync controls. If multiple administrators work in the same project, align on who is making the update so one person’s changes do not overwrite another’s.

If the project is already tied to a live website or active service connection, plan your edits for a time when a brief configuration change will have the least impact on documentation work or public visibility.