rencore.com (opens in a new tab) Start a trial (opens in a new tab)

Custom metadata

Last updated Inventory

AI summary

Custom Metadata lets you add custom business fields to your inventory, such as cost centers or project codes, then use them across Rencore Governance. You can define custom properties (typed fields), custom objects (new inventories), and custom relations (links between objects). These metadata then appear as filters in Policies and Reports, in Provisioning forms, in reviews, and in Automation actions.

Custom Metadata lets you add your own business fields to the inventory, cost centers, project codes, classifications, anything Microsoft does not track, then use those fields the same way you use any built-in property: to scope a Policy, group a Report, fill in a Provisioning form, or set a value from an Automation.

Custom Metadata is included in the Enterprise Plan and available as an add-on to the Premium Plan.

What you can define

  • Custom properties: A typed field you add to an existing inventory object, for example a Cost Center field on Teams. Choose from five data types: Text, Number, Date, Single select, and Yes-No.
  • Custom objects: A new inventory of your own, for example a list of cost centers or SAP project codes, with its own property schema and its own instances.
  • Custom relations: A link from an object to exactly one instance of another object, for example a Team to its Cost Center, created separately from a Custom Property. The link is visible on both ends.
  • Data sources: A SharePoint file or library that keeps a Custom Object or a property’s values current automatically, refreshed at least every four hours or on demand.

Where you will find it

Every customization you create, on any connector, is listed on one page, Manage your metadata. From there you add, edit, or remove a Custom Property, Relation, Object, or data source, and control whether a property is shown to end users in the Teams App.

Beyond the inventory itself, Custom Metadata shows up across Rencore Governance:

  • In Policies and Reports, as a filter, a group-by field, or an exclusion rule that keeps Automations off objects you mark as protected.
  • In Provisioning, as fields on the request form, so business context is captured when a workspace is created instead of chased down later.
  • In reviews, as a step where the workspace owner fills in or corrects a property.
  • In Automation, through the Set a custom property value action, which writes a value when a lifecycle event happens.

Start with

  1. Create a custom property Add your own field, such as a cost center, to an inventory object.
  2. Connect a data source for custom metadata Keep a Custom Object or a Custom Property current automatically from a SharePoint file or library, refreshed on a schedule or on demand.
  3. Use custom metadata in policies and reports Custom Properties and Custom Relations appear as operands in the Segment, Report, and Policy builders, so you can scope, group, and exclude by the fields you defined.

All guides in custom metadata

See and use your metadata 2 guides

Where your own fields, objects and relations show up, and how to filter on them.

  • Manage your metadata

    Manage your metadata lists every Custom Property, Custom Relation, Custom Object and data source of your Environment…

    Before you begin: Your Rencore role includes the inventory's Edit permission. (+1 more)

    3 steps

  • Use custom metadata in policies and reports

    Custom Properties and Custom Relations appear as operands in the Segment, Report, and Policy builders, so you can…

    Before you begin: Your Rencore role can create the Segment, Report, Policy or Automation you want to use the metadata in. (+2 more)

    3 steps Watch it · 4 min

Add your own fields and objects 3 guides

Create Custom Properties, Custom Objects and Custom Relations.

  • Create a custom property

    Add your own field, such as a cost center, to an inventory object.

    Before you begin: Your Rencore role includes the inventory's Edit permission. (+1 more)

    11 steps Watch it · 4 min

  • Create a custom object

    Add your own object type, such as projects or departments, to the inventory.

    Before you begin: Your Rencore role includes the inventory's Edit permission. (+1 more)

    9 steps

  • Create a custom relation

    Link inventory objects to each other or to your custom objects.

    Before you begin: Your Rencore role includes the inventory's Edit permission. (+2 more)

    9 steps

Keep it current 1 guide

Fill and refresh your metadata from a SharePoint file or list.

  • Connect a data source for custom metadata

    Keep a Custom Object or a Custom Property current automatically from a SharePoint file or library, refreshed on a…

    Before you begin: Your Rencore role includes the inventory's Edit permission. (+3 more)

    10 steps

Frequently asked questions

Which data types can I choose for a custom property?

You can choose from five data types: Text, Number, Date, Single select, and Yes-No. A Custom Property is a typed field you add to an existing inventory object, for example a Cost Center field on Teams.

How often is a custom metadata data source refreshed?

A data source is refreshed at least every four hours, or on demand. It uses a SharePoint file or library to keep a Custom Object or a property's values current automatically.

Where can I see and manage all my custom properties, relations, and objects?

Every customization you create, on any connector, is listed on the Manage your metadata page. From there you can add, edit, or remove a Custom Property, Relation, Object, or data source. You can also control whether a property is shown to end users in the Teams App.

Where can I use custom metadata in policies and reports?

Custom Properties and Custom Relations appear as operands in the Segment, Report, and Policy builders. You can use them as a filter, a group-by field, or an exclusion rule that keeps Automations off objects you mark as protected.

How can custom metadata be set during provisioning or by an automation?

In Provisioning, custom metadata appears as fields on the request form, so business context is captured when a workspace is created. In Automation, the Set a custom property value action writes a value when a lifecycle event happens.