Every workspace collects slightly different information about its members and companies. OfficeRnD's default fields cover the essentials, but if you need to track things like locker numbers, VAT categories, or internal compliance flags, Custom Properties let you add exactly the fields your workflows depend on.
In this article:
Add custom fields to members, companies, resources, and more.
Define the type and format of each custom property.
Control who can view or edit the property: members, admins, or both.
Use custom properties in templates or workflows across OfficeRnD.
Prevent errors by avoiding names that duplicate existing system fields.
How custom properties work
OfficeRnD includes default fields for members, companies, and other entities. Custom Properties let you add fields for anything that isn't there by default: a locker number, a VAT category, an internal policy flag, a vehicle plate number.
Once created, a custom property becomes part of the entity's profile in the Admin Portal. You control the data type, which entities it applies to, and who can see or edit it. Properties can also be referenced in invoice and email templates using their unique identifier.
Add a custom property
To create a custom property in the Flex Admin Portal:
Go to Settings > Data & Extensibility > Custom Properties.
Click Add Property.
Fill in the property details:
Name - Enter a name for the custom property. Avoid naming custom properties after existing fields, such as Invoice number or Description.
Unique Identifier – Generated automatically, but you can edit it before saving. It can't be changed after saving. This identifier is used when referencing the property in templates, for example
{{ customID }}.Type – Choose a data type (string, number, checkbox, date, select, multi-select). You can't change the property type later.
Values – If using “Select” or “Multi-select,” enter the allowed options separated by commas. This allows admins and members to pick one or more of them when editing the property's value.
Applies to – Select which entities this property applies to: members, companies, resources, opportunities, or a combination.
Placeholder – Add a short example or description to guide users in filling out the field. This is not a default value.
Privacy – Choose who can view and edit the property.
Members Public – Members can view and edit their value and make it publicly visible in the portal.
Members Protected – The member can edit the property. However, only the member and the admins can view it.
Admin Only – Оnly the admin team can view and edit the field.
Click Add. The property is created and added to the relevant entity profiles.
Best practices
If you're using custom properties in templates, choose the unique identifier carefully before saving. It can't be edited later, and a typo means deleting and recreating the property from scratch.
If you're creating a Select or Multi-select property, define all possible options up front. Adding options later requires editing the property, which may affect existing records.
If you're collecting sensitive or internal data (such as access tags or compliance flags), use Admin Only privacy so members can't view or edit those fields.
FAQ: Managing custom properties
Can I rename the unique identifier after saving?
No. Once saved, the unique identifier is permanent. If you need a different one, delete the property and create a new one. Deleting a property also removes all stored values for that field, so export any data you need first.
Can I change the property type after saving?
No. The type is fixed on creation. Create a new property if you need a different type.
What's the difference between Members Protected and Members Public?
Members Public means the member can view and edit the property, and it's visible in the Member Portal. Members Protected means the member can edit it, but only the member and admins can see the value.
Can I apply one property to multiple entity types?
Yes. Select all relevant entity types in the Applies to field when creating the property.
How do I reference a custom property in a template?
Use double curly braces with the unique identifier: {{ customID }}. This works in invoice and email templates.
What happens when I delete a custom property?
The property and all stored values are permanently deleted. Export the data before deleting.
Is there a limit on how many custom properties I can create?
There's no hard limit, but adding more fields than you actively use makes profiles harder to manage. Create properties only for what is required in your workflows.
Read next