member badge
Arunkumar Kumaresan
Content authors currently cannot attach structured metadata to standard Categories in Document360. Custom Fields are available on Articles and Page Categories, but standard Categories (folder-type navigation nodes) do not support this capability. This creates a gap for integrations that organize content at the category level and need to store audience or access metadata alongside the category itself, rather than deriving it from individual articles.
Requested Solution:
  1. Custom Fields should be configurable and retrievable for standard Categories in the same way they are currently available for Articles and Page Categories. Specifically:
  2. Allow custom field definitions to target standard Categories as an entity type.
  3. Expose custom field values on standard Category API responses.
  4. Allow content authors to assign custom field values to standard Categories directly in the Document360 interface.
Benefits:
  1. Content authors can define audience intent at the category level without tagging every article individually.
  2. External platforms can retrieve category-level audience metadata in a single API call rather than aggregating from article responses.
  3. Category-level and article-level audience metadata can coexist, giving teams flexibility in how they model content ownership.
Use Cases: Multi-organization enterprise portals where content is structured by category and each category is owned by a specific organization or department; headless integrations that build navigation from category-level metadata rather than article-level aggregation.