# Modules

> The module is a space's type. From Feed to Time Tracking, what each one does, who creates content in it and when to use it.

The **module** is the type of a [space](/conceitos/espacos). It decides the screen members see, what gets created inside the space and who can create it. Each space has **one** module, chosen in the first step of **Add Space**.

<div class="flow">
<div class="flow-row"><span class="flow-node">Section</span><span class="flow-arrow">→</span><span class="flow-node">Space</span><span class="flow-arrow">→</span><span class="flow-node">Module</span><span class="flow-arrow">→</span><span class="flow-node">the screen and the items of that type</span></div>
</div>

## The modules

| Module | On screen | What gets created inside | Who creates (minimum) | Good for |
|---|---|---|---|---|
| [Feed](/espacos/feed) | **Feed** | Statuses, with comments and reactions; also shows content, events, courses and calls from the spaces the person sees | Member | Community conversation, a class board |
| [Content](/espacos/conteudo) | **Content** | Text, image or video posts, each with its own page | Member | Articles, guides, long announcements, a blog |
| [Events](/espacos/eventos) | **Events** | Online, in-person or hybrid events, with RSVPs and broadcast | Moderator | Live sessions, workshops, meetups |
| [Courses](/espacos/cursos) | **Courses** | Courses with modules and lessons | Admin | Training, learning paths |
| [Gallery](/espacos/galeria) | **Gallery** | Images, with reactions | Member | Event photos, portfolio |
| [Engagement](/espacos/ranking) | **Engagement** | Nothing: shows the points leaderboard | — | Rewarding who takes part the most |
| [Link](/espacos/link) | **Link** | Nothing: opens an external address | — | A form, a chat group, a website |
| [Call for papers](/espacos/chamada-de-trabalhos) | **Call for papers** | Calls for papers and talk proposals | Admin | Events with speakers |
| [Store](/espacos/loja) | **Store** | Nothing: lists products to buy | — | Selling courses, tickets, materials |
| [Certificates](/espacos/certificados) | **Certificates** | Templates and certificates issued to members | Administrator (or the team, per **Who issues**) | Courses, training, events |

The **Surveys** module, on the **Community** tab: questionnaires in sections, with NPS and results, identified or anonymous. The audience is whoever has access to the space, who gets an invitation by email when the survey opens; an optional public link takes answers from people without an account. The space is **One survey** (opening it goes straight to it) or **Several surveys** (a list). Who creates: owner or admin. See [Surveys](/espacos/pesquisas).

The **Forms** module, on the **Community** tab: collects data from members and, if the team allows it, from anyone with the link, with privacy consent, an e-mail to the responsibles on each submission and the submissions list with status and CSV; optionally, it saves whoever submitted as a member, with a tag. The space is **One form** or **Several forms**. Who creates: whoever the space's **Who can post** allows. See [Forms](/espacos/formularios).

The **Channel** module, on the **Community** tab: the group conversation in real time, with the newest message at the bottom, threads, reactions with any emoji, mentions, photos and video. One space is one channel; who writes is the space's **Who can post**, and whoever can't only reads and reacts. Who creates the space: owner or admin. See [Channel](/espacos/canal).

The **Upvote** module, on the **Community** tab: a board where members propose topics, vote (one vote per person, retractable) and comment, and the staff changes each one's state (Planned, In progress, Done, Archived with a reason) and merges duplicates. One space is one board; in a public space, anyone reads. Who creates the space: owner or admin. See [Upvote](/espacos/upvote).

The **Classifieds** module, where members post ads for jobs, services or items for sale and others show interest (no payment on the platform). See [Classifieds](/espacos/classificados).

The **Downloads** module, which shares files (spreadsheets, e-books, PDFs, templates) in a repository or as a single file, free, sold through a product or included in the plan. Who creates: the team, or members, if the owner or the admin allows it. See [Downloads](/espacos/downloads).

The **Podcast** and **Videos** modules, in the **Community** tab: audio or video shows with episodes, chapters, their own player, a queue, resuming on any device, transcripts and numbers. The space is **One show** or **Several shows**. Who creates shows: owner or admin; who publishes the episodes: them and each show's presenters. See [Podcast](/espacos/podcast) and [Videos](/espacos/videos).

