Team Members Collection

Overview

A Team Members collection stores your staff profiles. It is one of the most common collections on any website and serves double duty — displaying profiles on your "About" or "Team" page while also being referenced by blog posts, case studies, and events.

Recommended fields

Required

• Name (text) — the primary field. Full name, used in dropdowns and references.
• Role (text) — job title or position.
• Photo (image) — professional headshot.

Recommended

• Department (select) — design, engineering, marketing, operations, leadership.
• Order (number) — manual sort order for display.
• Bio (rich text) — for team member detail pages.
• Email (email) — contact information.

Optional

• LinkedIn (url) — social profile link.
• Twitter (url) — social profile link.
• Phone (phone) — direct line.
• Start date (date) — when they joined.
• Location (text) — office or city.
• Skills (multi-select) — areas of expertise.
• Featured (boolean) — highlight on homepage.

Display contexts

Card view (team grid)

Most team pages display members as a grid of cards showing photo, name, and role. For this context, you need:

• Name, role, photo, department.
• Optional: email, LinkedIn link.

Detail page (individual profiles)

If team members have their own pages, add:

• Bio (rich text) — full biography.
• SEO title and meta description.
• Social links.
• Related projects or blog posts (via reverse references).

Reference context

When team members appear as authors on blog posts or leads on case studies, only name and photo are pulled. Make sure these fields are always filled in.

Departments: select vs. collection

For most sites, a select field for department is sufficient. Use a separate Departments collection only if:

• Departments have their own pages.
• You need to display department descriptions.
• You want to filter team members by department dynamically.

Relationships

• Blog Posts → Team Members (single reference as "Author")
• Case Studies → Team Members (multi-reference as "Team")
• Events → Team Members (single reference as "Organizer" or "Speaker")
• Departments → Team Members (reverse lookup)

Webflow-specific considerations

Field count budget

Webflow allows 60 fields per collection. A full team member profile with departments, social links, skills, and SEO fields uses about 18-22 fields. That leaves plenty of room, but think twice before adding rarely-used fields.

Slug field

Team member slugs should be auto-generated from the name field. Watch for duplicate names — if you have two "Sarah Johnson"s, Webflow will append a number to the slug. Consider using "first-last-department" as a slug pattern for larger teams.

Collection list limits

Webflow collection lists display a maximum of 100 items per list. If your team has more than 100 members (common in larger organizations), you will need pagination or Finsweet CMS Load to display them all.

Reference field limits

Webflow allows 5 multi-reference fields per collection. If Team Members references Departments, Projects, Blog Posts, Events, and Skills as multi-reference, you have hit the limit. Use single-reference or select fields where possible to conserve multi-reference slots.

Airtable sync tips

When syncing team members from Airtable to Webflow:

1. Photo hosting — Airtable attachment URLs expire after ~2 hours. Trellis caches images in Firebase Storage to ensure they remain accessible in Webflow.
2. Department mapping — if departments is a linked record in Airtable, it maps to a reference field in Webflow. If it is a single select, it maps to an option field.
3. Sort order — Airtable sorts by view; Webflow sorts by field value. Add an explicit "Order" number field for consistent display ordering across both platforms.
4. Rich text formatting — Airtable's long text with rich formatting translates to Webflow rich text, but some formatting (tables, code blocks) may not carry over perfectly. Test with a sample record before syncing all members.

Industry patterns

Nonprofits

Nonprofits often have team members across multiple departments: education, restoration, research, operations, and leadership. Add a Programs multi-reference field to link team members to the programs they lead. Consider a "Years with organization" computed field for tenure display.

Agencies

Agency team pages often highlight individual skills and project portfolios. Add a Projects multi-reference field and a Specialties multi-select field. Consider a separate "Leadership" boolean for partners and principals who should appear first.

SaaS companies

SaaS team pages are often small and focused on building trust. Prioritize photo quality, a concise bio, and LinkedIn links. Skip phone and direct email — funnel inquiries through a contact form instead.

Common mistakes

1. Missing order field — without it, team members display in creation order, which is rarely ideal.
2. Bio on card-only pages — if you only show cards, skip the rich text bio. It wastes content entry effort.
3. Separate "Leadership" collection — use a department filter or "featured" boolean instead. Keeping all people in one collection avoids duplicate profiles.
4. Overloading with social links — most visitors only care about LinkedIn and maybe Twitter/X. Don't add fields for every social platform — it creates a maintenance burden.
5. Not planning for growth — if you have 8 team members now but plan to grow to 80, design for 80 from the start. Add department filtering, pagination support, and a featured toggle now.