Overriding concepts¶
Sometimes a standard or company-wide concept is almost right, but your team means something slightly different. Overriding lets you change the definition where you need it changed, without touching the shared one everyone else relies on.
Prerequisites¶
Editor role. You override within your own scope: a workspace can override an organization or standard concept; the organization tier can override a standard one.
How an override works¶
Overriding does not edit the shared concept in place. It creates a scoped copy that takes precedence for you and leaves the original untouched.
Start from a shared concept: A standard or organization definition
Override it: Adverity Atlas forks a copy at your tier
Edit the copy: Your change applies only in your scope; the shared concept is unchanged
Because the original is never modified, an override is always reversible: remove it and the inherited definition applies again, exactly as before.
Note
This is why you never “edit” a standard concept directly. Attempting to change a shared concept transparently creates an override at your tier and applies the edit there, the shared definition stays intact for every other workspace and tenant.
Creating one from the concept page¶
Open the concept you want to change. Which buttons you see depends on the tier it belongs to:
Button |
When it appears |
What it does |
|---|---|---|
Edit |
On a concept your scope can change in place |
Opens the edit panel. Editing a shared concept forks it into an override at your tier |
Clone into workspace |
On a shared concept your workspace cannot edit in place |
Creates a workspace-scoped copy and opens it, so you can edit freely |
Promote to organization |
On a workspace-specific concept |
Requests promotion to the organization tier. It does not apply immediately |
Promotion asks for confirmation first: “An admin must approve; on approval this workspace copy is replaced by the shared definition.” While the request is outstanding the concept shows Promotion pending approval instead of the button, and an admin resolves it in Settings > Approvals.
What to override, and what to inherit¶
An override can change as much or as little as you need, the definition, the calculation expression, the synonyms, the aggregation rule. Fields you do not change keep inheriting from the tier above, so a small override stays small rather than becoming a full second copy to maintain.
Precedence¶
An override wins for everyone in its scope, following the usual resolution, workspace beats organization beats standard. See Concept layers for the full precedence rules and an example.
Warning
An organization-tier override applies to every workspace in the tenant. Before changing a shared concept at that level, consider whether the difference is company-wide or belongs in a single workspace. The narrower scope is usually the safer choice.
What’s next?¶
Concept layers, the precedence an override relies on
Adding concepts, the fields an override can change
Approvals, the review step when an override is promoted wider