Skip to content

Conversation

ian-at-airbyte
Copy link
Contributor

@ian-at-airbyte ian-at-airbyte commented Sep 19, 2025

What

This PR updates docs.airbyte.com to be consistent with the new sidebar/org landing page changes in Airbyte. This is a very large PR that touches almost every section of the docs site.

How

  • New "Organizations and workspaces" section: Created a new section to improve and expand the discussion of what these objects are in Airbyte. Pays particular regard to Enterprise Flex, data residency, and self-managed data planes. Moved most organization and workspace settings discussions to be children of that new section. In limited cases, a topic seemed thematically more relevant to another part of the docs, so I left it alone. Completely removed the "Account Management" section, because it was almost entirely about orgs and workspaces.

  • Updated instructions and screenshots: Updated all user, organization, and workspace settings tasks and instructions. Content now passes checks with MarkDownLint. Almost all of this info needed some level of rewrite, which is why this PR touches so many files. Where screenshots seemed valuable, I kept them and updated them. Several seemed unimportant on review, so I just removed them.

  • Mermaid diagram visual improvement: Added some color and spacing configuration to Mermaid diagrams so I could write some supporting flow diagrams. These changes aren't perfect, but they make the diagrams slightly more appealing than before. More work is needed on Mermaid's appearance, it just wasn't the focus of this task. These changes were applied in the main Docusaurus configuration file, so they would apply globally.

  • Consolidation of redundant content: Many connector migration guides had the same instructions. Instead of updating them all, I've added instructions on how to pin and update connectors to the Upgrading Connectors page. Then, updated connector migration guides to link to those instructions instead of reproducing them. This triggers review from Breaking Change Reviewers.

  • General cleanup of random problem areas, misspellings, typos, etc. that I noticed along the way.

  • Made a few additions to Vale's controlled vocabulary, to avoid linting those words.

Not part of this PR

  • This PR does not include new Arcades/interactive demos. I'll do this as a separate set of changes.

Review guide

  • The crux of the change is the creation of the new orgs and workspaces section. This is probably the area that should receive the most scrutiny.
  • Breaking change reviewers should ensure the changes to the migration guides are satisfactory.
  • It might be helpful to spot check the steps in other pages

User Impact

  • Accurate documentation and screenshots.

  • No changes to page URLs. This is a low risk set of changes.

Can this PR be safely reverted and rolled back?

  • YES 💚
  • NO ❌

Copy link
Contributor

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

Helpful Resources

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions.
    • You can specify a custom changelog by passing changelog. Example: /bump-version changelog="My cool update"
    • Leaving the changelog arg blank will auto-populate the changelog from the PR title.
  • /run-cat-tests - Runs legacy CAT tests (Connector Acceptance Tests)
  • /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).
  • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
  • /poe source example lock - Alias for /poe connector source-example lock.
  • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
  • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.

📝 Edit this welcome message.

Copy link
Contributor

github-actions bot commented Sep 19, 2025

Deploy preview for airbyte-docs ready!

✅ Preview
https://airbyte-docs-6q6ftii0r-airbyte-growth.vercel.app

Built with commit 360af8a.
This pull request is being automatically deployed with vercel-action

ian-at-airbyte and others added 10 commits September 19, 2025 18:43
…. Also fixed and linted a PostgresSQL Cloud topic that was behaving strangely.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…cy.md

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@ian-at-airbyte ian-at-airbyte changed the title Docs for new orgs and workspaces redesign [WIP DO NOT MERGE] Docs for new orgs and workspaces redesign Sep 22, 2025
@ian-at-airbyte ian-at-airbyte changed the title Docs for new orgs and workspaces redesign Docs for new orgs and workspaces redesign aka Org Landing Page Sep 22, 2025
ian-at-airbyte and others added 4 commits September 22, 2025 16:15
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@ian-at-airbyte ian-at-airbyte marked this pull request as ready for review September 22, 2025 23:18
@ian-at-airbyte ian-at-airbyte requested a review from a team as a code owner September 22, 2025 23:18
# Manage notifications

This page provides guidance on how to manage notifications for Airbyte, allowing you to stay up-to-date on the activities in your workspace.
If you want Airbyte to notify you about important events, use its built-in notification system.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Someone with more understanding of our notification system should review this.

### Airbyte Open Source (OSS) and Self-Managed Enterprise (SME)

Airbyte recommends using an updated version of Airbyte when updating connections.
Airbyte recommends using an updated version of Airbyte when updating connections.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know you did not write this on this PR but does Airbyte recommends using the latest version of Airbyte read better? I think that is what that is trying to say.

Copy link
Contributor

@bgroff bgroff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some questions and comments but nothing blocking.

Comment on lines +67 to +69
:::info
Currently, this portion of the setup requires an Airbyte employee. Contact Support to proceed.
:::
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this correct? Don't the following steps describe a self-serve SSO configuration?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the moment, yeah. People were locking themselves out of their org so we had to shut this down temporarily until we had better validation.

:::

1. In Airbyte, click **Settings**.
1. In Airbyte, click **Organization settings** > **General**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if we want to call out when things require certain roles, but this setup is only visible to Org Admins. Maybe that's intuitive enough that it does not require an explicit mention here 🤷

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made a slight wording change that should make this more clear, but this requirement is established in the introduction of the Okta and Entra ID articles. So I think we're good here.

If you want Airbyte to notify you of source schema changes, enable the following notifications.

