> 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/directory-profiles-overview.md). # What are Directory Profiles Directory Profiles are your experiences or benefits that don't require a reservation or an action to be taken by the member to utilize a space, service, or policy. Each Directory Card describes one space, service, or experience, and the card type controls what happens when a member taps on it on the Member Portal across modules like Dining, Spa, Appointments, Activities, Workspaces, Staff Directory, and Club Benefits. ### Before you begin (Prerequisites) * **Permissions**: Administrator, Supervisor, Manager, Support, or Account Rep. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md). * **Categories must exist**: Each Directory Card must be assigned to a category to appear under the correct module on the portal. See: [How to Set Up and Use Categories](/products/portal-overview/setup-categories.md). * **Portal version**: Directory Cards as described here apply to the new Portal 3.0 model. ### Where Directory Cards are managed * **Standard Dash**: **ENGAGE > View Directory > Add Profile to Directory** > **Note (Pro Dash):** **SELL > Directory > View Directory**. ### Creating and displaying Directory Cards To display a Directory Card, it must first be created in the Control Panel and assigned to a Category under a Parent Category Group. Every profile must define at least its category or subcategory so it appears under the correct module on the Member Portal. For example, a Spa Directory Card must be assigned to a subcategory under the **Spa** Parent Category to show up on the Spa page. See: [How to Set Up and Use Categories](/products/portal-overview/setup-categories.md). ### The five Directory Card types | Type | Purpose | Typical Use Case | | ------------------------ | ---------------------------------------- | ------------------------------------------------------------------------------------ | | **Informational** | Convey information; no action | Lounge, Pool, Library, Club Benefits page | | **Bookable** | Link one or more Schedulers for bookings | Dining Reservations, Spa Appointments, Workspace Bookings | | **Form** | Connect a Form for inquiries | Private Event inquiry | | **Hybrid** | Combine Schedulers and a Form | Private Dining with Special Requests; Spa services that need a booking + intake form | | **Call-to-Action (CTA)** | Informational with a primary link | External link to hotel booking engine; in-portal page such as Nominate a Member | ### How each type is set up #### Informational Use when the card is purely descriptive and the member does not need to book or submit anything. * Create the card and fill in **Directory Name**, **Slogan/Headline**, **Preview Text**, **Page Content**, **Preview Graphic**, and **Page Banner**. * **Do not attach** a Scheduler or a Form. #### Bookable Use when members need to book a time slot. * Create the Directory Card first. * Create the Scheduler(s) separately. * In the **Scheduler** settings, attach the scheduler to the Directory Card. You can attach **multiple Schedulers** to one Bookable card (e.g., one scheduler per dining table or per spa room). See: [How to Set Up Dining Reservations with Schedulers](/products/control-panel-overview/events-engine-overview/setup-dining-reservations.md). #### Form Use when members need to submit an inquiry or request. * Create the Directory Card first. * Create the Form separately. See: [How to Create a Form](/products/control-panel-overview/forms-overview/create-form.md). * Attach the Form so it presents to the member. **Only one Form can be attached.** #### Hybrid Use when members need both a booking *and* an intake/preferences form (e.g., book a private dining room and submit dietary preferences in the same flow). * Create the Directory Card first. * Create all needed Schedulers and the Form. * Attach the Schedulers from the **Scheduler settings**, then attach the Form. **Only one Form can be attached.** #### Call-to-Action (CTA) Use when the card should send members to an internal page or external URL as the primary action. The link can point to an external site (for example, a hotel booking engine) or to another page inside the Member Portal, such as the **Nominate a Member** page. * Create an **Informational** Directory Card. * In the **Page Content**, type the link text, highlight it, and use the hyperlink icon to paste the URL. * For an external site, set the link **target to "New window"** so it opens in a new tab. An in-portal link, such as Nominate a Member, takes the member to that page within the portal. ### How to pick the right type | Question | Recommended Type | | ----------------------------------------------------------------- | ---------------- | | Members just need to know it exists | Informational | | Members must reserve a time slot | Bookable | | Members must submit info before being contacted | Form | | Members must reserve a slot **and** share preferences in one flow | Hybrid | | Members need a single external/internal link as the action | CTA | ### Best Practice * **Pick the simplest type that fits.** A Hybrid card is more work to maintain than a Bookable + separate Form — only choose Hybrid when the booking and the form belong together in one transaction. * **Use a 16:9 image aspect ratio** for card thumbnails so they render consistently across phones, tablets, and desktops. * **Assign each card to a category** so it appears on the matching module page. See: [How to Set Up and Use Categories](/products/portal-overview/setup-categories.md). * **Attach multiple Schedulers** when a Bookable card represents several resources (tables, rooms, treatment beds) that members can choose between in one search. ### What Happens Next * **On the member side**: The Directory Card appears under its Parent Category on the matching Module page (e.g., a Dining Bookable card appears under **Restaurants** on the Dining page). The member taps the card to view details, book, fill out the form, or follow the CTA — depending on the type. * **Next step**: [How to Set Up Directory Profiles](/products/portal-overview/setup-directory.md) · [How to Set Up and Use Categories](/products/portal-overview/setup-categories.md) · [How to Set Up Dining Reservations with Schedulers](/products/control-panel-overview/events-engine-overview/setup-dining-reservations.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/directory-profiles-overview.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.