# Community welcome

> The screens a new person sees on their first visit (text, video, rules to accept and profile fields), required or skippable mode, who goes through them, and First steps, with up to 6 missions, points, badges and a congratulations at the end.

The **welcome** is the set of screens a new person sees on their first visit, before the community: an introduction, the welcome video, the rules to read and accept, the profile fields the community wants to know. After it come the **First steps**, a card with up to 6 missions (complete the profile, make the first post, go to the first event) that complete themselves through use and can give points and badges.

**Where it is:** in **Settings › Welcome**, for the owner and the admin.

## What it's for

| Community | How it uses it |
|---|---|
| Community with a code of conduct | The first screen shows the rules with **I have read and accept**; nobody gets in without accepting, and the acceptance is recorded with the date and the text |
| Online school | A welcome video that must be watched to the end, and a mission "Complete the opening lesson" |
| Professional community | A screen asks for job title, company and interests (custom fields); the missions lead to the first introduction in the Feed and the first event |
| Open community | Skippable welcome: whoever is in a hurry goes straight in, and the First steps card stays in the Feed |

## Who can

| Role | What they do |
|---|---|
| Owner and admin | Set up the screens, the mode and First steps, and see how many completed, skipped or are pending |
| Moderator and finance | Filter the member list by welcome status; they do not change the settings |
| Member | Goes through the welcome and sees their own First steps card |

The team (owner, admin, moderator and finance) **never** goes through the welcome or sees the First steps card.

## How it works

### The screens

From **1 to 5 screens**, in the order the person will see them. Each screen has:

- **Title** (up to 120 characters) and **text**, with formatting.
- **Video**, optional: **No video**, **Upload a video** (up to 2 GB) or **YouTube or Vimeo link**. Only an uploaded video can have **Continue only after watching to the end**; with an outside link, it cannot be required.
- **Rules**, optional: in **Ask to accept the rules**, the text of the rules, one per line. The person only moves on by checking **I have read and accept the rules**. The acceptance is stored with the date and the text accepted at that moment, even if the rules change later.
- **Profile fields**, optional: up to 20 [custom fields](/membros/campos-customizados) per screen, with the same checks as the profile. A required field must be filled in to move on.

The person sees the screens in order (*Step 1 of 3*), with **Continue** and, on the last one, **Enter the community**; if they leave halfway, they pick up where they stopped. **View as member** shows the screens as a new member sees them, without recording anything.

### The mode

| Mode | What happens |
|---|---|
| **Required** (the default) | The community is blocked until the person completes the last screen |
| **Can skip** | The person sees **Skip the welcome**; whoever skips gets in and is not asked again |

