October 21, 2026

• Surveys
• Recognition
• Feedback
• New content notices by e-mail
• Development Plan
• Feedback about another person
• Time Tracking

#Surveys

What it is. A new space module for team questionnaires, with sections, up to 100 questions and 5 question types (NPS included). Each survey is identified or anonymous, and the audience is whoever has access to the space; an optional public link takes answers from people without an account, no sign-in needed.

Why it matters. Before, measuring an event's satisfaction or the members' NPS took an outside tool and a spreadsheet to match the answers. Now the survey lives in the community: the invitation goes out by e-mail, and the results show per section, with NPS, filters by group, tag, company or origin, and CSV export. On an anonymous survey, nobody (not the team, the API or the assistant) can link an answer to a person.

Where it is. In the menu, Add Space, Community tab, Surveys module. The space holds One survey (opening it lands right on it) or Several surveys (a list).

How to start.

1. Create the Surveys space and choose who has access: they are the ones who will answer.
2. Click New survey, pick a template (NPS, satisfaction, event, course, eNPS or blank) and adjust the questions right on the screen.
3. Choose the Mode, the Response type (Optional survey, Required survey or Immediate response) and the Period, then click Open (or Schedule, with a future start).

Example. An event creates the Event survey space, private to ticket buyers, with an anonymous satisfaction survey marked as required and closing in seven days. On opening, each attendee gets the e-mail invitation, and whoever enters the app sees a notice asking for their answer. The speakers, who have no account, answer through the public link. The results show from 3 responses on, with the event's NPS. See Surveys.

#Recognition

What it is. A public wall of praise: a member recognizes 1 to 20 colleagues for what they did, with an optional community value, and whoever sees the space reacts and comments. It is a module of the Planning & HR tab, and a community can have several, one per team or area. See Recognition.

Why it matters. The thank-you that used to get lost in a private chat becomes visible to the team and reinforces the community values with real examples. Whoever is recognized gets an e-mail, and recognition can earn points in the ranking, with limits so nobody climbs by volume.

Where it is. Add Space, Planning & HR tab, Recognition module. The community values and the Dashboard are in Manage recognitions; the points, in Members › Gamification.

How to start.

1. Create the space and, if you want, set up the community values.
2. Share the space: anyone with access clicks Recognize, picks the colleagues and writes the message.
3. If you want points, give a value to Recognize a colleague and Be recognized in Members › Gamification.

Example. The support lead recognizes Ana and Bruno with the value Customer at the center: "They solved the integration problem on a Saturday, without anyone asking." The team reacts and comments, both get the e-mail, and the card also shows in the Feed, under the Recognitions filter.

#Feedback

What it is. The place for ongoing feedback between colleagues: give feedback, ask for someone's, answer, decline and say thanks, in the Received, Sent and Requests boxes. It is a module of the Planning & HR tab, and a community can have several, one per team or area. See Feedback.

Why it matters. Only the giver and the receiver read the text. Not the owner, not the admin, not Memberfy support. The team sees only the Numbers (how many feedbacks, requests and answers, and the participation), with no text, author or recipient. That makes it safe for candid conversations to happen outside review cycles.

Where it is. Add Space, Planning & HR tab, Feedback module. The numbers are in Manage feedback, for the owner and the admin.

How to start.

1. Create the space and choose who has access: they are the ones who can give and receive feedback.
2. Click Give feedback (or Ask for feedback), pick the person and write.
3. The recipient gets an e-mail, without the text, and reads it in the app.

Example. Ana asks Bruno for feedback "About yesterday's presentation". Bruno gets the e-mail, opens Requests › Asked of me and clicks Answer. Ana reads it in Received and clicks Say thanks. Nobody else sees what the two wrote.

#New content notices by e-mail

What it is. When the team publishes something new in a space (event, post, course, download, store product, call for papers opened or survey), whoever has access gets one e-mail with the title and a button to open it in the app. And each member chooses, by category, what they get from each community, in E-mails from this community. See New content notices by e-mail.

Why it matters. Before, telling the community about a new event meant building a campaign. Now the notice goes out on its own when you publish, and people who don't log in every day hear about it in time. On the other side, members turn off only what they don't want (the store, say) and keep getting the rest; in each notice's footer, one click turns off just that category.