The **Attendance** module, on the **Coworking** tab, which records who is in the physical space: members tap **I've arrived** and **I'm leaving**, the team sees who's here and registers guests, and a kiosk on the front desk iPad welcomes guests with no login. Who creates the space: owner or admin. See [Attendance](/espacos/presenca).

The **Parcels** module, on the **Coworking** tab, which records the letters and packages arriving at the physical space: the team registers them with a photo and place, the member is notified by email and confirms the pickup. Who creates the space: owner or admin. See [Parcels](/espacos/encomendas).

The **Visitors** module, on the **Coworking** tab, linked to an Attendance space: the member registers the guest ahead of time, the front desk marks the arrival with a notice to the host and the kiosk recognizes whoever is expected. The guest is not a member and doesn't count toward the plan. Who creates the space: owner or admin. See [Visitors](/espacos/visitantes).

The **Support** module, on the **Coworking** tab: the resident opens maintenance tickets or requests (with category, room or place and photos), the team triages, assigns, answers and resolves, with an expected time per category and internal notes the resident never sees. Who creates the space: owner or admin. See [Support](/espacos/suporte).

The **Bookings** module, on the **Coworking** tab, where members book rooms, desks and stations paying in [credits](/monetizacao/creditos), with search, rescheduling, maintenance blocks and a calendar invite by email. Who creates the space: owner or admin. See [Bookings](/espacos/reservas).

The **Recognition** module, in the **Planning & HR** tab: a wall where a member publicly recognizes 1 to 20 colleagues, with an optional community value, reactions, comments and engagement points. A community can have several. Who creates the space: owner or admin. See [Recognition](/espacos/reconhecimento).

The **Feedback** module, in the **Planning & HR** tab: give, ask for and answer feedback between colleagues, in **Received**, **Sent** and **Requests**. Only the giver and the recipient read the text; the team sees only the numbers. A community can have several. Who creates the space: owner or admin. See [Feedback](/espacos/feedbacks).

The **Development Plan** module, in the **Planning & HR** tab: each person builds their development plan, with actions and due dates, and sends it to their direct leader, who approves it or returns it with a note; the leader follows the team and the management team sees the dashboard per leader. One active plan per person in each space; a community can have several. Who creates the space: owner or admin. See [Development Plan](/espacos/pdi).

The **Performance review** module, in the **Planning & HR** tab: 90°, 180° or 360° performance review cycles, with self-review, manager, peers and direct reports, progress tracking, the rating calculated on closing, the team's results for the leader and each person's after the release. One cycle or several per space. Who creates the space: owner or admin. See [Performance review](/espacos/performance-review).

The **Goals & OKRs** module, in the **Planning & HR** tab: goals cycles with company, group and personal objectives, aligned in a tree, key results of four types with a weight and an owner, check-ins with a status light and the check-in reminder. One cycle or several per space. Who creates the space: owner or admin. See [Goals & OKRs](/espacos/metas-e-okrs).

The **1:1** module, in the **Planning & HR** tab: the recurring series of meetings between a direct leader and a direct report, with an agenda owned by both, shared or private notes, agreements that can go to the Development Plan and the history; HR and the indirect leader see only the adherence. Who creates the space: owner or admin. See [1:1](/espacos/1-1).

In the **1:1** module, **Log 1:1** keeps the 1:1 that happened (or will happen) with your direct leader or a direct report, with topics, notes and agreements, and the history by person; the owner and the admin read every pair's 1:1s, read only and never anyone's private note. The indirect leader keeps only the adherence.

The **Time Tracking** module, in the **Planning & HR** tab: employees clock in and out in the app, with the server's time, and get a receipt; nothing that was punched can be changed; the direct leader handles missing punches through adjustments; the management team (owner, admin and finance) sets the rules, closes the month with the timesheet and generates the CSV, the AFD and the AEJ. Each space points to an establishment (the employer); a community can have several. Who creates the space: owner or admin. See [Time Tracking](/espacos/controle-de-ponto).

The **Networking** module, on the **Community** tab: people join the program (directly or with approval), offer to talk, get found in **Explore** and booked at a time on their schedule, always free; afterwards, both say how it went and review each other, and sessions earn points. Four models (community mentoring, company mentoring, business connections, event networking) and Custom. Each space is a program. Who creates the space: owner or admin. See [Networking](/espacos/networking).

