Properties

A Property is a typed field that records a fact about one asset, such as its risk tier, last-validated date, owning organization, or internal model ID. Tags sort the same assets into shared categories. Each Property is defined once and means the same thing on every asset. Properties live in the same Govern area as the Tag Browser, and defining or changing them requires the CloudAdmin or Librarian role. Asset owners fill in the values.

How it works

Each property definition carries:

A name, which identifies the property on every asset it applies to.
A type, which constrains the values users can enter.
An optional description explaining what the property captures.
An optional group, which keeps related properties together.
A list of applicable assets: Apps, Projects, Project Templates, Datasets, NetApp Volumes, Models, Environments, Policies, and Policy Versions.

A defined property can be set on every asset type listed for it. Properties don’t nest or use Namespaces. Except for the select types, a property accepts any value of its type. Global search matches property values on Projects, Datasets, Apps, Environments, and NetApp Volumes.

Property types

Type	Accepted value
Text	Free-form text
Number	A numeric value
Date	A single date
Boolean	True or false
User	One Domino user
Org	One Domino organization
User or Org	Either a Domino user or an organization
Single select	One value from a predefined list of options
Multi select	One or more values from a predefined list of options

Use Single select for a trait with a fixed set of values, such as a risk tier of Low, Medium, or High.

Set property values

Set and update values from the asset’s overview page. The asset’s owner can do this, as can SysAdmins and CloudAdmins.

Asset	Scope
Apps	Globally on the App, and independently on each version
Projects	The Project. Values appear on the Project card and are indexed by global search
Project Templates	Set at template creation, then carried into new Projects according to the behavior chosen per property
Datasets	The Dataset, shared across all of its snapshots
NetApp Volumes	The volume, shared across all of its snapshots
Models	Globally on the Model, and independently on each version
Environments	The Environment
Policies	The Policy
Policy Versions	The specific version of a Policy, independently of values set on the Policy itself

On Apps, Models, and Policies, a property can hold one value for the whole asset and a separate value on each version.

Carry property values into new Projects

When you create a Project Template, choose one of three behaviors for each property. The behavior decides what each Project created from the template starts with:

Behavior	Effect on the new Project
Copy value	The value on the template is copied into the new Project
Empty (optional)	The property starts empty, and users can fill it in later
Empty (required)	Users must supply a value before the Project can be created

Property values on the template’s Datasets, NetApp Volumes, and Apps carry over to the corresponding assets in the new Project.

Tags: organize the same assets into shared, hierarchical categories.
Knowledge management: how Tags, Properties, and search relate, and when to choose each.

Core Concepts

Features

How it works

Property types

Set property values

Carry property values into new Projects

​How it works

​Property types

​Set property values

​Carry property values into new Projects

​Related

How it works

Property types

Set property values

Carry property values into new Projects

Related