> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/portal-overview/setup-categories.md). # How to Set Up and Use Categories Categories and subcategories control how members browse and filter content on the Member Portal. They let your team segment large datasets — event programming, blog posts, directory cards — into manageable groups, and they give members a simple way to narrow down what they see (for example, filtering Dining by *Fine Dining* or *Casual Dining*). ### Before you begin (Prerequisites) * **Permissions**: Administrator or Supervisor. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md). * **Portal version**: This guide describes the new Portal 3.0 category model. If you are still on the legacy portal, contact your Account Manager or Support Team about upgrading. ### What are categories and subcategories? A **category** is the parent. There is one main category associated with each activated module (Dining, Spa, Events, Blogs, Club Benefits, and so on). The main category and its module are set up during onboarding, so the parent you need usually already exists. A **subcategory** sits under a parent category. Subcategories are what become the visual sub-navigation on each module page — the row of sub-filters members tap to narrow a listing. Each subcategory ties to a parent category, and content assigned to that subcategory appears under its sub-filter on the matching page. The relationship runs top to bottom: **Module → Parent Category → Subcategory → Directory Card (or other content)** For example, on the Club Benefits page: * **Module**: Club Benefits * **Parent Category**: the main Club Benefits category (set during onboarding) * **Subcategory**: *Amenities* * **Content**: a Directory Card such as *Library* assigned to *Amenities* The same pattern applies to other modules — each subcategory groups the Directory Cards or schedulers assigned to it. > **Note**: Most main categories and subcategories are built during a client's onboarding. Because the module is already activated, you typically won't need to create a new parent category. Use this page when you want to add a new sub-navigation / sub-filter, or edit an existing title. ### How categories show up in the portal On the Manage Categories page, each main category displays the underlying module in parentheses, to the right of the title your team has given it. For example, if the Restaurants module is activated and titled *Dining*, the category appears as **Dining (Restaurants)**. Other examples you may see include *Amenities (Club Benefits)* or *Casual Dining (Restaurants)*. On the member side, subcategories appear as the sub-navigation / sub-filter row at the top of a module page. Selecting a sub-filter narrows the listing to the content assigned to that subcategory. On mobile devices, the sub-filter row scrolls horizontally. ![Member portal preview — categories and sub-navigation](/files/IcuWW94E5QMx2ZLFYY4Z) In this example, **Dining** is the parent category (the module, shown in the left-hand nav and as the page title), and **Book a Table** and **Private Dining** are its subcategories — the sub-navigation tabs members use to filter the module's content. ### How to set up a subcategory Each subcategory requires three primary settings: **Specific Component**, **Parent Category**, and **Order**. 1. Open the **\[Company Name]** dropdown (top-left corner) and select [**Data & Tagging > Manage Categories**](https://control.peoplevine.com/admin_categories.aspx). > **Note (Pro Dash):** Open the **\[Company Name]** dropdown and select **Tagging > Manage Categories**, or **Tagging > Setup New Category** to start a new one. 2. Click **CREATE A CATEGORY** (or open an existing category to edit it). 3. Enter the subcategory **Category Name** (e.g., *Fine Dining*). 4. Set the **Specific Component** to match the module: * Blogs → **Content** * Events → **Events & Promotions** * All other pages (Dining, Spa, Appointments, Activities, Workspaces, Staff Directory, Club Benefits) → **Directory Location** 5. Set the **Parent Category** for the page where this subcategory should appear: | Portal page | Parent Category | | -------------- | --------------------- | | Blog | *My Club* or *Blogs* | | Dining | *Restaurants* | | Events | *Events & Promotions* | | Club Benefits | *Club Benefits* | | Rooms | *Meeting Rooms* | | Appointments | *Appointments* | | Spa & Wellness | *Spa & Wellness* | | Directory | *Club Directory* | 6. Set the **Order** value. Order controls the left-to-right display of subcategories on the module page. Use whole numbers starting at `0` and increment by `1` (e.g., 0, 1, 2, 3). 7. Save the subcategory. #### Example — Fine Dining under Restaurants If you create a *Fine Dining* subcategory with Parent Category = *Restaurants*, it appears on the Manage Categories page as **Fine Dining (Restaurants)**. Any Directory Card you assign to Fine Dining shows under the **Dining** module on the portal, filtered by the *Fine Dining* sub-filter. ### How to assign directory cards and other content Once subcategories exist, attach content to them so it appears on the portal under the right sub-filter. #### Assign a Directory Card 1. Open the Directory Card in [**ENGAGE > View Directory**](https://control.peoplevine.com/admin_businesses.aspx). > **Note (Pro Dash):** Navigate to **SELL > View Directory**. 2. In the card's **Settings** section, set **Assign to a Category** to the subcategory you created (e.g., *Fine Dining (Restaurants)*). 3. Set the **Order #** to control where the card sorts within the subcategory (ascending from 0). 4. Save the Directory Card. It now appears on the matching module page under the chosen sub-filter. For full Directory Card setup, see: [How to Set Up Directory Profiles](/products/portal-overview/setup-directory.md). #### Assign events and blog posts * **Events**: create the subcategory with Specific Component = **Events & Promotions** and Parent Category = **Events & Promotions**, then assign the event to that category so it filters under the matching sub-filter on the Events page. * **Blog posts**: create the subcategory with Specific Component = **Content** and Parent Category = **My Club** or **Blogs**, then assign the post to that category. See: [How to Create a Blog Post](/products/portal-overview/create-blog-post.md). ### Best Practice * **Keep subcategory Order values unique within a module** so the display order is predictable. * **Limit subcategories** per module to what members will realistically use as sub-filters. * **Match subcategory titles to how members talk** about the experience (e.g., *Fine Dining* instead of *FD-Tier1*). ### What Happens Next * **On the member side**: members on the relevant module page see a sub-navigation row matching your subcategories. Selecting a sub-filter narrows the listing to content assigned to that subcategory. * **Next step**: [What are Directory Profiles](/products/portal-overview/directory-profiles-overview.md) · [How to Set Up Directory Profiles](/products/portal-overview/setup-directory.md) · [How to Create a Blog Post](/products/portal-overview/create-blog-post.md). *Last updated: 2026-06-11* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.peoplevine.com/products/portal-overview/setup-categories.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.