> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gettap.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Core concepts

> The eight objects that everything else in Tap is built from.

Tap's settings screens assume you know this vocabulary. Reading this page once will save you guessing at what a screen is asking for.

## Profile

A **profile** is one shareable identity: a name, photo, title, company, and a set of links. It is the thing a visitor sees after a tap or scan.

A member can hold more than one profile — for example one for their main role and one for a specific trade show — and switch which is active. Profiles carry their own view counts and tap counts, so you can tell which one is actually doing work.

<Note>
  A profile is not the same as a member. A member is a person with a login; a profile is one of the identities that person shares. Deleting a profile does not remove the member.
</Note>

## Link

A **link** is one row on a profile: a phone number, an email, a LinkedIn URL, a PDF, a payment link, a WhatsApp handle. Each link has a **link type** that decides how it renders and how it behaves when tapped.

Links can be grouped into **link groups** so a profile can present, say, all its social accounts together. Admins can restrict which link types a department is allowed to add — see [Department permissions](/en/teams/department-permissions).

## Connection

A **connection** is a person your team member met and captured. It is created when someone submits a lead capture form, when a member saves a contact manually, or when a card is scanned.

Connections can be filed into **connection groups** and labelled with **tags**. In Tap Teams the same records appear under **Leads** — connection is the underlying object, lead is what the dashboard calls it.

## Lead capture form

The **lead capture form** is what a visitor fills in after landing on a profile. Each field has two parts that matter:

| Part | What it is |
| - | - |
| `label` | The human-readable text the visitor reads. Change it freely. |
| `name` | The stable machine key the answer is stored under, and the key your CRM mapping points at. |

Renaming a label is safe. Changing a `name` breaks any CRM mapping pointing at the old key. This distinction is the single most common source of "why is this field empty in HubSpot" — see [Lead capture forms](/en/leads/lead-capture-forms).

## Template

A **template** is a profile blueprint an admin publishes. It fixes the layout, branding, and a starting set of links so every member's profile looks like it came from the same company.

Templates can also carry their own lead capture fields. When a profile uses a template that defines capture fields, those fields win over the member's own form.

## Department

A **department** is a group of members inside your company — Sales, Field Marketing, EMEA. Departments exist to carry permissions rather than just to organize the member list.

A department can control which profile fields its members may edit, which link types they may add, which CRMs they can reach, and whether they get location features.

<Warning>
  Department permissions default to **full access**. A department with no restriction rows saved lets its members do everything. Restrictions only start applying once you explicitly save them.
</Warning>

## Meeting

A **meeting** is a recorded conversation attached to a lead. Tap transcribes the audio, then extracts a summary, topics, objections, sentiment, and action items from the transcript.

Meetings consume **minutes**, which are drawn from your plan's entitlement. See [Transcription](/en/leads/transcription).

## Tag

A **tag** is a free-form label you attach to leads to slice them later — event names, product interest, priority. Tags are defined once at the team level and then applied to any number of leads.

***

## How they fit together

```mermaid theme={null}
flowchart LR
    T[Template] -->|shapes| P[Profile]
    P -->|holds| L[Link]
    D[Department] -->|restricts| P
    D -->|restricts| L
    P -->|visitor submits| F[Lead capture form]
    F -->|creates| C[Connection / Lead]
    C -->|labelled by| TG[Tag]
    C -->|has| M[Meeting]
    M -->|feeds| I[Insights]
    C -->|syncs to| CRM[(CRM)]
    M -->|syncs to| CRM
```

<Card title="Next: plans and limits" icon="arrow-right" href="/en/getting-started/plans-and-limits">
  How quotas, minutes, and entitlements are enforced.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.