Hi all, I have a question about Parent/Child workspace relationship. Since recent (or maybe not that recent) updates, the children can be configured to have a different datasource than the parent. How does that work? Since the child workspace inherits the layout of the parent, does that mean that the child datasource has to work with the same LDM from the parent or I can treat the child as a separate workspace from the parent, just to be nested visually in the parent workspace?

Hi Goran, The relationship is not just visual—it enforces the same data structure across parent and child workspaces. However, child workspaces can have a different data source than the parent, which allows for tenant-specific data management while keeping the same LDM. Here’s how it works • Shared LDM: The child inherits the parent’s LDM, meaning tables, attributes, and metrics must align. • Different Data Source: The child can be assigned a unique data source (e.g., a different database or schema) while still using the same LDM. • Schema Path Customization: If using the same data source as the parent, the child can define a unique

schemaPath

to point to its own schema. • Not a Separate Workspace: The child is not fully independent; it must respect the parent’s LDM and cannot redefine it. You can find more information here: https://www.gooddata.com/docs/cloud/workspaces/workspaces-layout/#CreateaMultitenantEnvironment-UniqueDataSourcesforTenants

Hi @Julius Kos Thank you for the clarification. It made sense to be like that, just wasn't sure. Thanks