Skip to content

Scope models to projects and workspaces

Projects and workspaces are not part of the free edition. A workspace is a selection of catalog tables, so a free organization has nothing for one to hold: its models, entities and glossary live at organization level, under Business in the global rail, and the scoped pages below are not there. See Pricing for what each edition includes.

DeltaVault keeps one business model library for your whole organization, but a project or a workspace rarely needs all of it. Scope a model into a project or a workspace, and that project’s or workspace’s Models and Entities pages show only the models you chose and the entities that hang off them, instead of every model your organization has ever built. This guide covers adding and removing models from a project or workspace, managing that same membership from a model’s own record, and what stays organization-level no matter where you’re working.

Open the scoped Models and Entities pages

Section titled “Open the scoped Models and Entities pages”

The Business group in the left navigation follows your scope. While you are inside a project, its Models and Entities entries open that project’s own scoped pages; inside a workspace, they open the workspace’s. Outside any project or workspace, the same two entries open the organization-level Business > Models and Business > Entities views (see Business entities).

Both scoped pages render the same models grid and entities catalog as the organization-level views, filtered to whatever belongs to that project or workspace. Open, edit, and browse a model or an entity exactly as you would at the organization level: scoping changes which rows show up, not how you work with them.

Add a model to a project or workspace

Section titled “Add a model to a project or workspace”

A project or workspace with no models yet shows “No models in this project yet” (or “No models in this workspace yet”) with an Add models button. Select it, and a panel titled Add models to your project or workspace lists your organization’s models: check the ones you want, and select Add models again to confirm. Parent domains come along automatically, so a model’s domain shows up in the scoped view even though you only picked the model itself.

Once a project or workspace holds models, add more from the model’s own record: open the model, and on its Details tab use Add to project or Add to workspace under Used in projects & workspaces (see Manage membership from the model itself below).

Add a model to a workspace, and DeltaVault adds it to the workspace’s own project too, if it isn’t there already. Workspace membership always implies project membership: a workspace never holds a model its project doesn’t also claim.

Remove a model from a project or workspace

Section titled “Remove a model from a project or workspace”

Open a model’s row menu on the scoped Models page and select Remove from this project or Remove from this workspace.

At the project level, removing a model that one of the project’s workspaces still uses stops short and asks first: a dialog lists every workspace that holds the model or one of its descendants. Confirm, and DeltaVault removes the model from those workspaces in the same step before completing the project-level removal; cancel, and nothing changes. At the workspace level, removal is direct: a workspace has nothing below it, so there’s nothing left to check first.

Manage membership from the model itself

Section titled “Manage membership from the model itself”

You don’t have to be inside a project or workspace to change what it contains. Open any model, and its Details tab carries a Used in projects & workspaces section: every project and workspace the model belongs to, listed under Projects and Workspaces with a Remove button on each row, plus Add to project and Add to workspace pickers. Both ends manage the same membership. Add a model here and it appears on the scoped page; remove it from the scoped page and it disappears from here.

Keep your place as you click through

Section titled “Keep your place as you click through”

Open a model or a domain from a scoped Models or Entities page, and DeltaVault keeps you in that project or workspace instead of dropping you back into the organization-level view. The breadcrumb at the top of the page carries the scope with you, reading Projects › your project › your workspace › Models › your model (a domain reads Domains › your domain instead, and a project-level page drops the workspace segment). As long as the breadcrumb shows your project or workspace, you’re looking at the exact same model or domain the organization-level view shows: you just got there through your own scope instead of the full library.

What stays organization-level

Section titled “What stays organization-level”

Scoping covers models and their entities. A few surfaces don’t have a scoped version, and DeltaVault takes you out of scope on purpose when you click into one, which the breadcrumb confirms: the Business glossary, Map and match source metadata, and the business modeling workshop always work across your whole organization, never one project or workspace at a time.

The scoped Entities page itself carries no add or remove actions: entities follow whichever model they belong to, so managing a model’s membership is what changes which entities you see there. Creating an entity still works from a scoped Entities page, but only into a model already in that scope. Without one selected in the tree, New entity stays disabled, because a scoped view has no Unassigned bucket to fall an entity back into.

That Unassigned bucket, for entities that don’t belong to any model yet, is organization-level only. An unassigned entity belongs to no model, so it belongs to no project or workspace either: it never appears in a scoped Entities page, only in Business > Entities at the organization level.

Section titled “Related guides”