Introduction
Public people profiles and booking-provider data. Enabled, bookable, services offered, schedules, and locations affect both the public team section and booking provider choices.
Use Cases
- Introduce the people customers may meet, work with, or want to know about.
- Let customers choose a team member when they book a service with a specific provider.
Supported fields
Basics
- Section label
- Optional. A short label that can appear above or beside the team heading. It is often decorative, but it can also carry a proof point, qualifier, or small trust signal.
- Title
- Recommended. The main heading for the team section. It tells visitors what this part of the page is about before they scan the items underneath.
- Intro
- Optional. Supporting text for the team heading. It gives context before visitors reach the cards, list, gallery, or form below.
- Icon
- Optional. An icon for team templates that include a small visual marker. It can help establish the section theme without requiring a full image.
Team
- Team members
- Multiple team members per site. Each team member is a reusable person profile. The same person can appear in team sections, detail pages, forms, event speaker contexts, booking provider flows, and staff workflows.
- Name
- Required for each team member. The public name of the person.
- Role or title
- Optional per team member. The short subtitle under the person’s name: job title, specialty, credential, department, instructor level, or role.
- Bio
- Recommended for public profiles. Longer profile copy for experience, approach, credentials, personality, or why customers should choose this person.
- Photo
- Recommended; multiple images supported. Team photos are used as the primary visual for cards, carousels, detail pages, and provider-style displays.
- Optional per team member. A direct email address for this person when the business wants profile-level contact data.
- Phone
- Optional per team member. A direct phone number for this person when profile-level contact is appropriate.
- Social links
- Optional; multiple links per team member. Profile-level links such as LinkedIn, Instagram, portfolio, publications, or professional pages.
- Display order
- Optional numeric order. Controls how team members are sorted when a template orders by hierarchy or manual order.
- Show on homepage
- One on/off setting per team member. Controls whether this person should appear in homepage team sections while still allowing them to exist elsewhere.
- Enabled
- One on/off setting per team member. Controls whether the team member appears in public team templates.
- Bookable
- One on/off setting per team member. Allows this person to act as an appointment provider when the booking section is configured for service appointments.
- Working hours
- Optional custom schedule for bookable members. Overrides the default location hours for this provider. Without custom hours, booking flows can fall back to location or booking-section availability.
- Services offered
- Optional; multiple bookable services per provider. Limits which bookable services this team member can provide. If set to all services, the provider can be matched to any currently bookable service.
- Provider location
- Optional when configured. Connects a provider to one business location so booking flows know where that person can accept appointments.
- Bookable provider ID
- Managed automatically. Preserves the provider identity used by booking records when a team member becomes a bookable provider.
Settings
- Enabled
- One on/off setting. Controls whether the team section is rendered on the published site.
- Show on homepage
- One on/off setting. Controls whether team appears on the homepage. Some content can still be used by detail pages, forms, checkout, bookings, or generated pages even when the homepage block is hidden.
- Display name
- Optional. The label used when the team section needs a short name outside its full heading.
Preview
Team examples
These examples use Flax templates with sample content. The selected template controls the final appearance on your site.
Loading examples…