Chargeback, agent cost and policy scope, in your own terms
Chargeback by business unit
Report SharePoint consumption grouped by the business unit that owns it, next to the storage those units' licenses entitle them to. Export the two together and each unit's surplus or overage is there to bill against.
Agent and Copilot cost on the right budget
Put cost center, owner and purpose on the workspaces your agents and Copilot users work in, then group Copilot usage and license cost by those fields instead of reading one tenant-level total.
Rules in your own terms
Scope a policy to department teams, client project rooms or a single cost center, because those are fields now rather than naming conventions. Every report, segment, policy and review campaign you already run can be narrowed the same way.
Define the fields your business actually uses
A field goes on any object in the inventory: a Team, a SharePoint site, a user, an agent, a file. Pick the type that fits, including a relation to one of your own objects or to any other object, so you can model your own relationships. You configure it in the product, with no developer and no parallel store to keep alive.
Every field becomes an operand: a filter in a report, a condition in a policy, and the target of a Set Custom Property action.
Your cost centers, clients and projects become part of the inventory
Your business does not run on Teams and sites alone. It runs on cost centers, client engagements, projects and business units. Custom Metadata brings them into the inventory as things you can browse, filter and report on, with every workspace connected to the ones it belongs to.
Each value lives in one place and everything else points to it, so 50,000 project codes stay manageable and one correction fixes every workspace that references it.
Captured at creation, not chased afterwards
Choose per provisioning template which fields a requester sees, which are required, and what your own explanation says next to each one.
It works in the Rencore Teams App, so the person asking for a workspace supplies the business context themselves, inside the flow they already use.
Kept current by the people who own the work
Most of your estate was never created through a form. A custom-properties step inside reviews asks owners only for the values that are missing, and confirms the ones already there.
Run it on its own or append it to a review you already send. The people who know the answer are the ones filling it in.
Fed from where the data already lives
Load values and instances from CSV, with per-row error reporting and a round-trip export, so a correction is a spreadsheet edit rather than a ticket.
The same import runs on a schedule against a CSV at a URL, a SharePoint list or a blob URL, with a wizard for mapping columns. Point it at whatever already holds the truth, SAP, an HR system, a CMDB, a data warehouse, and your lookup tables follow it without anyone maintaining them.
Custom Metadata questions, answered
How does our data get in?
Four ways, and you can mix them. Edit a value by hand on the object itself, which is often all a one-off correction needs. Bulk CSV import for values and instances. A scheduled pull from a CSV at a URL, a SharePoint list or a blob URL, with a column-mapping wizard. And capture at the source, through provisioning forms and reviews. Entra ID extension attributes are ingested automatically, so anything you already maintain there needs no work at all.
Can we put custom metadata on files and folders?
Yes. Wherever Rencore holds files and folders in the inventory, your custom properties apply to them exactly as they apply to workspaces, so a retention class or an owning cost center can sit on a container and on the documents inside it. File and folder coverage is included in Enterprise and available on Premium with the Files & Folders add-on. This is your own business data, defined once and governed the same way across every service, rather than per-library columns you would have to configure and maintain site by site.
Can custom properties drive automations, not just describe things?
Yes, in both directions. A custom property can be the condition that starts a policy or automation, and it can be the outcome: a Set Custom Property action can flag an object as reviewed, exempted or out of policy, and the next policy takes that flag as its trigger. Detect, flag, act, as a chain rather than a set of unrelated rules.
Do the values show up in reports and exports?
Yes, natively, alongside every other property Rencore holds. They are filterable in the inventory, groupable in reports and included in exports, so you can group and sum by cost center, department or project.
Where does the data live?
In Rencore's inventory, alongside everything else Rencore governs, in your chosen hosting region. There is no schema work in Microsoft 365 and no change to how your tenant is configured.
Which plans include Custom Metadata?
Included in Enterprise, available as a paid add-on on Premium. See the pricing page for the full comparison.