Skip to main content

Project Designer

The Project Designer lets you work within one Project without introducing a new interface. The Designer Workbench home, side panels, and editor tabs remain unchanged.

Open a Project in Designer​

You can enter a Project context in two ways:

  • select Open in Designer from the Project detail;
  • select Open Project in the global Workbench and choose the Project in the side panel.

The Project name appears in the product header, the fixed Workbench tab, and the home page, together with your effective role. Global Workbench removes the context and returns to the cross-Project catalog.

What is restricted​

In the Project Designer:

  • catalogs, recent objects, and Open panels only show objects belonging to the Project;
  • Create assigns the new object to the open Project;
  • Import uses the open Project as its only destination;
  • Export only offers objects from the Project;
  • selectors inside editors, including Workflows, User Views, and Semantic Models, apply the same scope.

You do not need to select the Project again in a panel: the context is already visible and cannot be changed there.

Roles and read-only access​

Owners and Editors can create, import, and edit when the object permissions also allow the operation. A Viewer opens the Project Designer in read-only mode: mutation commands are unavailable and compatible editors open in view mode.

Tabs and switching Projects​

Each Project stores its open tabs separately in the browser session. Tabs from the global Workbench and different Projects are not mixed. Save or close tabs with changes before switching context.

Shared objects​

An object can belong to multiple Projects. The catalog then displays a shared badge. The object is not a copy, so changes are visible in every associated Project.

Manage cross-Project scope and user sharing from the global Workbench. An object associated with multiple Projects must also be archived or deleted from the global Workbench, where its wider impact is explicit. To create an independent variant, clone or import the object as a new copy in the Project.

Imports and dependencies​

Reusable dependencies must belong to the open Project. If a dependency with the same name only exists outside it, Designer requires a copy in the Project instead of linking or overwriting it implicitly.

Exporting every object in a Project as one package is not available. Use the standard export function provided for each object type.