To set up email notifications, click **Settings** and navigate to **Workspace** > **Notifications**.
- `Automatic Connection Updates`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be Connection updates, also the capitalization in the table vs. the items in this list is inconsistent. In the UI we capitalize all words, e.g. Connection Updates Requiring Action

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

If these are off, even if you turned on schema update notifications in a connection's settings, Airbyte won't send notifications about schema changes.

![](./assets/notifications-email.png)
To edit this setting, click **Connections** and select the connection you want to receive notifications for. Click the **Settings** tab on the Connection page. In the **Advanced Settings**, toggle **Schema update notifications**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is named slightly different in the connection advanced settings:

image

## Step 1: Create an Application

While logged into the Airbyte UI, go to the `settings/applications` page, then create an application to get a pair of `client_id` and `client_secret` credentials. This can be exchanged anytime to get an access token to make requests to the API. These credentials do not expire, but may be deleted at any time.
1. In the navigation bar, click your user name > **Applications**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this needs to be your user name > **User settings** > **Applications**

image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you. Fixed.


Self-Managed users must manually update the connector image in their local registry before proceeding with the migration. To do so:

1. In the navigation bar, click **Workspace settings** > **Sources**/**Destinations**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In SME we actually have the source/destination pages under Organization Settings:

image

I think the rationale is that in SME, connector updates affect all workspaces, so it makes more sense to have them at the org level. In OSS, users only have a single workspace (and no organization settings) so we have to put it in the workspace settings. In Cloud, workspaces can have their own connector version overrides, so it makes sense to keep connector versions there.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did not realize this. Thank you!

- In Airbyte, go to **Settings** > **User Settings** > **Cookie Preferences**.
- On Airbyte's website, click **Cookie Preferences** in the footer of our [homepage](https://airbyte.com).
- In the navigation bar, click your user name > **Cookie Preferences**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again here you need to click your user name, then "User settings", then "Cookie Preferences". Not sure if you intentionally left out that middle step or not.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, just an omission. Thanks for catching it.

You can create, manage, and delete workspaces, and control access to them.

## Add users to your workspace
## Create a new workspace
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be worth noting that you need an Organization Editor or Organization Admin role to do this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added the role requirements for each action.

Comment on lines +377 to +383
{
type: "category",
label: "Organizations and workspaces",
link: {
type: "doc",
id: "organizations-workspaces/readme",
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the Vercel deploy preview supposed to be showing the latest commit? It seems like it should, but I'm seeing this:

image

...which looks like an old version.

https://airbyte-docs-cfep36vq6-airbyte-growth.vercel.app/platform/

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah.

My guess is you might be viewing the 1.8 docs (you can see this in the version switcher in the nav bar).

https://airbyte-docs-py1nbmbqz-airbyte-growth.vercel.app/platform/next/organizations-workspaces/ should show the latest one.

Copy link
Contributor

@joeykmh joeykmh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Left some comments, but nothing blocking

…tead of a link.

The UX in the app requires the user to click a link to get to the migration page, so we judged it a bad experience to then immediately ask them to go to another page again. This way still allows for a reusable set of text that can be easily updated, but the end user UX is less demanding.
Copy link
Contributor Author

@ian-at-airbyte ian-at-airbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All review comments have been addressed and/or responded to. Thank you!

Comment on lines +377 to +383
{
type: "category",
label: "Organizations and workspaces",
link: {
type: "doc",
id: "organizations-workspaces/readme",
},
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah.

My guess is you might be viewing the 1.8 docs (you can see this in the version switcher in the nav bar).

https://airbyte-docs-py1nbmbqz-airbyte-growth.vercel.app/platform/next/organizations-workspaces/ should show the latest one.

Comment on lines +67 to +69
:::info
Currently, this portion of the setup requires an Airbyte employee. Contact Support to proceed.
:::
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the moment, yeah. People were locking themselves out of their org so we had to shut this down temporarily until we had better validation.

:::

1. In Airbyte, click **Settings**.
1. In Airbyte, click **Organization settings** > **General**.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made a slight wording change that should make this more clear, but this requirement is established in the introduction of the Okta and Entra ID articles. So I think we're good here.

If you want Airbyte to notify you of source schema changes, enable the following notifications.

To set up email notifications, click **Settings** and navigate to **Workspace** > **Notifications**.
- `Automatic Connection Updates`
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

- In Airbyte, go to **Settings** > **User Settings** > **Cookie Preferences**.
- On Airbyte's website, click **Cookie Preferences** in the footer of our [homepage](https://airbyte.com).
- In the navigation bar, click your user name > **Cookie Preferences**.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, just an omission. Thanks for catching it.

You can create, manage, and delete workspaces, and control access to them.

## Add users to your workspace
## Create a new workspace
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added the role requirements for each action.


Self-Managed users must manually update the connector image in their local registry before proceeding with the migration. To do so:

1. In the navigation bar, click **Workspace settings** > **Sources**/**Destinations**.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did not realize this. Thank you!

@ian-at-airbyte
Copy link
Contributor Author

Just need approval from @katmarkham or @tybernstein as code owners and then I think we're good to merge.

@ian-at-airbyte ian-at-airbyte merged commit 93fb9f4 into master Sep 25, 2025
30 checks passed
@ian-at-airbyte ian-at-airbyte deleted the docs-orgs-and-workspaces branch September 25, 2025 20:52
matteogp pushed a commit that referenced this pull request Oct 10, 2025
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants