categories within the portal docid\ q195kmiam 00ehin1 drc allow for organisations to strucutre their portal catalogs into logical clusterings, and apply visibility rules and details to drive user experience categories act as the parent to catalog items docid\ bfgj8ynh1hsi8zaeyyopc , creating a taxonomy for self service that becomes visible to end users when navigating the appropriate portal categories can either be directly paired to catalog items, or can include sub categories additional categories to further drive the taxonomy portal taxonomy the options surrounding how you strucutre your portal are endless, however here are a few suggestions to consider business unit centric taxonomy each business unit has it's own category, and relevant sub categories, with bu specific catalog items underneath \ title \[portal categories] \## do not modify the theme variables config theme base themevariables primarycolor '#afd3f0' secondarycolor 'white' \ flowchart td classdef portal fill #fdaa43 classdef subcat fill #02012d, color white class z category z{service portal} z portal > a(accounting) subcat z > b(finance) subcat z > c(it services) subcat a > a1((expense \<br>reimbursement)) a > a2((end of month\<br>summary)) c > ca(end user \<br>compute) subcat c > cb(service &\<br>storage) subcat ca > ca1((request new\<br>hardware)) ca > ca2((report a fault)) capability centric taxonomy instead of dividing by business unit, the taxonomy is structured by capabilities across the organisation \ title \[portal categories] \## do not modify the theme variables config theme base themevariables primarycolor '#afd3f0' secondarycolor 'white' \ flowchart td classdef portal fill #fdaa43 classdef subcat fill #02012d, color white z{service portal} z portal > a(human resources) subcat z > b(customer support) subcat z > c(operations) subcat z > d(marketing) subcat a > a1((employee\<br> onboarding)) a > a2((policy & \<br>compliance)) b > b1((troubleshooting)) b > b2((request for\<br> assistance)) c > c1((logistics \<br>management)) c > c2((vendor \<br>management)) d > d1((campaign \<br>management)) d > d2((social media\<br> monitoring)) category configuration ea ch portal category has the following fields for configuration field label field type purpose name string the name of the category visible to end users when navigating the portal, and indexed for search parent category reference ( optional ) parent field to create a multi level taxonomy of categories key string (optional) unique identifier for advanced scripting active boolean flag to enable or disable the entire category (and it's childen catalog items docid\ bfgj8ynh1hsi8zaeyyopc ) from the portal order integer numerical order of appearance for categories within the parent smallest number will be the first appearing category highlight boolean allows for visual distinction of categories within the portal useful for new offerings or changes to portal taxonomy show items boolean items of subcategories can be shown along with subcategories on a category page summary text summary text of the category this will be used as part of the category display in the portal image attachment image for category this will be used as part of the category display in the portal icon attachment icon for the category used in the portal roles multi reference only users with these roles will have this category available if no roles specified, category is available for all groups multi reference only users who are members of these groups will have this category available if no groups specified, category is available for all entitlement script script complex entitlement rules may be scripted the script should result in a boolean true/false, or set the the answer variable subcategories related list related list of all categories with the current category listed as the parent