What is the best way to set up multitenancy on open-source Airbyte? By multitenancy I mean several groups will have access to Airbyte to create their own ingest pipelines but shouldn’t be able to see sources/destinations/connections/logs other than their own. Do workspaces help with this? I don’t see workspaces mentioned much in the documentation (although I see them in the API reference.)

@Ashley Baer Did you find an answer? Edit: I see now on Discourse, you can add workspace through the API and switch workspaces using the URL (but not manageble in the UI as in Airbyte Cloud).