[Workspace] How to handle with global object across workspace

[SuZhou-Joe]

Is your feature request related to a problem? Please describe.

We are introducing workspace to manage saved objects and enhance them with permission control. But there are some objects supposed to only exist out of workspace. Advanced settings for example, under the hood it is a saved object whose id consist of config:${OSDVersion} and stands for application settings for the entire OSD.

But as we are introducing workspace, and workspace will regard all saved objects as workspace objects by default, which means those "global objects" will be created inside a workspace accidentally. And it will break some features, for example, if the advanced settings is created accidentally inside a workspace foo, and the owner of the workspace someday decide to delete the workspace, all the related objects inside the workspace, including the advanced settings, will be deleted as well.

Describe the solution you'd like

Option A: Prevent user from visiting global-objects-related pages in browser side.

description: We can limit user from visiting the related pages and thus user is not able to create those objects inside workspace by using OSD Web UI.
pros:

• Less effort to implement
  cons:
• User can still create the objects by calling OSD APIs.

Option B: Prevent user from creating global objects in server side.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.