From 63684a7e9d761d961bb2cf863353440986eb21bc Mon Sep 17 00:00:00 2001 From: Matthew White Date: Wed, 26 Aug 2026 20:49:47 -0400 Subject: [PATCH] Clarify rules about custom property names --- docs/central-projects.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/central-projects.rst b/docs/central-projects.rst index 88f4e847f..2602cc937 100644 --- a/docs/central-projects.rst +++ b/docs/central-projects.rst @@ -131,7 +131,7 @@ Managing Custom Properties Custom Properties let you control which Entities each App User or Public Link receives. For example, if your organization works across multiple regions, you can create a ``region`` Custom Property, assign each App User a region, and configure an :ref:`Entity List access filter ` so each user receives only Entities from their region. -Go to the :guilabel:`Custom Properties` tab for a project to see the available Custom Properties and add new ones. Custom Property names follow the same rules as form field names or Entity property names: they can't have spaces in them, must start with a letter, and can only contain letters, numbers, _ or -. +Go to the :guilabel:`Custom Properties` tab for a project to see the available Custom Properties and add new ones. Custom Property names follow the same rules as form field names or Entity property names: they can't have spaces in them, must start with a letter or underscore, and can only contain letters, numbers, and a limited set of symbols (``_``, ``-``, and ``.``). Once a Custom Property is defined, assign values to App Users or Public Links. You can then create :ref:`Entity List access filters ` that compare Entity properties with those Custom Properties to determine which Entities each user receives.