The welcome comes **before** *Complete your registration* (see [Sign-up and access](/membros/cadastro-e-entrada#sign-up)): if a required field is still missing afterwards, the registration window comes next.

### Who goes through it

When you switch the welcome on, you choose whether it also applies to existing members:

- **Unchecked** (the default): only members who join **from now on** go through it.
- **Also apply to existing members**: every member goes through it on their next visit.

Switching it off lets pending people in at once. **Switching it back on does not reach whoever joined while the welcome was off**: the count restarts when you switch it back on, unless **Also apply to existing members** is checked. Whoever already completed or skipped is never asked again.

### First steps

On the same screen, below the screens, the **First steps**: 1 to **6 missions**, each with the text shown on the card (**How it shows on the card**, up to 80 characters) and, in **When the person**, an action the platform already tracks:

| When the person | Done when they… |
|---|---|
| **Completes their profile** | have a photo and every required field filled in |
| **Posts for the first time in a space** | post in the chosen space |
| **Answers a form** | answer the chosen [form](/espacos/formularios) |
| **Registers for an event** | register for an event (**Any event**, or the chosen one) |
| **Completes a course** | complete the chosen course |

- Each mission can give **points** (0 to 10,000, with [gamification](/membros/gamificacao) on) and a **badge** (see [Badges](/membros/engajamento#badges)). Completing them all can give a **final badge** (**Badge for finishing them all**).
- A mission is marked **within about 1 minute** of the action, with nothing for the person to do. The profile one is also checked when the card opens.
- **Anything done before the mission existed does not count.** Changing a mission's action or item also restarts its count; changing only the title, points or badge keeps whoever already did it.
- They apply to members who join after First steps is switched on, or to everyone with **Show to existing members**.

**The card.** The person sees the **First steps** card, with the progress (*2 of 4*) and each mission's points, at the top of the Feed column (even with the widgets off) and on their own member page, after the welcome. When all are done, they see the **congratulations only once**, get the final badge and the card disappears. **Dismiss** hides the card for good, and from then on no mission counts.

### Tracking

The settings show how many members **completed**, **skipped** or are **pending** in the welcome and, for First steps, how many **started** (did at least one mission), **completed** and **dismissed**, with how many did each mission.

In the [member list](/membros/gerenciar-membros), the team uses the **Welcome** filter (**Pending**, **Completed** or **Skipped**). Each member's page shows the team the **Welcome and first steps** block, with the welcome status and the progress in the missions.

### Automate with workflows

Two [workflow](/notificacoes/workflows) triggers in the **Members** block:

- **Completed the welcome**: the person completed the last screen. Skipping does not fire it.
- **Completed the first steps**: the person did every mission, once per person.

Both also reach [webhooks](/api/eventos-de-webhook).

## Step by step

### A welcome with rules and video

*Role: owner or admin.*

1. Open **Settings › Welcome**.
2. On **Screen 1**, give the title *Welcome to the community*, a short text and, under **Video**, **Upload a video**, with **Continue only after watching to the end**.
3. **Add screen**: on **Screen 2**, check **Ask to accept the rules**, write the rules and pick the fields *Job title* and *Company* under **Profile fields**.
4. Under **For the member**, leave **Required**. Turn on **Welcome on** and decide whether to check **Also apply to existing members**.
5. Check it with **View as member** and save.

### First steps with a final badge

1. On the same screen, turn on **First steps** and use **Add mission**: *Complete your profile* (**Completes their profile**, 50 points), *Introduce yourself in the Feed* (**Posts for the first time in a space**, space *Introductions*, 50 points) and *Register for the next meetup* (**Registers for an event**, **Any event**).
2. Under **Badge for finishing them all**, choose *Pioneer*, decide on **Show to existing members** and save.

## Example

Maria joins the community. Before seeing any space, she watches the video to the end, accepts the rules and fills in *Job title*. In the Feed, she finds the card *First steps · 0 of 3*. She completes her profile and posts her introduction: within about 1 minute the card shows *2 of 3* and she has 100 points. The next week, she registers for a meetup, sees the congratulations, gets the *Pioneer* badge, and the workflow with **Completed the first steps** adds her to the *Active members* group.

## Common errors and how to fix them

| Situation | What to do |
|---|---|
| I switched the welcome on and existing members did not go through it | That is the default. Check **Also apply to existing members** |
| I cannot require the video to be watched to the end | Only an uploaded video allows it; with a YouTube or Vimeo link, it does not |
| I switched it back on and people who joined while it was off did not go through it | Switching back on only applies to people who join from then on; check **Also apply to existing members** |
| The mission was not marked | Wait about 1 minute. Check that the action was in the chosen space, form or course, and after the mission existed |
| The profile mission is not marked | The photo or a required profile field is missing |
| The mission gave no points | [Gamification](/membros/gamificacao) must be on |
| I cannot switch it on without a screen (or mission) | You need at least one screen to switch the welcome on, and one mission to switch First steps on |

## Frequently asked questions

**Does the team go through the welcome?**
No. Owner, admin, moderator and finance go straight in and do not see the First steps card.

**Can the person see the welcome again?**
No: after completing or skipping, they are not asked again, even if you change the screens.

**Do I have to mark missions by hand?**
No. Each mission completes itself through use, within about 1 minute.

**Can the member ignore the card?**
They can dismiss it. It disappears for good, and the missions stop counting for that person.

## In the API

`GET` and `PUT /api/welcome/settings` (owner and admin; other roles get 403): the screens (`screens`, 1 to 5, with `title`, `body`, `video` with `mediaId` and `requireFinish` or `url`, `rules.text` and `fieldIds`), `mode` (`REQUIRED`, the default, or `SKIPPABLE`), `enabled` and `applyToExisting`, with `stats` (`completed`, `skipped`, `pending`). First steps goes in the same route: `missionsEnabled`, `missionsShowExisting`, `finalBadgeId` and `missions` (1 to 6, with `kind` `profile_completed`, `first_post` with `spaceId`, `form_submitted` with `formId`, `event_registered` with optional `eventId` or `course_completed` with `courseId`, `title`, `points` from 0 to 10,000 and optional `badgeId`), with `missionStats`. A validation error returns 422 on the field (`screens[0].title`, `missions[1].spaceId`).

For the person themselves (any role): `GET /api/welcome` (the status, `off`, `exempt`, `pending`, `completed` or `skipped`, the current screen and the screens), `POST /api/welcome/progress` (completes the current screen: `step`, `rulesAccepted`, `videoFinished` and `fields`; a screen out of order returns 409) and `POST /api/welcome/skip` (only in skippable mode; otherwise 409). The card: `GET /api/welcome/missions` (`status` `off`, `exempt`, `active`, `completed` or `dismissed`, `visible`, `celebrate`, `done` of `total` and the missions), `POST /api/welcome/missions/dismiss` and `POST /api/welcome/missions/celebrated` (the congratulations were shown).

`GET /auth/me` returns `welcomePending`. `GET /api/members` filters with `welcome=pending|completed|skipped`, and `GET /api/members/{id}` returns `welcome`, with `missions`. The events `member.welcome_completed` (`member`, `completedAt`) and `member.onboarding_completed` (`member`, `completedAt` and `missions`, the number of missions) reach workflows and webhooks. See the [API reference](/api/referencia).

## Through the assistant (MCP)

Ask to see or change the welcome and the missions (*"turn on a required welcome with a rules screen"*): [`get_welcome_settings`](/mcp/ferramentas-membros#get-welcome-settings) and [`update_welcome_settings`](/mcp/ferramentas-membros#update-welcome-settings), which always asks to confirm. Who is pending: [`list_members`](/mcp/ferramentas-membros#list-members) with `welcome: pending`; someone's progress: [`get_member`](/mcp/ferramentas-membros#get-member).

## Related

- [Sign-up and access](/membros/cadastro-e-entrada)
- [Custom fields](/membros/campos-customizados)
- [Gamification](/membros/gamificacao)
- [Engagement and badges](/membros/engajamento#badges)
- [Workflows](/notificacoes/workflows)