Skip to main content

Glossary

Use this glossary to distinguish terms that describe data, presentation, permissions and review. Each definition links to its detailed procedure. French and English names help you recognize both interfaces.

Data and model​

Knowledge base / Référentiel​

All assets maintained by the organization, with their properties and the relationships between them. Inventories present its assets or relationships by type. Visualizations present this information without replacing the underlying assets. Read more.

Asset / Actif​

An element documented in the knowledge base, such as an application or process. Its page contains its properties and relationships. Read more.

Asset type / Type d’actif​

A definition of the kind of element and properties it can contain. Type names and available types depend on your organization. Read more.

Property / Propriété​

A characteristic of an asset or relationship, with a configured value format. A property definition belongs to the metamodel; its value belongs to an asset or relationship. Read more.

Property category / Catégorie de propriétés​

A named group of properties that organizes their presentation in forms and asset pages. It changes neither their values nor their access permissions. It is distinct from categories that organize asset types themselves. Read more.

Calculated property / Propriété calculée​

A read-only value obtained from a formula and its references. Hiding an intermediate calculation in the interface is not a confidentiality rule. Read more.

Unique key / Clé unique​

A property used to identify assets within its type and context. It differs from a display name and from Boldo’s internal asset identifier. Read more.

Relationship / Relation​

A relationship goes from a source asset to a target asset, according to a relationship type. It can carry its own properties. Read more.

Parallel relationships / Relations parallèles​

Several instances of the same relationship type between the same assets, when the type permits them. Each instance has its own identifier and distinguishing properties. Read more.

Metamodel / Métamodèle​

The structure defining asset types, properties and relationship types. Editing that structure differs from filling in an asset’s values. Read more.

Inventories and visualizations​

Inventory / Inventaire​

The list of assets of a type, drawn from the knowledge base. It provides access to asset pages and permitted table edits. Filters change the displayed selection, not stored membership. Read more.

View / Vue​

A saved inventory configuration, such as selected columns and filters. It reuses repository data rather than creating independent asset copies. Read more.

Diagram / Diagramme​

A visual composition of assets, relationships and presentation elements. A visual line is not automatically a stored business relationship. Read more.

Chart / Graphique​

A visualization aggregating values by dimensions. The measure and relationship path determine what a number means; it is not always a count of distinct assets. Read more.

Nested map / Carte imbriquée​

A visualization nesting assets through configured relationship levels. The same asset can appear along several branches. Read more.

Dashboard / Tableau de bord​

A page assembling visualization widgets. Access to the dashboard does not automatically grant access to all underlying content or business data. Read more.

Impact analysis / Analyse d’impact​

A traversal from source assets through configured relationship stages. Propagation, stop and display rules affect different parts of the result. Read more.

Process flow / Flux de processus​

Steps, lanes and transitions maintained inside a flow-enabled asset. The asset type controls whether this process editor is available. Read more.

Context and permissions​

Organization / Organisation​

The environment containing its own model, data, members and configuration. Your account can access several organizations with different permissions. Read more.

User type / Type d’utilisateur​

Owner, Administrator, Editor or Viewer: a member’s level of platform capabilities. Business roles and the plan add further access conditions. Read more.

Role / Rôle​

A set of business permissions applied to a member or connection. An administrative user type does not automatically remove business restrictions. Read more.

Access domain / Domaine d’accès​

A classification used to scope permissions on data or content. A folder’s domains are not a permanent inheritance rule for every descendant. Read more.

Personal and Shared spaces / Espaces Personnel et Partagé​

Catalog locations for folders and visualizations. A personal visualization does not make private copies of the assets it displays. Read more.

Scenario / Scénario​

A context for preparing changes separately from real data or a parent scenario. Comparing, resynchronizing and applying changes are different actions. Read more.

Archive / Archive​

An asset or relationship removed from active data but retained for possible restoration. Archiving and permanent deletion have different consequences. Read more.

Real data and sub-scenarios / Données réelles et sous-scénarios​

Real data is the shared reference repository. A sub-scenario prepares changes from its parent scenario; check the source and destination before synchronizing or applying. Read more.

Resynchronization and application / Resynchronisation et application​

Resynchronizing brings reference changes into a scenario. Applying carries selected scenario changes to its destination. Neither action should be inferred from simply saving a scenario edit. Read more.

Version and activity log / Version et journal​

A visualization version preserves its supported historical state. An asset’s activity log records business events. Deleting an activity entry does not undo the underlying change. Versions and asset history have separate procedures.

Quality and collaboration​

Asset owner / Propriétaire d’actif​

A member responsible for reviewing an asset. Ownership does not grant editing permissions. It is distinct from the organization’s Owner user type. Read more.

Attestation / Attestation​

An explicit confirmation by an asset owner that its information was reviewed. Saving an edit does not automatically attest the asset. Read more.

Freshness / Fraîcheur​

The review state based on attestation, any request for a new attestation and, when the type has one, its revalidation delay. Without a delay, an attestation stays valid until someone requests a new one. Read more.

Request for reattestation / Demande de réattestation​

An explicit request to review an attested asset again, making it stale at once, whether or not its type has a revalidation delay. A new attestation clears the request. Read more.

Completeness / Complétude​

The proportion of counted properties that are filled. Optional, hidden-in-metamodel and calculated properties are excluded. A complete asset can still be inaccurate or stale. Read more.

Suggestion / Suggestion​

A request to create, change or archive data through Boldo’s suggestion feature. It waits for an authorized reviewer to accept it before changing the knowledge base. Read more.

AI proposal / Proposition IA​

An action prepared by the AI assistant in the chat, such as creating a visualization or updating an asset. Review it before applying or dismissing it. Some proposals send suggestions for a separate review instead of changing the data directly. Read more.

A URL giving access to a configured published resource under the link’s permissions and expiration. It is separate from organization membership. Read more.

Connections​

API key / Clé API​

A secret used by a program to call the v1 API for one organization. Its own type and roles combine with its owner’s membership conditions. Read more.

MCP / MCP​

A protocol connecting a compatible external AI client to Boldo through OAuth. Depending on its authorization, the client can read data, send suggestions or write directly. These tools do not create proposal cards in Boldo’s chat. Read more.