Where it is. For the team, the Notify by e-mail · N people box, checked by default, when publishing. For the member, My Account, E-mails tab, E-mails from this community card.

How to start.

1. Publish as usual: the box comes checked and shows how many people will get it.
2. For a fix or a test, uncheck the box: nobody gets an e-mail for that post.
3. Tell members they pick their categories in My Account › E-mails.

Example. The coordinator opens the annual meeting's call for papers with Notify by e-mail · 1,240 people. Ten minutes later, the 1,240 get the e-mail with the title and the deadline. She fixes the title the next day and nobody gets it again. Each person gets at most 3 notices a day from one community, and the team sees only the number, never who turned off what.

#Development Plan

What it is. The individual development plan: each person builds theirs, with actions and due dates, and sends it to their direct leader, who approves it or returns it with a note. The person updates the progress and completes it at the end of the period. It's a module in the Planning & HR tab, and a community can have several Development Plan spaces. See Development Plan.

Why it matters. The plan no longer gets written after the review and forgotten: the leader follows the team in My team and To approve, and the management team sees on the Dashboard, leader by leader, how many have a plan and how many are behind (in the community's time zone).

How to start. Create the space in Add Space › Planning & HR › Development Plan, check in Members who reports to whom and ask each person to go to My plan › Create my plan.

#Feedback about another person

What it is. A leader asks colleagues for feedback about someone on their team, and a colleague tells the leader something about a person. The feedback has two parts: the Internal feedback, read only by the author, the requester and the direct leader, and the optional Message to the person, which they read with the writer's name. See Feedback › Feedback about another person.

Why it matters. The leader hears the team before talking to the person, without exposing what was said; the management team still sees only numbers.

#Time Tracking

What it is. The community's working-hours record, a module in the Planning & HR tab. Employees clock in and out in the app, with the server's time, and open the receipt right away; nothing that was punched can be edited or deleted. The direct leader decides adjustments (include a forgotten punch or disregard an undue one, always with a reason), and the management (owner, admin and finance) sets the rules, closes the month with the timesheet and generates the CSV, the AFD and the AEJ in the Portaria 671 layout. See Time Tracking.

Why it matters. A company that tracked hours in a spreadsheet or a separate system now has it inside the community: IP and location recorded with every punch (without ever refusing one), contractual schedule, tolerance, overtime paid or banked, night hours, national holidays preloaded and months closed in order, with each person's acknowledgement.

Where to find it. Add Space › Planning & HR › Time Tracking. In the space, the clock-in, timesheet, punches and Adjustments tabs; the management also has Team month, Rules and holidays, Employees and Establishment, AFD and AEJ.

How to start.

1. Create the space; the establishment step comes filled in with the company's CNPJ and legal name.
2. In Employees, register each person with CPF, hire date and job title.
3. Adjust the schedule in Rules and holidays and ask everyone to clock in.

#Improvements

• Tabs in Create Space. The dialog now has Events & Courses (Events, Courses, Certificates and Call for papers) and Sales (Store, Downloads and Classifieds); Community keeps Content, Ranking, Feed, Link, Gallery and Surveys, and Planning & HR brings Recognition and Feedback. See Modules.
• A one-item space is born with its item. In a space with a single call, course, survey or file, the Create Space dialog creates the space and the item together and ends open on it. Before, you created the space and then looked for where to create the item. Saving an empty space in one of these modes also goes straight to the item's form. See Create and organize spaces.
• Downloads with a single file gets the File step. You pick the file in the dialog itself, the Title comes with its name, and the item starts as a free draft, ready to review and publish. See Downloads.
• Several photos at once through the assistant. Ask "upload these photos to the Meetup 2026 gallery" and the assistant adds up to 20 images in one call, with a result for each; the ones that fail are sent again without repeating the others. See the recipe Upload a batch of photos to the gallery.
• Several Recognition and Feedback spaces per community. You can run a recognition wall or a feedback inbox per team or area, each with its own audience. Each recognition, feedback and request stays in the space where it was made, dashboards and numbers are per space, and the values still belong to the whole community and apply in all of them. See Recognition and Feedback.
• The invitation link opens the survey inside its space. Whoever answers lands on the form, with the community menu; the owner and the admin land on the editor or the results. In a Several surveys space, the browser address follows the open survey, so you can copy it, send it to someone on the team and reload without going back to the list. See Surveys.
• Themes and behaviors in Feedback. Whoever asks for feedback can say what they want to hear about, by picking themes and behaviors, and whoever gives or answers can write with a guide per theme (What did you observe, What was the impact, What do you suggest), checking first How the person will read it. Every community starts with 5 themes and 6 behaviors in each, which the owner and the admin adjust in Themes and behaviors, on the space's management bar. In the Numbers, the By theme block counts the themes without showing any text or person. Before, feedback was just a blank field. See Feedback › Themes and behaviors.
• Community values. In Recognition, "company values" are now called community values, which fits any kind of community, not just companies. See Recognition.
• Only the owner and admins set who reports to whom. Because the direct leader approves the development plan and reads feedback about the person, moderators and finance see the leader in the org chart and keep organizing groups. See Groups and org chart.
• Nobody sets their own leader. Not even the owner: an owner's or admin's leader is set by another owner or admin. See Groups and org chart.
• Website. The Memberfy website shows the Development Plan and Time Tracking as available in the Planning & HR extension and now covers themes and behaviors and feedback about another person in Feedback.
• New security controls.

#Fixes

• Event times follow the community's time zone. The event now stores the time zone of the community's country, and the page, list and cards show the time that was typed, wherever the reader is. Before, someone in another time zone saw the time converted to theirs. See Events.
• Deleting an event from its page works again. The Delete button failed; it now deletes and goes back to the list.
• Creating an event without picking a type works again. It used to fail; the event is now created with the Event type.
• The Events module description mentions tickets, which exist, instead of check-ins.
• The Leave Community warning says what really happens. It said all your data would be deleted; what goes are your certificates from that community, while your profile, posts and history stay with it. See Account and profile.
• Events require a start time. An event created without a start had no date; the start is now required through the API too, as it already was in the app and the assistant.

#For developers

#API

• Surveys: space module: "surveys" with moduleConfig.mode single or multi. The team uses /api/surveys (templates, create with spaceId, edit, audience preview, open, close, delete, filtered results, responses and CSV), with startsAt, closesAt and responseMode (optional, required, immediate); the status gains scheduled. Members have GET /api/surveys/pending and POST /api/surveys/{id}/notice/dismiss; the public link, /api/public/surveys/{publicToken}. See Surveys › In the API.
• Recognition: module: "recognition", routes under /api/recognitions (wall, reactions, comments, people, values and dashboard). In the Feed, the type recognition; in the ranking, the actions GIVE_RECOGNITION and RECEIVE_RECOGNITION. See Recognition › In the API.
• Feedback: module: "feedbacks", routes under /api/feedbacks (boxes, requests, thanks and numbers). A feedback or request that isn't yours returns 404, for the owner and the admin too. See Feedback › In the API.
• Feedback, themes and behaviors: the community catalog at /api/feedbacks/themes (read for whoever opens the space; write for the owner and the admin, with reorder and deactivate), themeIds/behaviorIds in POST /api/feedbacks/requests, sections[] in POST /api/feedbacks and in answer (the API assembles the text; POST /api/feedbacks/preview shows it without saving), themes in responses only for the two people, and byTheme in /dashboard (counts of 1 and 2 as null; null with groupId).
• New content notices: the publish routes accept notifyByEmail (default true) and answer with emailNotice (scheduled, recipientCount, reason); GET /api/content-notices/recipient-count counts who will get it. See New content notices › In the API.
• GET /api/spaces/modules lists surveys, recognition and feedbacks, with the categories community, learning, sales, people and coworking.
• Several Recognition and Feedback spaces: the /api/recognitions and /api/feedbacks routes that act in one space (lists, create, /people, /values, requests and /dashboard) accept spaceId. With a single space it is optional; with several, creating, requesting and searching people without it returns 422 (spaceRequired). A second space no longer returns 409. Recognitions, feedback and requests carry spaceId, and the dashboard without spaceId adds up all spaces.
• Surveys: GET /api/surveys/{id}/form carries spaceId, spaceSlug and sectionSlug (null when the survey has no space).
• Events: startTime is required in POST /api/events; without it, 400 with errors[].param = startTime.
• Development Plan: module: "developmentPlan", routes under /api/development-plans (lists with scope, /team, /dashboard, submit, approve, return with note, complete and the actions). See Development Plan › In the API.
• Feedback about another person: subjectId + giverIds[] in POST /api/feedbacks/requests, subjectId and messageToSubject in POST /api/feedbacks, and GET/PUT /api/feedbacks/settings (maxNominees). See Feedback › In the API.
• Hierarchy: reportsToId in PUT /api/hierarchy/members/{id} only by the owner and admins; other roles get 403.
• Time Tracking: module: "timeTracking", routes under /api/time-tracking (establishments, employees, punches and receipt, rules, holidays, adjustments, timesheet, months, CSV, AFD and AEJ with .sha256). No route changes or deletes a punch. See Time Tracking.
• Hierarchy: GET /api/hierarchy/me says whether the caller leads anyone (isLeader, directReports, hasIndirectReports; optional spaceId), and nobody sets their own reportsToId (403, owners included).

#MCP: technical details

• Surveys: 12 team tools (list_survey_templates, list_surveys, get_survey, create_survey, update_survey, preview_survey_audience, open_survey, close_survey, delete_survey, get_survey_results, list_survey_responses, export_survey_csv), with starts_at, closes_at and response_mode; open_survey with a future starts_at schedules. Opening, scheduling, closing and deleting ask for confirmation. Members have list_my_pending_surveys, and the survey recipe builds, opens and summarizes. Answering through the assistant does not exist, so as not to identify who answered. See Tools · Members › Surveys.
• Recognition: 13 tools, among them list_recognitions, create_recognition (with dry_run), react_to_recognition, create_recognition_comment and get_recognition_dashboard; deleting asks for confirmation. See Tools · Members › Recognition.
• Feedback: 13 tools, among them list_feedbacks, create_feedback (with dry_run), create_feedback_request, answer_feedback_request, decline_feedback_request, thank_feedback and get_feedback_dashboard. The assistant only reads the connected person's own feedback. See Tools · Members › Feedback.
• Feedback, themes and behaviors: list_feedback_themes (whoever opens the space) and, for the owner and the admin, create_feedback_theme, update_feedback_theme, reorder_feedback_themes, create_feedback_behavior, update_feedback_behavior and reorder_feedback_behaviors. create_feedback_request takes themes and behaviors; create_feedback and answer_feedback_request take sections, and dry_run returns the assembled text in body_preview. The sections never go into the assistant's log.
• Notices and preferences: the publish tools (create_event, create_post, create_poll, update_course, update_download_item, publish_product, update_call_status, open_survey) accept notify_by_email and return email_notice; get_email_notice_recipient_count gives the number beforehand. Each person reads and changes their own preference with get_my_email_preferences and update_my_email_preferences.
• create_space accepts the surveys, recognition and feedbacks modules.
• Gallery: add_gallery_images adds up to 20 images to a Gallery space, each by image_url (up to 50 MB) or image_base64 (all together within the call's 10 MB), with the same delivery as add_gallery_image; title and description apply to images without their own, tags to all of them, and each image comes back added or failed, with the reason. The minimum role is whoever can post in the space (its rule and approval apply); no confirmation, and no bulk delete. See add_gallery_images.
• Several spaces: the Recognition and Feedback tools accept space_id, required to create, request and search people when the community has more than one space. A member names people by name or id; when trying by e-mail, the assistant points to the name search (search_recognition_recipients, search_feedback_people) instead of a role error.
• Development Plan: 14 tools (list_development_plans, create_development_plan with dry_run, approve_development_plan, return_development_plan…) and the review_development_plans recipe. See Tools · Members › Development plans.
• Feedback about another person: create_feedback_about_request, about and message_to_person in create_feedback, get_feedback_settings and update_feedback_settings.
• set_manager is now owner and admin only.
• Time Tracking: 35 tools (records, rules, holidays, adjustments, timesheet, month close, CSV, AFD and AEJ), with confirmation to delete an employee or holiday, cancel an adjustment, close and reopen a month, and the recipes set_up_time_tracking and close_time_tracking_month. There is no tool to clock in: the punch is the person's own act, in the app.
• get_my_team says whether you lead anyone; set_manager explains that nobody sets their own leader.