From 2a8ddd26f332b604aff498dc49fae45d380902a0 Mon Sep 17 00:00:00 2001 From: Yulong Ruan Date: Tue, 10 Oct 2023 22:09:37 +0800 Subject: [PATCH] Update workspace.md --- docs/plugins/workspace.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/plugins/workspace.md b/docs/plugins/workspace.md index 331f0286f39e..9b311e065a09 100644 --- a/docs/plugins/workspace.md +++ b/docs/plugins/workspace.md @@ -106,6 +106,18 @@ Consider the following example, where a visualization is associated with multipl By allowing saved objects to be linked with multiple workspaces, this enables users to share and collaborate on resources across various workspaces(teams). +## Non-workspace saved objects +While the introduction of workspaces in OSD provides a powerful framework for organizing and managing saved objects, it's +important to note that not all saved objects are necessarily associated with workspaces. Some saved objects, by their +nature or purpose, may exist independently of workspaces. + +For example, the global UI settings object. This object contains configurations and settings that apply globally across +OSD, affecting the overall user interface and user experience. These settings are not tied to any specific workspace +because they are intended to impact the entire OSD. Such objects won't have `workspaces` attribute. + +The coexistence of workspace-associated saved objects and those without workspace association ensures that OSD strikes +a balance between context-specific customization and system-wide consistency. + ## Duplicate saved objects among workspaces While associating saved objects with multiple workspaces links a single object instance to multiple places, duplicating saved objects takes a different approach. When duplicating objects, it creates hard copies of the objects in the target workspace,