# Templates

When everyone on a team should offer the *same* meeting — same duration, same booking
questions, same reminders — you don't want each person rebuilding it (and drifting). An
admin creates a **template**, picks who gets it, and 42min rolls it out to those users
as an event type (or workflow) they can use but not freely edit. Templates are managed
from [**Templates**](/360/templates).

## What it is

- An **event-type template** — a standard event type definition (duration, location,
  [booking questions](/help/event-types/booking-questions), buffers, etc.) created by an
  admin.
- It's distributed to selected users. Each recipient gets it on their
  [Event Types](/360/events) page with their *own* booking link — but because it came
  from a template, its settings are locked, so the meeting stays consistent across the
  team.
- There are **workflow templates** too — the same idea for
  [workflows](/help/workflows/overview): a standard reminder/follow-up set, rolled out
  and kept in sync.
- Editing the template updates everyone's copy, so you fix or change it in one place.

<Screenshot
  src="/help/screenshots/team-and-admin/templates.png"
  alt="The Templates page in the 42min dashboard, where admins create event-type and workflow templates and choose who they're distributed to"
  caption="Templates — create an event-type or workflow template and choose which users it's distributed to."
/>

## When to use it

- A sales team that should all offer an identical "Book a demo" — same length,
  questions, and reminders, just with each rep's own link.
- Onboarding/support calls that must follow a set script of questions.
- Any case where consistency matters more than per-person customization.

## How to do it

1. Open [**Templates**](/360/templates) (admin).
2. Create an **event-type template** (or **workflow template**): set it up the way every
   recipient should have it.
3. Choose which **users** it's distributed to.
4. Recipients see it among their event types/workflows with their own link; if you edit
   the template later, their copies update.
5. Who's allowed to create templates is governed by the
   ["who can create shared events"](/help/team-and-admin/groups-and-permissions)
   permission.

## Common pitfalls

- **Recipient wants to tweak it.** Template-based event types are intentionally locked —
  if one person needs a variant, they should make their own separate event type instead.
- **Template change not reflected.** Edits flow to recipients' copies; if something
  looks stale, re-check the template and that the user is still a recipient.
- **Confusing it with sharing a link.** A template gives each recipient their *own*
  booking link with consistent settings — it's not one shared link (that's a
  [round-robin team](/help/team-and-admin/teams)).