Team Pages
A `/team/<slug>` landing page that lists every member's booking links — for departmental scheduling without sharing one URL.
A team page is a single landing route — workestra.app/team/<slug> — that shows every member's available booking links in one place. The visitor picks who they want to meet with; that rep's booking page opens.
It's the right shape when:
- You have a sales team and want one URL for "Talk to sales" that lets the prospect pick their account exec
- You have a customer success team and want a "Talk to CS" page where customers can find their CSM
- You have a board / leadership group and want their public scheduling presence in one place
A team page is not round-robin. Round-robin auto-assigns; a team page lets the visitor choose. Use round-robin when the visitor doesn't care who they meet; use a team page when they do.
Screenshot needed — /team/<slug> with 6 host cards, each with name, photo, role, and a 'See availability' link
Setting one up
Path: /calendar/admin/team-pages → New team page. Admin role required.
| Field | What it does |
|---|---|
| Name | Public-facing team name (e.g. "Workestra Sales") |
| Slug | URL fragment. /team/<slug> — typically sales, cs, partnerships |
| Cover image | Optional banner shown above the host list |
| Description | Short intro shown next to the cover |
| Members | Workspace users to include. Each member's booking links appear under their name. |
| Visibility | Public (anyone can see), Workspace (logged-in members only), or Private (URL-only) |
What the visitor sees
A page with the team name, cover image, and description, then a grid of host cards. Each card has:
- The host's avatar, name, and role (pulled from
user_profiles) - A short description (optional)
- The host's available booking links — title + duration
Clicking a link opens the standard /book/<slug> page for that host.
If a member has no public booking links, their card is omitted. If a link is private, it's omitted too. The team page only shows what a visitor could otherwise reach via direct link.
Members vs roles
The members list controls who shows up. The order in the list controls display order — drag to reorder.
A member's "role" on the team page comes from their workspace profile (e.g. "Account Executive", "Solutions Engineer"). There's no per-team-page role override yet.
Visibility
| Visibility | Who can see |
|---|---|
| Public | Anyone with the URL — surface in your nav, share on social |
| Workspace | Only logged-in workspace members. Useful for internal directories. |
| Private | The URL works, but it's not crawlable, indexed, or referenced from other pages |
The visibility setting affects search engine crawling — public pages emit index, follow; workspace and private emit noindex.
Multiple team pages
A workspace can have many team pages. Common pattern: one per department. A user can appear on multiple pages — alice on both /team/sales and /team/leadership is fine.
Customizing the look
The team page inherits the workspace's white-label config (logo, brand color). Per-team-page color overrides are on the roadmap but not shipped yet.
Read next
- Booking Links — what each card on the team page links to
- Managed Events — give every team member the same link template
- Round-Robin — for "any rep is fine" instead of "let the visitor pick"
- Calendar Dashboard — the admin toolbar links here
Managed Events
Admin-defined booking link templates with section locks, bulk assignment, and propagation — for organizations where consistency matters more than per-rep flexibility.
Conference Rooms & Resources
Book physical rooms, desks, and equipment as part of a meeting — required or optional, calendar-aware, conflict-checked.