The **Scheduling** module, where members book time with a person in the community (mentoring, class, appointment), for free or in credits. Who creates the space: owner or admin. See [Scheduling](/espacos/agendamento).

"Who creates (minimum)" is the minimum role for that item type. The space's **Who can post** rule can tighten this, never loosen it: a Content space set to **Staff** only lets the staff publish. See [Roles and permissions](/conceitos/papeis-e-permissoes).

The **Add Space** window sorts the modules into five tabs: **Community** (Content, Engagement, Feed, Link, Gallery, Surveys, Forms, Upvote, Channel, Networking), **Events & Courses** (Events, Courses, Certificates, Call for papers), **Sales** (Store, Downloads, Classifieds), **Planning & HR** and **Coworking** (Bookings, Scheduling, Attendance, Visitors, Parcels, Support). The **Planning & HR** tab shows the extension modules: **Performance review**, **Feedback**, **Goals & OKRs**, **Time Tracking**, **Development Plan**, **Recognition** and **1:1**.

The modules on the **Planning & HR** and **Coworking** tabs depend on the Memberfy plan. Without the extension in the plan, the tab shows a lock and **Get the extension**. See [Plan and extensions](/configuracoes/plano#extensions).

## How to choose

| I want… | Module |
|---|---|
| People to talk, with short posts | Feed |
| To publish texts that stay, with a cover and tags | Content |
| A calendar with RSVPs | Events |
| Lessons in sequence, with progress | Courses |
| A photo album | Gallery |
| A questionnaire with NPS, identified or anonymous | Surveys |
| To collect requests and contact details, with a submissions list | Forms |
| To show who takes part the most | Engagement |
| To praise colleagues publicly | Recognition |
| Feedback between colleagues that only the two read | Feedback |
| A development plan per person, approved by their leader | Development Plan |
| Record employees' clock-in and clock-out, with a timesheet and month closing | Time Tracking |
| A shortcut to something outside the community | Link |
| To receive and review talk proposals | Call for papers |
| To sell one-time products | Store |

## Common combinations

**Course community.** **Start here** section: Content (welcome, Public). **Student area** section (private, by plan): Courses, the class Feed, Events (the live sessions), Engagement.

**Coworking.** **Announcements** section: Feed with **Who can post = Staff**. **Residents** section: Events (the house calendar), Gallery, a Link to the room booking form.

**Company HR.** **Announcements** section: Content (Staff). **Training** section: Courses. **Culture** section: an open Feed, Gallery and Engagement.

**Annual event.** **Conference** section: Call for papers, Events (the program), Content (practical information), Gallery (photos afterwards).

## Can I change the module later?

The edit screen shows the **Module Type**, but changing the module of a space that already has content doesn't convert anything: items of the old type stop showing on the new screen (the events in an Events space don't turn into Feed posts). Choose carefully when you create it. If you change your mind, create another space with the right module and move the conversation there.

## Frequently asked questions

**How many spaces of the same module can I have?**
As many as you like. It's common to have several Feeds and several Content spaces, each with its own audience. Recognition and Feedback can have several too, for example one per team.

**Does the Feed show what's published in the other modules?**
Yes. Content, events, courses and calls appear in the Feed of whoever can see them, with filters by type.

**Why don't members see the create button in my Events space?**
Creating events is for moderators and above, in any space.

**Does the Link open in a new tab?**
Yes. It always opens the external address you configured in a new tab.

## In the API

The module is `space.module`: `feed`, `content`, `events`, `courses`, `gallery`, `ranking`, `url`, `call4papers`, `certificates`, `storefront`, `downloads`, `classifieds`, `surveys`, `bookings`, `scheduling`, `attendance`, `visitors`, `parcels`, `support`, `recognition`, `feedbacks`, `developmentPlan` or `timeTracking`. The catalog, with each one's category (`community`, `learning`, `sales`, `people` or `coworking`, in tab order) and availability, comes from `GET /api/spaces/modules`. See [Sections & Spaces](/api/referencia/sections-spaces).

## Related

- [Spaces](/conceitos/espacos)
- [Sections](/conceitos/secoes)
- [Create and organize spaces](/espacos/criar-e-organizar-espacos)
