Releases · Memberfy

2 novembre 2026

2026-11-02T23:59:59-03:00

Nouveautés

Memberfy en français. Le français devient la septième langue de Memberfy. Le site de Memberfy a désormais une version française, avec des pages pour la France, la Belgique, la Suisse et le Canada, et ce Centre d’aide s’ouvre en français à l’adresse docs.memberfy.net/fr-fr : la page d’accueil, les premiers pas, l’inscription, le compte et le profil, le Feed, le Contenu, les Événements, les Cours, l’offre et la commission de la plateforme et la vue d’ensemble du MCP sont déjà traduits. Les articles qui ne le sont pas encore s’affichent en anglais, avec un avis, en attendant leur traduction.
Thèmes de communauté. Dans Paramètres › Marque et apparence › Thème, tout le style de la communauté (mode, couleurs, police, coins, densité et état de départ du menu latéral) vit dans un thème, et activer un thème change tout d’un coup. La communauté garde jusqu’à 10 thèmes, avec Activer, Modifier, Dupliquer, Renommer, Restaurer et Supprimer, et choisit dans la galerie Thèmes prêts à l’emploi (Clair, Sombre, Sombre premium, Océan, Forêt et Éditorial) avec Utiliser ce thème ou Personnaliser. L’éditeur montre l’aperçu en clair et en sombre côte à côte, dans les onglets Couleurs, Police, Coins et densité et Navigation ; l’avertissement de contraste n’empêche pas d’enregistrer. Générer à partir d’une image propose un thème avec les couleurs d’une image ou du logo, avec un contraste garanti, en utilisant 1 utilisation d’IA de l’offre. Rien n’a changé dans votre communauté : elle a reçu le thème Actuel, actif, avec le style qu’elle avait déjà. Les anciennes Couleurs de la communauté sont devenues l’onglet Couleurs du thème, et le logo pour fonds sombres est passé dans Images. Voir Thème et couleurs.
Vitrine pour les Cours. Les espaces Cours ont un nouvel affichage Vitrine : une grille de couvertures verticales, comme un catalogue de films, avec la barre de progression sous la couverture et le badge Cours terminé sous le titre pour qui a fini. Choisissez-le dans Affichage à la création ou à la modification de l’espace. Voir Vitrine.
Format de couverture. Dans le formulaire du cours, la couverture peut être Bannière (3:1, le format habituel par défaut), Affiche (2:3, faite pour la Vitrine) ou Vidéo (16:9) ; l’envoi est recadré au format choisi. Les cours existants restent en Bannière. Voir Format de couverture.
« Reprendre là où vous vous êtes arrêté ». En haut de la liste des cours, qui a commencé un cours voit ceux qui sont en cours et revient directement à la leçon où il s’est arrêté et, dans une leçon vidéo, à ce moment de la vidéo. Voir « Reprendre là où vous vous êtes arrêté ».
« Mon contenu ». La liste des cours a une nouvelle vue Mon contenu, avec les cours auxquels la personne est inscrite et ceux que son plan ou un achat a déjà débloqués, même avant l’inscription. Voir Mon contenu.
Davantage de guides d’alternatives sur le site. La rubrique Alternatives du site de Memberfy a désormais des guides pour Skool, MemberKit, Hotmart Club, Mighty Networks, Discord, Nexudus et Qulture.Rocks, avec les prix publiés, les sources et la date de vérification.
Menu latéral compact. Sur ordinateur, le menu latéral peut être Compact : seulement les icônes des sections (ou les initiales, quand une section n’a pas d’icône), et un clic ouvre un menu flottant avec les espaces. Des pastilles montrent les nouveautés depuis votre dernière visite dans le Feed, le Contenu et les Événements, plus les mentions (en rouge) et les messages non lus dans Canal. Chaque personne change avec le bouton de l’en-tête ou dans Mon compte › Apparence › Menu latéral. Voir Menu latéral.
Barre du haut. Dans le thème, onglet Navigation, la communauté peut remplacer le menu latéral par la Barre du haut : sur ordinateur, chaque section devient un élément de l’en-tête qui ouvre ses espaces (ce qui ne tient pas va dans Plus, et Administration vient en dernier), avec les pastilles de nouveautés ; sur téléphone, une bande de sections sous l’en-tête ouvre les espaces dans un panneau qui monte. Pour réordonner, Administration › Modifier le menu ramène le menu latéral jusqu’à Terminer l’édition. Voir Thème et couleurs.
Masquer des éléments natifs. Dans le même onglet, Éléments natifs désactive pour tout le monde le Raccourci Personnes, le Classement général, Événements que j’organise, le Sélecteur de langue, le Signaler un problème de l’en-tête (qui passe dans le panneau de l’avatar) et Qui regarde la page. Les pages s’ouvrent toujours par leur adresse, et la cloche, la facturation, Mon compte, les Paramètres et l’Administration ne disparaissent jamais.
30 minutes de vidéo native offertes. Chaque communauté, Starter compris et y compris celles qui existaient déjà, a reçu 30 minutes de vidéo native, une seule fois, pour l’essayer. Elles sont utilisées avant le quota de l’offre.

Améliorations

Date de fin d’adhésion aussi sur l’écran du groupe. Quand vous ouvrez un groupe, Valable jusqu’au se trouve sous la recherche de personnes et s’applique à qui vous ajoutez ; chaque personne affiche la date à laquelle elle sort, et le propriétaire et l’administrateur la changent ou la retirent sur place. Voir Groupes et organigramme.
Des conditions d’utilisation plus claires. Les Conditions d’utilisation disent maintenant ce qui arrive au compte de quelqu’un qui n’a pas l’âge minimum, et que les notes internes de l’équipe ne sont pas incluses dans votre fichier de données ; leur accès se demande à la communauté. Voir Télécharger vos données.
La confirmation d’âge est désormais obligatoire. Confirmer son âge est maintenant obligatoire à l’inscription, dans la demande d’entrée, au premier mot de passe depuis une invitation ou un import et lors des achats payants, par l’API aussi (sans le champ, la réponse est 400). Les membres existants ne confirment pas à nouveau. Voir Âge minimum.
Registre d’accès. Comme l’exige le Marco Civil da Internet brésilien, Memberfy conserve désormais, pendant 6 mois, l’IP, le jour et la première et la dernière heure d’accès de chaque personne, par l’application et par l’assistant IA. Personne dans la communauté ne voit ces données. Voir How long data is kept, qui liste aussi les durées légales pour les paiements, le pointage et la vérification des bénéficiaires.
Votre historique d’accès dans votre fichier de données. Le fichier de Télécharger vos données inclut désormais acessos.csv, avec vos accès des 6 derniers mois : jour, IP et première et dernière heure.
Une zone de publication plus épurée. Désactiver les commentaires se trouve maintenant dans Plus d’options, replié, quand vous publiez dans le Feed et quand vous créez ou modifiez une publication ; Programmer la publication reste visible. Quand une publication a déjà les commentaires désactivés, Plus d’options s’ouvre tout seul. Voir Désactiver les commentaires.
Guide des intégrations vidéo. Le nouvel article Intégrations vidéo donne le pas à pas pour Bunny Stream, Cloudflare Stream, Panda Video et HLS, dans les leçons et les publications, et la clé de signature. Les articles Feed et Contenu listent désormais ces fournisseurs.
Un pied de page du site plus court. Le pied de page du site de Memberfy est beaucoup plus court, et sur téléphone chaque groupe de liens s’ouvre et se ferme. Chaque groupe mène à une page qui réunit tout ce qui relève de sa catégorie, comme la nouvelle page Solutions, avec les types d’organisation que Memberfy accompagne.
Des panneaux plus accessibles sur téléphone. Les panneaux qui montent sur téléphone gardent maintenant le focus du clavier à l’intérieur et le rendent là où vous étiez quand ils se ferment.
Le site s’ouvre dans la langue du visiteur. À la première visite, le site de Memberfy s’ouvre dans la version de la langue du navigateur (ou, quand cela ne suffit pas, du pays du visiteur). Qui choisit un autre pays dans le sélecteur en haut y reste lors des visites suivantes.
Type de communauté dans le formulaire d’inscription. Le formulaire d’inscription du site demande le type de communauté : Communauté, Entreprise et RH ou Coworking. Qui arrive depuis la page de l’une de ces solutions trouve ce type déjà sélectionné et peut le changer.
Nouveaux contrôles de confidentialité et de sécurité.
Plus de minutes de vidéo native, et des liens sans limite. Le quota de vidéo envoyée à Memberfy devient Vidéo native (minutes par mois) : 60 sur Growth, 180 sur Business et 300 sur Scale (le Starter utilise les minutes offertes). Les liens YouTube, Vimeo et d’autres plateformes ne comptent jamais et sont illimités dans toutes les offres.

Corrections

Vérification de votre propre compte Resend. La vérification de votre propre compte Resend (Business et au-dessus) fonctionne à nouveau : l’e-mail de test arrive à qui a cliqué sur Vérifier, et le compte devient actif quand Resend confirme la livraison. Voir Envoi par votre compte Resend.
Parcours de l’appel à propositions. Enregistrer un Appel à propositions avec un parcours qui porte le même nom qu’un autre, même un parcours déjà retiré, n’échoue plus : le nouveau parcours est enregistré avec sa propre adresse.
Menu latéral sur téléphone. Le menu latéral sur téléphone montre tout sans avoir à masquer la barre d’adresse du navigateur : la rubrique Administration en bas du menu apparaît dès l’ouverture.
Communautés fermées. Les abonnements d’une communauté fermée ne sont plus facturés et n’envoient plus d’avis de facturation. Les avis « Votre accès se termine » ne partent plus non plus d’une communauté fermée.
Ajustements de points dans les Journaux. Dans les Journaux, les ajustements de points et les autres actions de gamification affichent maintenant un nom lisible.
Dates avec une majuscule seulement à la première lettre. Dans les calendriers et les en-têtes, les dates ne mettent plus de majuscule qu’à la première lettre au lieu de chaque mot (dans les langues qui écrivent les dates en minuscules).

Pour les développeurs

API

Clés d’API : elles atteignent désormais les publications programmées (content), le parrainage de membres (members), les points (gamification) et le résumé public de la communauté (community) ; les intégrations vidéo, l’envoi par le compte Resend, les demandes de confidentialité, le menu latéral et les écrans de bienvenue n’acceptent pas de clés. Voir Authentification › API key.
GET /api/courses/continue : les cours en cours de la personne, avec la leçon à ouvrir maintenant et le moment de la vidéo (resumeAt) ; seulement les cours qu’elle peut encore ouvrir. Voir Cours.
GET /api/menu/counters : ce qui est nouveau depuis la dernière visite dans chaque espace Feed, Contenu et Événements, avec la somme par section ; un espace que la personne ne peut pas ouvrir ne compte pas. Voir Menu latéral.
coverFormat (BANNER, POSTER, VIDEO) dans POST et PUT /api/courses ; layout: "showcase" (Vitrine) sur les espaces Cours ; l’état de départ du menu latéral (full ou rail) dans le thème (values.navigation.sidebarDefault). Les écrans des Cours et du menu latéral compact sont en ligne dans l’application.
Thème : values.navigation.layout (sidebar ou top) et values.navigation.hiddenNative (une liste de people, leaderboard, organizedEvents, languageSelector, reportProblem, presence) dans /api/community-themes ; hors de la liste, 422 sur le champ. À l’activation, ils vont dans navigation.layout et navigation.hiddenNative de la lecture de la communauté. Voir Thème et couleurs.
Thèmes : GET /api/appearance/themes (prêts à l’emploi), /api/community-themes (lister, créer, lire, modifier, supprimer ; active à la place de l’id désigne le thème actif), /activate et /restore, et POST /api/communities/appearance/theme-from-image (proposition sans enregistrer, 1 utilisation d’IA). Le GET de la communauté apporte activeThemeId, et appearance et themePalette sont désormais lus depuis le thème actif.
Changement de contrat : mode et navigation dans PATCH /api/communities/appearance (qui garde darkLogoUrl), et themePalette et themeColor dans PUT /api/communities/{id}, répondent 400 sur le champ : le style s’enregistre par le thème. À la création de la communauté, la palette envoyée devient les couleurs du thème initial Clair. Voir Réponses et erreurs.
Changement de contrat : communityType (COMMUNITY, COMPANY_HR ou COWORKING) est désormais obligatoire dans POST /api/community-requests, la demande d’accès du formulaire d’inscription. Sans lui, la réponse est 400 avec param = communityType.
Utilisation de l’offre : video.trialMinutes (les 30 minutes offertes) et, dans l’utilisation vidéo, trialMinutes et trialMinutesLeft, utilisés avant video.transcodeMinutesPerMonth.

MCP : détails techniques

list_my_courses_in_progress : « Où est-ce que je me suis arrêté ? » ({"limit":1}), suivi de get_course pour ouvrir la leçon. Voir Outils · Cours.
list_space_updates : ce qui est nouveau dans vos espaces (include_zero: true liste aussi ceux qui sont à jour) ; la lecture par l’assistant ne remet pas le compteur à zéro. Voir Outils · Communauté.
create_course et update_course reçoivent cover_format ; create_space et update_space reçoivent layout: "showcase", Cours seulement ; l’état de départ du menu latéral se change dans le thème, avec update_community_theme.
Les outils de thème acceptent navigation.layout et navigation.hidden_native (la liste complète ; [] montre tout) ; la confirmation de activate_community_theme montre la navigation avant → après, et get_community_settings renvoie appearance.navigation_layout et appearance.hidden_native.
Thèmes : list_theme_presets, list_community_themes, get_community_theme, create_community_theme (origin: "image" garde la proposition du logo), update_community_theme (sans theme_id, le thème actif), activate_community_theme, restore_community_theme et delete_community_theme (les trois demandent confirmation) et suggest_community_theme_from_logo (1 utilisation d’IA, n’enregistre pas). primary_color, secondary_color, reset_colors et mobile_bar_color ont quitté update_community_settings, et mode et sidebar_default ont quitté update_community_appearance, qui garde le logo pour fonds sombres. Voir Outils · Communauté.

1 novembre 2026

2026-11-01T23:59:59-03:00

What's new

Configurable levels with weekly activity requirements

What it is. The community builds its own level ladder: 2 to 20 levels, each with a name, minimum points, an optional image and, if you want, weekly activity, such as "at least 3 posts a week" or "2 comments in the Introduce yourself space". The level shows who is taking part now, not just who piled up points once.

How it works. To move up, a person needs the points and the level's requirements met this week, and the move is immediate. To stay, the full previous week counts: whoever did not meet them moves down on Monday at 00:00, in the community's time zone. When you save, the preview shows how many people move up and how many move down.

Where it is. In Members › Gamification, Levels tab, for the owner and the admin. The level's name and image show on the ranking, the podium, My engagement, the profile and the member page.

If you change nothing. The community keeps the usual 9 levels, from Newcomer to Legend, with no requirements: nobody's level changes. See Gamification › Levels.

What is left this week, on the profile

When the level has requirements, the profile shows the week's progress: each requirement with how much is done (2 of 3) and, below, what is left to move up to the next level. The person and the team (owner, admin, moderator and finance) see this block. See Gamification › What is left this week.

Level and points triggers in workflows

The Levels and points block brings the Moved up a level, Moved down a level (with the Reason) and Reached N points triggers, and the Condition gets level and points rules. Example: "Moved down from Kernel → remove from the Kernel group". See Workflows › Levels and points.

In e-mail campaigns, {{level}} is now the name the community gave the level, and {{level_number}} brings its number.

Revenue in Monetization

What it is. A Revenue card in Monetization's Dashboard section, with the period's sales by payment date: Gross (with the number of sales), Refunds and Chargebacks (amount and count) and Net of refunds, the gross minus refunds and chargebacks. Amounts are before the platform fee.

Why it matters. Until now, a refund didn't show up next to the sales it undid. Now you see, in one place, what came in, what went back and what's left.

Where it lives. In Administration › Monetization › Dashboard, between the balance and the latest transactions, for the owner, admin and finance. The period goes from Last 7 days to Last 12 months (30 days by default); when the community sells in more than one currency, a picker chooses the currency.

Example. Over 30 days: Gross US$ 1,299.40 (9 sales), Refunds US$ 99.90 (1 refund), Chargebacks US$ 0.00, Net of refunds US$ 1,199.50. On the Dashboard, the indicator is now called Gross revenue, with the same source. See Revenue for the period.

Cookie notice in communities with Google Analytics: measurement only starts after the person accepts. Whoever comes in for the first time sees Cookies in this community, with Reject, Accept and Customize; the choice lasts 12 months, and Cookies, at the foot of the side menu and in the avatar panel, opens the notice again. A community without Google Analytics shows no notice. See The cookie notice.

Spaces and sections can open for whoever holds a badge

Spaces and sections can open for whoever holds a badge. In Who gets in, the badge sits next to groups, products and plans: whoever earns it gets in at once, with a bell notice, and whoever loses it is out on the next visit. On screen, + Badges in Who gets in; whoever does not have it yet sees the padlock with "Earn the Mentor badge" (a private badge shows only as "A special badge"), and removing a badge warns how many spaces and sections it opens. Also through the API and the assistant. See Visibility and access and What a badge unlocks.

Spaces and sections that open by level

In Who gets in, a minimum engagement level: whoever is at it or above gets in, whoever drops is out on the next visit. Whoever has not reached it sees the level and what is left, with the points and the week's activity. In Who gets in, the + Level button; the padlock shows "Available from level 9 · Legend" and, for members, the level's activity this week and See my progress. Also through the API and the assistant. See Visibility and access.

Badges awarded automatically

A badge can award itself by a rule: an action or a moment (course completed, check-in, quiz, form…), how many times, in which space and in which period, with no workflow. Counting starts when the rule is created. In the badge window, under Award automatically; also through the API and the assistant. See Award automatically.

Daily points cap per action

Each action can have a most-times-a-day that gives points; over it, the action happens with no points and does not count for badges. See Daily cap per action. On screen, it is the Max per day column in Points per action.

Signed calls in Call webhook

With the signing secret generated, every Call webhook call carries X-Memberfy-Signature, so the destination can prove it came from Memberfy. See Signed calls. The secret is generated in Variables and keys, in the Signing secret block.

Campaign audience by custom field

An e-mail campaign's audience can include or exclude people by a choice custom field, in the Fields section of Choose the audience and of Exclude: "City is one of São Paulo, Campinas", "Interests contains any of Data, AI", "Accepts sales contact: Yes". Up to 10 conditions per campaign; a closed or sensitive field cannot be used. If the field is deleted, closed, changes type or loses an option, the condition warns. See The audience.

Display per space, with an Events calendar

In six modules (Content, Events, Courses, Downloads, Classifieds and Gallery), the owner and the admin choose how items show for everyone: Feed, Cards, List, Compact, Grid or Calendar. In an Events space, the Calendar shows the month or the week, with undated events set apart. Without a choice, nothing changes. It is the Display field, when editing the space and in Create Space; also through the API and the assistant. See Display.

Turn off comments per post

The author, the owner, the admin and the moderator can turn off a post's comments, in the post's … menu (Turn off comments / Turn on comments) or with the Turn off comments box when creating and editing: nobody comments, the team included, and existing ones stay. "Comments are turned off" shows in place of the comment box. See Turn off comments.

Feed by activity

At the top of the feed, Sort chooses between Recent and Active: pinned posts first, then whatever had the latest comment or reply, so an old post with a new conversation comes back up. See Recent or Active.

Welcome and First steps

What it is. Screens a new person sees on their first visit, before the community: 1 to 5, with text, video (uploaded, which can require watching to the end, or a YouTube or Vimeo link), the rules to accept with I have read and accept the rules (the acceptance is recorded with the date and the text) and the profile fields the community wants to know. After them, the First steps card, with up to 6 missions that complete themselves through use (completing the profile, posting in a space, answering a form, registering for an event, completing a course), each with points and a badge, and a final badge.

Why it matters. The new person arrives knowing the rules, with the profile filled in and a clear path to start taking part.

Where it is. In Settings › Welcome, for the owner and the admin. The mode is Required or Can skip, and View as member shows the screens as a new member sees them. The team never goes through the welcome.

How to start. 1) Build Screen 1 and, if you want, more screens. 2) Turn on Welcome on and decide whether it also applies to existing members. 3) Turn on First steps and add the missions.

Example. Maria joins, watches the video, accepts the rules and fills in Job title. In the Feed, the card First steps · 0 of 3; she posts her introduction, and within about a minute the card shows 1 of 3. In the Members list, the Welcome filter shows who is pending, and workflows get Completed the welcome and Completed the first steps. See Community welcome.

Scheduled posts

What it is. When creating a post or a status, Schedule post picks the date and time it goes out, up to 1 year ahead. Until then, it only shows in the Scheduled list, for the author and the team; at that time, it goes out once, with the e-mail notice, the points and the new-post workflows.

Where it is. In the posting box and in the create-post window. The Scheduled list is in the arrow menu next to New Status, in the Feed, and in the confirmation's See scheduled link, with Edit, Reschedule, Publish now and Cancel. The owner, the admin, the moderator and finance manage everyone's scheduled posts; each person, their own. If the author loses access to the space by then, the post does not go out, and they and whoever scheduled it are notified. See Scheduling a post.

Groups with an end date

Each of a person's groups can have a Valid until: at the end of that day, in the community's time zone, they leave the group by themselves (within 10 minutes) and lose the access the group gave, without being told; the exit goes to the Logs. It is in the person's Place in the organization, shows in the Members list (until 12/31/2026), in the import (the Groups: valid until column) and in the workflows' Add to a group step (No end date, For N days or Until a date). Changing someone's groups now belongs only to the owner and the admin, because a group can open spaces. See Valid until.

Reason when removing a member

When removing someone, the team can write the Reason (only the team sees it). It stays only in the Logs, which only the owner and the admin read; the person never gets the reason. See Remove from the community.

Member referrals

Each member gets a referral link; whoever joins through it counts as referred, once, with points for the Refer a member action and the Referred someone trigger in workflows. The owner and the admin turn it on in Settings › Access and sign-up, Referrals card; the member gets the link in My Account › Refer (Refer the community, with Copy); the team sees who brought whom in Members › Referrals, with Download CSV, and the Referred by card on the member's page. See Member referrals.

Videos from Bunny Stream, Cloudflare Stream, Panda Video and HLS

Video lessons and posts take these providers' links, with their player. If the Bunny library or the Cloudflare account requires a token, the owner and the admin add the signing key in Settings › Video integrations (Save key, Verify), and the video goes out signed, valid for 6 hours. If the provider refuses the key, viewers see "Video unavailable", and the team gets a bell notice. See Video integrations.

Points in the Store

Points become a currency: a product can have a points price, and the person redeems it with their balance, without going through payment. Spending never lowers points or level, only the balance. The owner and the admin turn it on in Members › Gamification, Points balance card (The currency name, How the balance starts); each product picks How it is paid (Money, Points or Points or money) and the Points price. The Store shows "or N points", Redeem with points and "N points missing", and each person sees their balance and statement in My Account › My points. See Points in the Store.

Sending through your Resend account

On the Business plan or above, the community's e-mails can go out through its own Resend account, with its domain and without the plan's recipient quotas. It is in Settings › Sending through your Resend account: Connect the Resend account, with the key, the webhook secret, the sender and the Data notice; the Webhook address with Copy; the status (Pending, Active, Error or Paused by the plan) and the Verify, Change and Disconnect buttons. See Sending through your Resend account.

Badges and points in the member import

To bring the history of people coming from another platform: the import gets the Badges and Initial points destinations. In the summary, each badge not in the catalog has Create badge and Ignore, and The level people will land on shows up. See Migrating from another platform.

Dark mode

What it is. The community can show a Light background (the default), Dark, or Automatic, which follows each person's device theme. It applies to the whole app, Administration included. E-mails, certificates and the recognition art stay light.

Where it is. In Settings › Brand and appearance, Theme card, for the owner and the admin. Memberfy enables the dark theme community by community: without it, only Light shows. Once it is enabled, also upload the Logo for dark backgrounds (ideally a PNG with a transparent background); without it, the logo sits on a light plate. Each person can pick their own theme in My Account › Appearance: Follow the community, Light, Dark or Device, a choice that applies only to that browser and that community. See Dark mode.

Deleting your own account

What it is. A member requests the deletion of their account in a community, with their password. The deletion happens on the effective date: whichever comes last between 30 days and the end of the period already paid. Anyone with paid access keeps it until then; without paid access, the account is deactivated at once. After the effective date, the person's posts and comments show as Removed member; the subscription runs to the end of the period, with no refund.

Where it is. In My Account › Privacy, the Delete my account card. With the deletion scheduled, a banner at the top of the app shows the date, with Cancel deletion and Details; someone without paid access who tries to sign in sees Account deletion scheduled, with Cancel deletion and sign in. The e-mail's Cancel the deletion button cancels at once.

For the team. The owner and the admin handle the request of someone with a role below their own, including someone without a password: in the member's edit window, Delete this person's data, with the reason and the word DELETE. This deletion cannot be withdrawn. See Delete your account and Handle an erasure request.

Download your data

What it is. A ZIP file with what the community keeps about the person: profile, purchases, subscriptions, registrations, posts, messages, answers and the files they uploaded, with a README in their language.

How it works. In My Account › Privacy, Download my data, with the password. When the file is ready, an e-mail arrives; to download, the person signs in with their own account, and each download creates a link valid for 5 minutes. The file exists for 72 hours, and attachments too large for the ZIP come as 72-hour links. One request at a time, and a new one only 24 hours later.

For the team. The owner and the admin request it on the person's behalf, with a reason, in Export this person's data, in the member's edit window. The file goes only to their e-mail: the team cannot download it. See Download your data.

Data retention period

The data of guests and of parcels already closed, in Attendance and Parcels spaces, now has a retention period per space, from 6 to 60 months (12 by default), after which it is anonymized; a parcel waiting for pickup never is. The team's activity log loses the before-and-after detail of changes after 2 years. Automatic anonymization arrives in communities in the next few days. See How long data is kept.

The period changes in Configure space, in the Retention period (months) field, by the owner and the admin only: before saving, the Change the retention period? window shows how many records would be anonymized, and a reduction only applies 7 days later.

Minimum age

In Settings › Access and sign-up, the owner sets the Minimum age to have an account (16 to 99) and whether This community serves minors. Sign-up, the request to join and setting the password from an invitation ask for I confirm I am 16 or older (or the community's age), and a paid checkout asks for the declaration of being 18 or older, or authorized by a legal guardian. See Minimum age.

Circle alternatives guide on the website

On the Memberfy website, the Circle alternatives guide compares eight platforms side by side (published price, fee per sale, app, API and AI), with sources and the date they were checked, and opens the new Alternatives section.

Improvements

New security controls.
Terms of use updated on November 1. They now cover the minimum age to have an account, exporting and deleting data by the person themselves, and retention periods. See Terms of use.
Privacy policy updated with minimum age, downloading your data, account deletion and retention periods. See Privacy policy.
Dates in the community's time zone. E-mail deadlines and dates (payment, cancellation, plan change, sign-in and password notices, events) and the sale timeline are shown in the community's time zone, with the time zone abbreviation ("22:00 - 23:30 BRT"); before, some came out in the server's time. A community without business information uses the time zone of its language's region. See The community's time zone.
The space-unlocked notice arrives by push, in the achievements category, as well as in the bell.
More precise searches. A % or _ typed in a search is now matched as text: before, % listed everything and _ matched any character.
Liking from the feed earns points, like liking on the post itself: before, a like given in the feed earned nothing.
Undoing an action takes its points back. Unliking, deleting a post or a comment and dropping out of an event remove the points the action gave, and it no longer counts for badge rules and level requirements.
The assistant takes the Google and Bing verification. Ask it to add the Google Search Console or Bing Webmaster Tools code to the community. See Verify the community on Google and Bing.
The assistant's log without personal data in plain view. The record of what the assistant did in the community keeps e-mails, phones, CPF numbers and names masked (m***@memberfy.net), keeping who did what and when.
Links to the website and to the community at the top of the Help Center.
Engagement on the website. The Engagement page on the Memberfy website now covers badges (by hand, by workflow and automatic from a course, a check-in and Networking) and levels with weekly activity, with the level and point triggers.
Website: the “Request access” button is now “Create account”.
Your community now shows up better in search engines and AI: automatic robots.txt, sitemap and llms.txt in every community. See Your community in search engines and AI.
Save X%, one rule. The savings tag compares each option's price per month with the monthly option without a contract, at the price the buyer pays (with the platform fee when the buyer pays it), rounded to a whole number. The monthly option has no tag, and the tag does not show when there is no saving or no monthly option to compare with. See The savings tag.
Requirement in a space you cannot access. On the profile, a level requirement tied to a space the person does not open shows "in a space you cannot access" in place of the name. See What is left this week.
Drafts and posts awaiting moderation are visible only to whoever wrote them and to the team, in the feed counts too. See Content › The list and the page.
The fixed-IP call quota now renews at midnight in the community's time zone. See Fixed IPs.
The finance role can now view the community's pricing plans. See Roles and permissions.
Whoever replied STOP by SMS or WhatsApp sees on screen that it stopped and can turn it back on there. See Stopped by a STOP reply.
For the team: Google Analytics measures less. With the cookie notice, GA4 counts visits only for those who accept, so the numbers are lower than before. See Google Analytics.
Search engine verification. Under Settings › Search and discovery, paste the Google Search Console or Bing Webmaster Tools code to prove the community is yours, also on the .memberfy.net address. The sitemap and llms.txt now list the open courses, the calls with submissions open and the certificates their holders let be indexed (with Guest Access off, only the home page). See Your community in search engines and AI.

Fixes

Leaderboard without people who left. The leaderboard position no longer counts people who left the community, and it's now the same on the profile and in the reports. See Ranking.
Unnamed member. People with no name on file show as "Unnamed member" on the leaderboard, in the gallery, in comments and in chat.
Repeated currency filter. Asking Monetization for the same currency twice returns a validation error instead of an internal error.
Deleted purchases out of revenue. A deleted purchase no longer counts in the revenue numbers of Monetization, the Dashboard and the reports.
Amounts in workflows. The amount condition in workflows writes money in the community's currency and format, not always in reais. See The "Variable" condition.
Free trial without a sale notice. The community no longer gets the new sale notice when someone starts a free trial with no charge; the subscriber still gets the confirmation.
Sales and subscription reports round the half cent the same way as the statement.
Search finds public spaces inside members-only sections, for people who already have access to them.
Confirming attendance at an event answers in the language of whoever uses it.
Plan change by boleto that did not clear. If the plan change boleto does not clear by the business day after it is due, the change is given up: the boleto is canceled, the person gets the payment-not-completed notice, and the renewal goes ahead on the current plan. After that, another change can be requested.
Points price on edit. Editing a points product shows the points price, and so does the product list. See Points in the Store.
Creating a product with the name of a deleted one no longer fails.
Space-unlocked notice. The notice says whether a level or a badge opened the space or section: "Your level opened the … space" or "Your badge opened the … space".

For developers

API

GET and PUT /api/gamification/levels (owner and admin): the level ladder with its requirements; dryRun returns how many move up and down without saving.
GET /api/gamification/levels/progress: the week's progress for the current and the next level, for the person and the team; on the profile, in engagement.levelProgress.
New optional fields: levelId, levelName and levelImageUrl on the ranking and the profile. See Gamification › In the API.
Webhooks: the member.level_changed and member.points_changed events, 97 in total. See Webhooks.
GET /api/dashboard/monetization comes from the statement and carries refunds, chargebacks and net in metrics.totalRevenue, plus currency and currencies; the currency parameter picks the currency, and repeating it returns 400. See the reference.
GET /api/vault: outbound.month is now the month in the community's time zone, and the new optional field outbound.resetsAt says when the fixed-IP count restarts.
GET /api/communities/plans and GET /api/communities/plans/{id} accept the finance role; creating, editing and removing stay with the owner and admin.
GET /api/members/me/notice-preferences: the new optional globalOptOut field, in channels.sms and channels.whatsapp, shows the stop by a STOP reply; the PUT with enabled: true turns it back on in every community. See In the API.
access.badgeIds on POST/PUT of spaces and sections (absent keeps the badges; [] removes them). The 403 of an area closed by a badge carries reason: "badge", the earnBadge action, badges (public ones only) and hasHiddenBadge. space.access_granted gains source: "badge", and GET /api/badges brings unlocks. See Visibility and access › In the API.
PUT /api/communities/{id} accepts googleSiteVerification and bingSiteVerification, and GET /api/public/community-summary lists, without a session, the open courses, the calls with submissions open and the certificates their holders let be indexed (empty with Guest Access off). See In the API.
access.minLevelId/access.minLevel on spaces and sections; the 403 with reason: "level", earnPoints and progress; 409 gamification.levels.inUse with the spaces and sections; space.access_granted with source: "level". rule on POST/PATCH /api/badges, dailyCaps on PUT /api/gamification/config and GET/POST/DELETE /api/vault/signing-secret.
Campaigns: fields (oneOf, containsAny, containsAll, isTrue, isFalse; up to 10 conditions), audienceWarnings, fieldWarnings. See E-mail campaigns › In the API.
Spaces: layout (POST/PUT /api/spaces and when reading), layouts per module in GET /api/spaces/modules; GET /api/events with from/to, undated, truncated, undatedCount. See Display.
Welcome: GET/PUT /api/welcome/settings (screens, mode, First steps with missions), GET /api/welcome, POST /api/welcome/progress and /skip, GET /api/welcome/missions and POST .../dismiss and .../celebrated; welcomePending in GET /auth/me, welcome=pending|completed|skipped in GET /api/members. See Welcome › In the API.
Scheduled posts: publishAt in POST /api/content and /api/status (and in PUT, to reschedule), schedule in the response, GET /api/scheduled-posts and POST /api/scheduled-posts/{type}/{id}/publish; finance manages scheduled posts like the rest of the team. See Content › In the API.
Members: reason in DELETE /api/members/{id} (Logs only); groupExpirations in PUT /api/hierarchy/members/{id} and groups[].expiresAt; changing someone's groups now belongs only to the owner and the admin; the groupsExpireAt target in the import; expiresInDays/expiresAt in the addToGroup step. Import: the badges and points targets. See Groups and org chart › In the API.
Referrals: /api/referrals/settings, /me and /report; referralCode and referralSeenAt at sign-up; referredBy in GET /api/members/{id}. See Member referrals.
Points in the Store: /api/points/settings, /me and /members/{memberId}; pricingMode and pointsPrice on the product; POST /api/storefront/products/{productId}/redeem. See Points in the Store.
Sending through the Resend account: GET/PUT/DELETE /api/email-provider and POST /api/email-provider/verify. See Sending through your Resend account.
Video: the video lesson accepts Bunny Stream, Cloudflare Stream, Panda Video and HLS, with videoEmbed in GET /api/courses/{identifier}; signing keys in /api/video-integrations. See Courses › With the API.
Time zone: timezone on sales and refunds, atText on each timeline event; an event's timezone must be a valid IANA time zone (otherwise 400). See Sales.
Webhooks: the member.welcome_completed, member.onboarding_completed and member.referred events, 100 in total; member.group_left with reason: "expired"; purchase.completed with pointsPaid and purchase.refunded with paymentMethod: "POINTS" and pointsReturned, only on points purchases. See Webhooks.
Posts: commentsDisabled (POST/PUT /api/content, /api/status; commenting on a post with comments off: 403 comments_closed); sort=recent|activity (GET /api/feed), with lastActivityAt on every item. See Feed › In the API.
Dark mode: appearance (mode, effectiveMode, darkLogoUrl, darkModeAllowed) in the community reads, PATCH /api/communities/appearance and the logo upload with variant=dark, which does not replace the regular logo. See Dark mode.
Account deletion: GET/POST/DELETE /api/privacy/erasure, POST /api/privacy/erasure/cancel (the e-mail link, or e-mail and password) and POST /api/privacy/members/{memberId}/erasure (owner and admin, with a reason); with a scheduled deletion and no paid access, the login answers 403 with code: ERASURE_SCHEDULED. See Delete your account.
Data export: GET/POST /api/privacy/exports, GET /api/privacy/exports/{exportId}/download (5-minute signed link, the person only) and POST /api/privacy/members/{memberId}/exports (owner and admin, with a reason); 409 with one being built, 429 before the 24 hours. See Download your data.
Retention period: moduleConfig.attendance.retentionMonths and moduleConfig.parcels.retentionMonths on spaces; anonymized visits, guests and parcels carry anonymized: true. See How long data is kept.
Minimum age: minimumAge and servesMinors in the community settings (owner only), ageConfirmed on sign-up and ageDeclaration at checkout. See Sign-up and access › Minimum age.

MCP: technical details

Privacy through the assistant: export_my_data, get_my_data_export and export_member_data (the export arrives by e-mail only: the assistant does not hand over the file or the link); delete_my_account, get_my_account_deletion, cancel_my_account_deletion and erase_member_data (requesting the deletion disconnects the assistant); minimum_age and serves_minors in get_community_settings and update_community_settings (owner only); retention_months in create_space and update_space, with the count of what would be anonymized in the confirmation. Every action that deletes or exports asks for confirmation. See Download your data and Delete your account.
update_group_members now requires the admin role: only the owner and the admin change someone's groups.
20 new tools, 951 in total: welcome (get_welcome_settings, update_welcome_settings), referrals (get_my_referral, get_referral_report, get_referral_settings, update_referral_settings), points in the Store (get_member_points, get_points_settings, update_points_settings, redeem_product_with_points), scheduled posts (list_scheduled_posts, publish_scheduled_post), sending through the Resend account (get_email_provider, update_email_provider, verify_email_provider, disconnect_email_provider; the key never goes through the assistant) and video signing keys (list_video_keys, update_video_key, verify_video_key, delete_video_key).
Dark mode through the assistant: update_community_appearance (owner and admin, with confirmation) changes the theme and the logo for dark backgrounds, and get_community_settings shows appearance. With it, there are 952 tools.
Also changed: publish_at in create_post, create_short_post and update_post; reason in remove_member; expires_at in update_group_members; welcome and referredBy in list_members and get_member; badges and points in the member import; pricing_mode and points_price on products; refunding a points purchase; Bunny Stream, Cloudflare Stream, Panda Video and HLS in lessons; and sale dates in the community's time zone.
New tools: get_ranking_levels, update_ranking_levels (asks for confirmation, with the preview of who moves up and down) and get_level_progress. 927 tools in total. See Tools · Content.
Workflows through the assistant accept the member.level_changed and member.points_changed triggers and the levelAtLeast and pointsAtLeast rules.
The assistant now answers Monetization in any currency the community sells in, with gross, refunds, chargebacks and net shown separately.
get_sales_summary takes currency (one currency) and returns refunds, chargebacks, net and currencies. See Tools · Finance.
get_my_notice_preferences shows the stop by a STOP reply (global_opt_out), and update_my_notice_preferences turns the channel back on, with a confirmation saying it applies to every community.
update_space_access and update_section take badge_ids; each list sent replaces only its own. New get_space_access tool (team), and delete_badge warns what stops opening. See get_space_access.
min_level on update_space_access and update_section; rule on create_badge and update_badge; daily_caps on update_ranking_rules; new tools get_signing_secret, create_signing_secret and delete_signing_secret; the Welcome journey with badges recipe.
create_campaign, update_campaign, preview_campaign_audience accept fields in the audience and the exclusion (one_of, contains_any, contains_all, is_true, is_false); warnings come back in field_warnings.
create_space, update_space accept layout; list_space_modules returns layouts; list_events accepts from/to and undated, with truncated and undated_count.
create_post, create_short_post and update_post take comments_disabled; commenting on a closed post returns comments_closed; list_posts takes sort (recent, activity) and returns last_activity_at.
update_community_settings takes google_site_verification and bing_site_verification, and get_community_settings shows both.
The assistant's audit log (GET /api/oauth/audit) returns the arguments with personal data masked.

31 octobre 2026

2026-10-31T23:59:59-03:00

Improvements

Post to the Feed without opening a dialog, from the Write something… box. At the top of the Feed, the Write something… box opens right there, with the Status, Drops and, for the team, Poll tabs; the post goes to the top of the list without reloading the page. The arrow next to New Status opens the box on the tab you pick. See Feed.

Fixes

Profile points and level are now the community total, the same as the ranking. Whoever earned points in different sections saw a smaller number on the profile than on the overall ranking; now both show the same total. See Your profile.
Integrations article with the full list of events. The Integrations & APIs article now lists every event a webhook can receive.

30 octobre 2026

2026-10-30T23:59:59-03:00

What's new

The redesigned Store. The store follows the order in which buyers decide: the How buying works here strip, explaining subscription, add-on and product; the featured item, in a large card; Plans, as pricing cards side by side, with Recommended, the Monthly | Yearly toggle and the yearly discount tag; Add-ons, with the price added to the plan and a button that says what to do (Add to plan, Upgrade or Subscribe to plan); and one-time Products. On Yearly, the card shows the price the way checkout does: "12× of R$ X" on card and the up-front amount. Each plan says how many spaces it unlocks and, with a single plan, the store lists next to it what it opens. See What the store shows.
The Subscriptions page. The community's plans page (/pricing) is now called Subscriptions and uses the Store's cards, with the Monthly | Yearly toggle, the savings tag and the How the subscription works strip. With a single plan, what it unlocks shows beside it. Link-only plans still stay out. See The Subscriptions page.
A padlocked space sells right there. Whoever opens a space unlocked by a plan, add-on or product sees, in the space itself, the cards of what opens it, with the Store's payment: plans side by side, cheapest first, and, when a plan needs an add-on to open the space, the add-on already checked and the Total added up, in a single payment. Only what actually opens that space shows. See The exclusive access screen.
Plan change with the checkout's look. Change plan is now a two-step page: pick the plan (with the Your plan card on top) and confirm, in the checkout's layout, with You have → Moving to. The new plan's add-ons join the same change and the same charge; the ones you already have show as You have it · continues, and the ones the new plan doesn't include, as Leaves. The difference due now can be paid with the saved card, a new card, PIX or boleto; with PIX or boleto, the plan changes once the payment is confirmed. The page also opens from the Store, the Subscriptions page and a padlocked space, already on the chosen plan. See Change plan.
The bell on your browser and phone too. Everything that reaches the bell now also arrives as a notification, by category: besides Messages and Channels, now Team notices (new, on by default), 1:1, Upvote, Achievements, Join requests and Automations. More than 3 notices in a minute become a single notification, "You have N new notifications", which opens the bell. See What arrives as a notification.
Side column in Content spaces. As in the Feed, Content spaces got a column on the right with the most used Tags (clicking one filters the list) and Trending in this space, the 5 posts with the most reactions and comments. On smaller screens, it becomes a tabbed card above the list. See The side column.

Improvements

The savings tag says where you save. On yearly options, the tag now says which payment method the saving is on ("Save 17% with PIX or boleto", "paying up front by card"), so the card never promises what only PIX delivers, and it already carries the up-front amount. The rule is the same in checkout, on the Subscriptions page, in the Store and on a padlocked space. See The savings tag.
Tabs in the chat panel. Conversations and People are now underlined tabs, like the Feed's, with your status on the same row. See Messages.
A post's thread on the side. In a Content space, clicking an item in Trending, Comment or the comment count opens the post and its comments in a panel on the right, without leaving the list. See Content.
When the Spotify player doesn't load, the post shows a card with Listen on Spotify and Load the player again.
The Sale card in the right column. In courses, events and downloads, the price, the status and the shortcut to sell sit in a card at the top of the right column. See The Sale card.
A single management bar in a Downloads space with a single file. See Downloads.
Ranking badges like on the profile. Clicking a badge shows its description, origin and date. See Ranking.
New notification categories arrive on. People who had already chosen their categories get the new on-by-default ones; whatever you turned off stays off.
Download straight from the Downloads list. Each card in the list has a button at the bottom to download or buy without opening the item. See Download from the list.
New security controls.

Fixes

What was unlocked, in full. The page after a purchase now also lists the spaces of a section unlocked for the plan or product.
Automations limit notice in the bell. The notice that the month's fixed-IP calls ran out now shows in the owner's bell and opens the automations. See Workflows.
Translated messages. Some platform messages still showed in English in Spanish, Italian and German.
European Portuguese wording. In the menu, dashboard and settings, the app in European Portuguese now says Subscrições, subscrição and subscrever where it used the Brazilian word for subscription.

For developers

API

Plan change: POST /api/subscriptions/{id}/change-tier and the /change-tier/quote preview accept addOnProductIds (add-ons in the same charge), cardToken (a new card), the idempotency key (idempotencyKey or the Idempotency-Key header) and paymentMethod (CREDIT_CARD, PIX or BOLETO, among the preview's allowedMethods). With PIX or boleto, the response comes with mode: "PENDING_PAYMENT" and pendingChange, and the plan changes once the payment is confirmed. See Plan change.
Padlocked space: when actions has buy or seePlans, the 403 carries data.offers: { plans, addOns, products }, in the Store's shapes. See Responses and errors.
Catalog and Store: each billing option carries isHighlighted, and each plan unlocks (the spaces it opens for the caller). See Checkout.
Content: GET /api/spaces/{id}/sidebar returns the space's tags and trending. See Content.
Notifications: in GET and PUT /api/push/preferences, the phase 2 categories come with available: true, the new teamNotices and each one's label. See Browser and phone notifications.

MCP: technical details

Plan change: quote_plan_change and change_my_plan accept add_on_ids and payment_method; with PIX or boleto, the assistant returns the copy-and-paste code or the boleto, and without a saved card it offers PIX or the link to the prefilled plan change page. See Change your plan and recipes 111 and 112.
Content: the new get_space_highlights tool returns the tags and what's trending in a Content space. The server now has 924 tools. See get_space_highlights.
Notifications: get_my_push_preferences and update_my_push_preferences cover the new categories (team_notices, one_on_ones, upvotes, achievements, workflows, signup_requests).

29 octobre 2026

2026-10-29T23:59:59-03:00

Today's highlights:

Networking
Member page
Side column in the Feed
Recognition with types and art
Chat on your photo, with status
Browser and phone notifications

Networking

What it is. A new space module, in the Community tab of Create Space. People who can help join the program and open their calendar; people looking for help (or business) find the right person in Explore, pick a time and book a session, with the reason for the conversation. Afterwards, both say in How did it go? whether the session happened and, if the space asks for it, rate each other. Sessions turn into numbers on the profile, labels, badges and points. A session is always free: it uses no credits and no payment.

Why it matters. Mentoring, business matchmaking and event networking usually live in spreadsheets and chat groups. Now the community runs the program in a space, with each person's calendar, the calendar invite, the reminder and the emails, and knows how many conversations actually happened.

Where it is. In the menu, Add Space › Community › Networking. Each space is a program.

How to start.

Create the space and pick the Model: Community mentoring, Company mentoring, Business connections, Event networking or Custom. The model fills in every option; Adjust options changes whatever you want before creating.
Choose who can offer sessions and whether joining is direct or needs approval.
Share the space: whoever joins as a mentor sets up their calendar, and everyone else books through Explore.

Example. An association opens "Career mentoring": senior members join with the team's approval and offer 30-minute sessions; newer members search by specialty in Explore, book on the mentor's calendar and, after the conversation, answer How did it go?.

The model fills in the options; everything can change later in Settings.

The program's emails (request to join, approved entry, session request, How did it go?) have the new Networking category in This community's emails, on by default. People in the same program chat without needing a connection. See Networking.

Member page

What it is. Every member has a page in the community, with its own link. It shows who the person is (cover, job title, company, country, languages, links, experience and the signup fields the community lets it show) and what they did there, in the Overview, Activity, Achievements and Credits tabs. Clicking a name opens a short preview, with View full profile.

Why it matters. People get to know each other before starting a conversation, and each one decides what to show. Privacy has 3 levels, chosen for each part of the page: Public, Members or Private. The community's team always sees everything.

Where it is. On your page, Edit profile, with the Profile, Page and Privacy tabs. For the team, Settings › Search and discovery, in the Member pages card.

How to start.

Open your page and, in Edit profile › Page, add the cover, the company and your experience.
In Privacy, choose the level for each part.
For pages that open to people who aren't signed in, the owner or an admin turns on Public member pages (off by default) and sets the most open level allowed for each part.

Example. A mentor leaves her header and experience as Public and her activity as Members: her link, sent to someone outside the community, shows who she is, without her posts. The public page isn't indexed by search engines.

Cover, company, country, languages, links and experience.

Custom fields have a new On the member page option: never, the person chooses, or always. Sensitive fields (phone, documents, health, address…) start at never. See Your profile and Custom fields.

Side column in the Feed

What it is. Next to the list, the Feed shows a column with up to four cards: Upcoming events and Trending posts, on by default, and New members and Leaderboard, which the team can turn on. Each card shows only what the person can open.

Why it matters. Whoever opens the Feed sees the next meetup and what's moving the community right away, without looking for it.

Where it is. In the Feed. To choose the cards, the owner or an admin edits the Feed space, under Side column.

How to start.

Open the Feed: events and trending posts are already there.
To change it, edit the space and turn each card on or off under Side column.

Example. A community with monthly meetups keeps Upcoming events and turns on New members, so newcomers are welcomed right at the door. On a phone, the cards become a carousel above the filters.

Upcoming events and Trending posts next to the posts.

See Side column.

Recognition with types and art

What it is. Every recognition now has a type (Appreciation, Welcome, Milestone, Award, Event shout-out, Course completed or Work anniversary), and each type has its own art and phrase. The card opens with the art and reads "X recognized Y", and the wall shows two columns when there is room. Whoever gave or received it downloads the Card to share and, when allowed, uses Post on LinkedIn.

Why it matters. A thank-you, a milestone and a welcome no longer look the same on the wall and in the Feed, and the recognition leaves the community on a good-looking card.

Where it is. In the Recognition space, in the Type field of Recognize. For the owner and the admin, Edit space › Types and art: turn each type on or off and upload the community's own art.

See Recognition.

Chat on your photo, with status

What it is. The chat opens from your photo, at the top right, in a panel with your conversations, people and your account. You choose your status: Available, Busy (messages arrive without sound) or Unavailable; Away shows up on its own after 10 minutes without activity. People who are out of the app show when they were last online, and everyone decides whether to show theirs.

Why it matters. You can tell whether it's a good time to message someone, and ask for quiet without disappearing from the chat.

Where it is. On your photo, at the top. The status sits next to Conversations and People; Show when I was last online is in the chat's gear.

See Messages.

Browser and phone notifications

What it is. The community lets people know right away, on the computer and on the phone, when someone messages or mentions them, even with the community closed. For now, two categories send notifications: Messages (a new message, a connection request and an accepted connection) and Channels: mentions and replies. Several messages in a row from the same person become a single notification, and tapping it opens the conversation or the thread.

Why it matters. Nobody has to keep the tab open to avoid missing a conversation, and the community is one tap away on the phone's screen.

Where it is. Each person turns them on on their own device: in the window that shows up right after signing in, in the colored band under the header (Turn on) or in My Account › Notices, on the Browser and phone card. That's also where the main switch, the categories, Show the message text (off by default: the notification only says who and what) and the Devices list, with Send test and Remove, live.

How to start.

Sign in to the community and tap Turn on in the window or the band.
Allow notifications when the browser asks.
In My Account › Notices › Browser and phone, use Send test to check.

On the iPhone and iPad, notifications arrive through the app installed on the home screen (iOS 16.4 or newer): in Safari, Share › Add to Home Screen, open it from the new icon, log in again with your e-mail and password and tap Turn on.

See Browser and phone notifications.

Improvements

Ranking with a podium and levels. The top three on a podium, tied positions marked with =, names for the nine levels (from Newcomer to Legend), badges in the list, how far each person moved up or down and a new My engagement. See Ranking.
Survey results as a dashboard. One header, the sections as tabs, cards with responses, response rate and NPS, the Responses per day chart and one card per question. In an anonymous survey, the chart counts published batches, never the time someone answered. See Surveys.
A clearer Performance Review. The cycles list with numbers, filters and fuller cards; a scale of 2 to 10 levels, named however the community wants; Template and score in two columns and a new questions editor; and, for the owner and the admin, who reviews whom. See Performance Review.
Goals & OKRs with a score and the current cycle. The current cycle up front, the cycle result (overall progress and KRs met, partial and missed) and the OKR score from 0 to 1. See Goals & OKRs.
A 1:1 management dashboard. Anyone who leads someone opens the 1:1 space in Manage, with their team's adherence and dates (the owner and the admin see the whole community); Mine has your own 1:1s. See 1:1.
Manage and Mine in Certificates, Development Plan and Performance Review. Whoever runs the space opens the management view, and each person has their own in Mine.
Support tickets like a help desk. A header with Resolve or Reopen, the conversation as a timeline, Reply and Internal note in the same box, photo attachments and an editable Details panel. See Support.
A fuller member page. A compact header with the leader and the main group, Certificates and Badges sections, certificates opened in a viewer, each badge's origin linked and Grant badge in the menu. See Your profile.
The course page. The title under the cover, underline tabs, a leaner side column and a single action button; for the team, the builder with a drag handle. See Courses.
Simpler Networking. Whoever opens the space books a session right away, without joining the program; only becoming a mentor is a request. And the team can limit who may ask to be a mentor by groups, tags or badges. See Networking.
The Feed's side column in tabs. On narrower screens, the cards become a single card with tabs, and Upcoming events shows up to 5. See Feed.
My account reorganized. Sections in groups, your profile edited right there with a single All saved bar, Billing inside My account and Report a problem at the top of the app. See Account and profile.
The same screens across the app. Underline tabs for sections, a Back that goes up one level, the same management bar in every module and the create button always in the space header.
Person card in Channels. Clicking a mention or an author's name opens the person's card, with Send message. See Channel.
A more elegant post card. In the Feed, a Content post card has the cover edge to edge, the title up front and the author with Posted in {space}. The post page uses the same header and the new width. See The post card.
The same filters and list navigation across the app. Before, each screen filtered its own way (tabs, rows of buttons, dropdowns). Now sales, members, subscriptions, coupons, products, logs, listings, courses, campaigns, workflows, scheduling and the other lists use the same pieces: search first, each filter in a button with a menu, active filters as chips with × and Clear filters. On a phone, the filters sit in Filters (N). Screens with many areas, like Members, Monetization and My Account, got a section menu on the left. And the filter lives in the link: reloading or sending the address opens the same view. See Lists and filters.
Feed filters on a single line. The Feed's types become smaller pills; the ones that don't fit go to More ▾. See Filters.
The unread message count fixes itself. Before, after reading and replying to someone's first message, Chat could keep one unread until you reloaded the page. Now the count follows what you've read. See Messages.
Site: the Networking module got its own page, and the Feed page now shows the side column.
New security and privacy controls.
New security controls on API keys.
Automations module on API keys (read). A key with Read on Automations lists and looks up workflows, versions, run history and deliveries; creating, editing and running stay in the app and the AI assistant. See Integrations & APIs.

Fixes

Workflows show each trigger's name. The workflow list and history showed the code of some triggers (like a workflow called by another one). Now they show the name, like the editor does. See Workflows.
"1 request", not "1 requests". The management bars of Scheduling, Classifieds, Parcels, Downloads and Upvote now use singular and plural.
Renewal on the right day. A subscription started on the 29th, 30th or 31st used to slide to the 1st to 3rd after February. Now it stays on its original day and, in shorter months, renews on the last day of the month. Subscriptions started between the 1st and the 28th don't change.

For developers

API

Networking: the new routes are under /api/networking (settings, showcase, profiles, participation, request queue, sessions, reviews, session types and badges). Canceling and rescheduling use /api/bookings/{id}/cancel and /reschedule. See Networking.
Member page: GET /api/members/{id} returns coverUrl, company, country, languages, links, experiences, profileFields, communityStats and sections; PUT /api/members/me/profile saves the page; POST/DELETE /api/upload/cover/member handle the cover; GET /api/members/{id}/activity lists the Activity; without signing in, GET /api/public/members/{id} and /activity. The publicMemberPages and memberPageCeilings settings are in PATCH /api/communities/{id}/settings, and custom fields accept profileVisibility. See Your profile › In the API.
Feed: GET /api/feed/sidebar?spaceId= returns the side column's widgets, already filtered for whoever asks; POST /api/spaces and PUT /api/spaces/{id} accept feedWidgets. The GET /api/feed/recommendations route was removed. See Feed › In the API.
Recognition: POST /api/recognitions accepts type, and every recognition returns recognitionType, typeLabel, typePhrase, artUrl, canShare and canPostToLinkedIn. GET /api/recognitions/types lists the types; PUT /api/recognitions/types/{type} turns one on or off, and POST/DELETE /api/recognitions/types/{type}/art uploads or removes the community's own art. See Recognition.
Chat: PATCH /api/chat/me accepts chatStatus (AVAILABLE, BUSY or UNAVAILABLE); people online return status (including AWAY), and people offline return lastSeenAt when both people keep chatShowLastSeen on. See Messages.
Surveys: GET /api/surveys/{id}/results returns activity, responses per day, counts only. Performance Review: scaleLabels (2 to 10 names) when creating or editing a draft cycle. Goals & OKRs: score from 0 to 1 on cycles and objectives.
Networking: PUT /api/networking/host-rule stores who may ask to be a mentor (groupIds, tags, badgeIds), and GET /api/networking/config returns hostRestricted and hostEligible. Members: GET /api/members/{id} returns, with a session, leader, directReportsCount and groups.

MCP: technical details

Networking: the new tools cover the program (get_networking_settings, update_networking_settings, update_networking_badges), search (search_networking_profiles, get_networking_profile), joining (join_networking, update_my_networking_profile, leave_networking), the queue and the people, for the team (list_networking_requests, decide_networking_request, list_networking_participants…), and sessions (book_networking_session, list_networking_sessions, accept_networking_session, review_networking_session…). create_space and update_space accept the networking argument. See Tools · Networking and recipes 105 to 108.
Member page: update_my_profile edits your page, list_member_page_activity lists the Activity, get_member returns the new fields already filtered, update_community_settings accepts public_member_pages and member_page_ceilings, and custom fields accept profile_visibility. See recipe 101.
Feed: get_feed_highlights replaces get_feed_recommendations, which left the server, and answers "what's trending?" and "what are the upcoming events?"; create_space and update_space accept feed_widgets. The server now has 923 tools. See get_feed_highlights and recipes 102 to 104.
Recognition: list_recognition_types, update_recognition_type, upload_recognition_type_art and remove_recognition_type_art; create_recognition accepts type. See Tools · Members.
Chat: update_my_chat_preferences takes status and show_last_seen. See recipes 109 and 110 in Recipes.
Browser and phone notifications: get_my_push_preferences, update_my_push_preferences, list_my_push_devices, remove_my_push_device (asks for confirmation) and send_test_push, always only with the data of whoever asks. See Through the assistant.
1:1: get_one_on_one_dashboard returns the Manage dashboard. Performance Review: scale_labels and list_review_cycle_assignments (who reviews whom). Goals & OKRs: score and the cycle summary. Surveys: get_survey_results returns activity. Networking: host_rule limits who may ask to be a mentor.

28 octobre 2026

2026-10-28T23:59:59-03:00

What's new

Sign-up with approval. In Settings › Access and sign-up › Access Control, the Allow New Sign-ups toggle gives way to Who can join: Open, With approval or Closed. With approval, Ask to join replaces Sign Up: the person sends their name, email and the sign-up fields, with no password, and the request goes to the pending queue, in Members › Pending. The owner and admins approve one by one or in bulk (up to 100 at a time) and reject with an optional reason; whoever is approved gets the email to create a password. A request nobody answers expires in 30 days. The team is notified in the bell and by email in the new Join requests category, in Emails from this community, on by default. See Sign-up with approval.
For those without access: restricted areas with a padlock. Restricted sections and spaces (by group, plan, product, Members or Subscribers) now show with a padlock to people without access: only the title and description, never the content, and a click leads to the way in (subscribe, buy, sign in). To pick another mode, the owner or an admin edits the section and, under For those without access, chooses Hide, Section only or Section and spaces (the default); each space follows the section or has its own mode (Same as the section, Hide or Show with a padlock). Team-only areas (nobody under Who gets in) never show to anyone else and now carry the Team only badge. See For those without access.
Heads-up, if you have restricted areas that shouldn't show. Every section that already existed is now set to Section and spaces, and every space to Same as the section: group, subscriber or member areas that used to disappear for people without access now show with a padlock, with their title and description. For an area to stay invisible, switch it to Hide.
Talk to the team. In a padlocked area unlocked by a group (or with nothing on sale), the exclusive-access screen has a Talk to the team button, which opens a chat conversation with someone on the team who can grant access. It shows when chat is on and someone is available to answer. See The Talk to the team button.
Ten new platform messages on WhatsApp. With WhatsApp on, Memberfy now sends on its own: the visitor at the front desk (to whoever invited them), the parcel received, the booking reminder 1 hour before (to whoever booked and to the host), the subscription renewing in 3 days, the card expiring this month, the refund processed, the waitlist spot opened, the reply to a support ticket and the certificate issued. Sign-up approved arrives with sign-up with approval, below. They all start on: the community turns off what it doesn't want under Platform messages, on the WhatsApp card, and each person in My Account › Notices. The Business or Scale plan, quiet hours, the daily cap and the per-person limit apply. See Platform messages.
SMS and WhatsApp consent declared by the team. When the community collected consent outside Memberfy (a meetup form, a signed form), the owner or the admin records that consent through the API or the assistant, declaring that the community collected it. In the spreadsheet import, the SMS and WhatsApp consent columns, with the attestation, now also apply to existing members, and the spreadsheet's phone replaces the one on the profile. Anyone who left the channel is never re-enrolled. See Consent declared by the team.
The phone the team provides can receive right away. The phone the team provides when declaring the consent, through the API, the assistant or the import, gets SMS and WhatsApp without the code verification, while it is the profile's current phone. It is not verified: verification codes still require the person, and consent, opt-out (including STOP and SAIR), quiet hours and caps apply just the same.
More templates in workflows. The Send WhatsApp block now offers Booking reminder, Subscription renewing, Refund, Waitlist spot and Certificate issued. See the full list in Send SMS and Send WhatsApp.
Each Feed chooses what it shows. When creating and editing a Feed space, the owner and the admin choose What this feed shows: Only this space's posts or Every space in this section. A section can now have a general Feed that brings everything together, plus News or Jobs feeds with only what's posted in them. The only Feed of a section starts out bringing the section together; a Feed created in a section that already has one starts out with only its own posts. See What this feed shows.
Heads-up for sections with more than one Feed. In those sections, each Feed now shows only its own posts. No post is gone: each one stays in the space where it was published. To make a Feed bring the section together again, edit the space and choose Every space in this section. The only Feed of a section stays as it was.
Clickable tags in Feed and Content. Feed statuses get a Tags (optional) field, when posting and when editing, like Content posts: up to 10 tags of 40 characters. Tags show on the card as #jobs, and a click filters the list right there, with Showing only #jobs × at the top; the × goes back to the full list. Case and accents don't matter: Jobs, jobs and #jóbs filter the same. The filter stays in the address (?tag=jobs) and respects each person's access. See Clickable tags.
Who is here and team editing. Each screen header shows, on the right, the faces of who else is there (faded when away for 30 seconds, with a pencil when editing). In the editors (event, campaign, e-mails, workflow, course, form, survey, certificate template and Settings), Someone is also editing and Someone saved changes appear, with Reload; and if someone saved before you, the Someone else saved before you window lets you choose between See the saved version and Keep mine. Nothing is overwritten without warning. With the community chat off, no faces show; only people editing the same item still see each other. See Who is here and team editing.
A post becomes an e-mail campaign in one click. In the … menu of a published post (on the card, on the post page or in the Feed), Create email creates a campaign draft with the title, the subtitle, the cover, the whole text and the Read in the community button, and with the People who can access {title} audience, recalculated on every send: a subscribers-only post reaches only those who can open it. Moderators and finance create the draft; only the owner and admins send it. See Send a post by e-mail.
Posts with "…see more" and post reads. In the Feed and in the space's list, the text of a long post is cut at about five lines, with …see more, which opens the whole text right there (see less collapses it); the button is centered, with a chevron, in the community's color. Title, cover and player stay outside the cut; in a cut post, the link cards and the list of links only show up after …see more (short posts show everything, as before), and the post page shows everything. On the post page, the owner, the admin and the author see Reads of this post: how many people opened the post, opened …see more and clicked a link, and the Most clicked domains (only the domain is kept; clicks inside players such as YouTube and Spotify don't count). Each number counts one person per day, and counting starts today. In Administration › Analytics › Overview, the Most read content block shows the period's most read posts, for the owner and the admin. See Reads of this post and Most read content.
Pin posts in the Feed and in the space. In the ⋮ menu of a Content post, in the Feed and in the space's list, the owner, the admin and the moderator now have Pin to top and Unpin, as status and events already had. The pinned post moves to the top of the space and of the Feed with the Pinned bar and shows whole, with no …see more and the link cards in view. See Pin to top.

Improvements

Phone and channels in Profile. In My Account › Profile, right below Phone, Confirm number sends the 6-digit code on WhatsApp (by SMS when the community doesn't use WhatsApp), and one switch per channel, Get notices and news by SMS and on WhatsApp, authorizes reminders, tickets, pending items and news at once. My Account › Notices keeps only the categories and the WhatsApp messages. See My Account › Profile.
Marketing templates only for people who accepted news. Before, Community notice and Feedback received reached people with only the service consent. Now, since WhatsApp classifies them as marketing, they only reach people who accepted news on WhatsApp, like Purchase not completed, Mention and New content. In a workflow, a Send email after the block reaches everyone else. See Marketing templates.
A deleted item or wrong link is now clear. Opening an event, course, campaign, product, workflow or other item that was deleted says it no longer exists and shows the way back to the list. A connection failure appears separately, with "Try again".
Readable names in approved templates. On the WhatsApp card, the Approved templates list now shows the ten new templates with their name and purpose in the dashboard language (Visitor arrived, Booking reminder, Support ticket answered…), instead of the internal code.
The new post notice goes only to people who can open the post. In a community with paid entry, a members-only post no longer notifies people still waiting for their entry to be released. See New content notices.
The post's player moves up to the cover's place. A post with no cover and no video of its own now opens with the first audio or video link in its text (Spotify, YouTube, Vimeo, SoundCloud…) at the top, on the Feed card, in the list and on the post page, without repeating the player below. A podcast episode with only a Spotify link already shows with the player. Plain link cards stay where they are. See Links become a player or a card.
The official community in the directory. Memberfy's own community now shows first in the directory (hub.memberfy.net), with the Official community badge: news, tutorials and exchange among people who lead communities. The website gained an Our community link that takes you there.
Website: home page and the pages for communities, companies and HR, and coworkings rewritten, each with the Memberfy Cast episode for its audience.
New security controls.

Fixes

The e-mail button opens the post. Read in the community in new post notices and in the campaigns' Latest posts block opens the post again, including in e-mails already sent.
Signing up with an e-mail that has an account in another community. People who already had an account in another Memberfy community got "e-mail already registered" when signing up to yours. Now the sign-up works with the same e-mail and creates a new, separate account with its own password. The e-mail is only refused when it already has an account in your community.
Back on a post opened from a direct link takes you to the space. When a post was opened from a direct link, clicking Back did nothing. Now the button takes you to the post's space.
Pinning in the Feed works again for the team. Pinning a status, an event or a post in the Feed works again for the owner, the admin and the moderator.
The Feed shows your options right after login. After you sign in, the Feed already shows your ⋮ menu and Edit, with no need to reload the page.

For developers

API

Directory: GET /api/public/hub/communities and GET /api/public/hub/communities/{slug} carry official: true on Memberfy's official community, which comes first in the list; the other ones don't carry the field. See Hub.
Sign-up with approval: signupRequiresApproval in PATCH /api/communities/{id}/settings; POST /api/auth/signup-request (public, always 202); GET /api/signup-requests, POST /api/signup-requests/approve and POST /api/signup-requests/reject; the member.joined webhook gains source: approval. See Sign-up and entry.
For those without access: lockedDisplay on POST/PUT of sections and spaces, locked and lockReason in the listings, and GET /api/sections/{id} with denial. See Visibility and access › In the API.
Talk to the team: POST /api/chat/contact-team (spaceId or sectionId); a padlocked refusal carries canContactTeam.
moments in /api/whatsapp/settings and whatsapp.moments in /api/members/me/notice-preferences gain visitorArrived, parcelArrived, bookingReminder, subscriptionRenews, cardExpiring, refundProcessed, waitlistOffer, supportReply, certificateIssued and joinApproved. whatsappNode.templates (GET /api/workflows/triggers) gains bookingReminder, subscriptionRenews, refundProcessed, waitlistOffer and certificateIssued; a template outside the list comes back with whatsappTemplateInvalid. category in GET /api/whatsapp/templates shows the classification WhatsApp applied (MARKETING included); people who didn't accept news are skipped with whatsappNoConsent.
feedScope (space or section) in POST /api/spaces and PUT /api/spaces/{id}, Feed spaces only, for owner and admin. GET /api/feed with spaceId follows the space's feedScope, and the new sectionId brings the whole section together. See Sections and spaces and Feed.
Consent declared by the team: POST /api/contact-consent/attestations (owner and admin; attestation: true, channels, purpose, up to 200 members; the response has sendable per member), the team origin and the attestationMethod field in GET /api/members/{memberId}/contact-consents; in the import, smsConsent and whatsappConsent with the attestation also apply to existing members, with the row warnings CONSENT_WITHDRAWN and PHONE_KEPT_VERIFIED. See SMS and WhatsApp notices › In the API.
Tags: tag on GET /api/feed and GET /api/content; tags (up to 10 of 40 characters) on POST and PUT of /api/status and /api/content. See Content › In the API.
Version in the editors: saves accept updatedAt (on the community row, settingsUpdatedAt) or If-Unmodified-Since and answer 409 with the current version when another save came first; it is optional. See Version conflict. On the WebSocket, presence.join, presence.leave and presence.active, the presence snapshots and the item.saved notice. See Realtime.
Campaign from a post: POST /api/campaigns/from-content (contentId; team), the itemAccess: { type: "content", id } audience (exclusive), itemAccess in the audience preview, sourceItem on campaigns and canCreateCampaign in the Content list, the post detail and the Feed. See E-mail campaigns › In the API.
Post reads: GET /api/analytics/content (the period's most read content; owner and admin) and GET /api/analytics/content/{contentId} (one post's metrics; owner, admin and the author, 403 for others). The collector POST /api/analytics/events accepts post_expand and post_link_click (domain only), and page_view carries contentId; the post detail carries canViewMetrics. See Analytics › In the API.

MCP: technical details

list_signup_requests, approve_signup_request and reject_signup_request handle the join-request queue; update_community_settings accepts signup_mode (open, approval, closed). See Tools · Members.
locked_display on create_section, update_section, create_space and update_space; list_spaces shows locked and lock_reason. See Tools · Community and structure.
contact_team opens the conversation with the team from a padlocked area.
create_space and update_space take feed_scope (space or section, Feed module only); list_spaces shows each Feed's feed_scope; list_posts takes section_id, and a Feed's space_id follows its feed_scope. The delete_section description is fixed: the section must be empty, and its spaces are deleted first with delete_space. See Tools · Community and structure.
attest_contact_consent records the SMS or WhatsApp consent the community declares it collected (asks for confirmation); preview_member_import and start_member_import take the sms_consent and whatsapp_consent columns, with the attestations; list_member_contact_consents shows the team origin; the result of attest_contact_consent has phone_verified and sendable. See recipe 99.
list_posts takes tag; create_post, create_short_post and update_post take tags. See Tools · Content and recipe 98.
create_campaign_from_content creates the campaign draft from a post (the app's Create email); create_campaign, update_campaign and preview_campaign_audience accept the item_access audience, and the send_campaign and schedule_campaign confirmation shows the post title and how many people receive it, or warns when the post went offline; list_posts carries canCreateCampaign. The server now has 883 tools. See Tools · Community and structure and recipe 100.
analytics_report gets view: "content", the period's most read content (owner and admin), and the new tool get_post_metrics reads a post's reads, expansions, clicks and most clicked domains, by id, link or title (the author sees only their own posts). Ask "Which posts were most read this month?" or "How many clicks did the 'Welcome' post get?". The server now has 884 tools. See get_post_metrics.

27 octobre 2026

2026-10-27T23:59:59-03:00

What's new

New event editor on the event page itself. Before, creating an event meant filling a long form in a window. Now New Event creates a draft and opens the event page, the same one members see, and each part is edited in place: cover and card image (with Adjust framing), name, date, location, description, organizers and speakers, tickets, registration questions, certificate, recording, Who can see it and check-in. The draft saves itself and belongs to the team only: members don't see it, it doesn't enter the Feed and it notifies no one. The To publish list shows what is missing, Preview shows the page as members will see it, and Publish asks whether to send the e-mail notice and puts every ticket on sale. On a published event, Edit event turns on the same mode, with Save changes. Drafts live in the list's Drafts tab. See Events.
Badges in Engagement. In Administration › Engagement, the Badges tab (owner and admin) creates seals with an image, name, description and Public or Private. A badge arrives by hand (Give to…, up to 100 people, or on the profile), on course completion (Badge on completion, on the course's Completion tab), on event check-in (Badge on check-in) or by workflow, and the same person never gets the same badge twice. The recipient is notified in the bell and by e-mail, in the new Achievements category, on by default. See Badges.
The profile shows engagement. Each member's profile shows the points, the level and the Achievements tab, with badges and certificates. Private badges only show for their holder and for the owner and admins; certificates, for the person and the team, until they choose The whole community. See The profile shows engagement.
Adjust points on the profile and in the ranking. Before, giving someone points took a workflow. Now the owner and the admin click Adjust points, on the profile or in the ranking row's menu, with the points and the reason, which the person sees in their history. See Gamification.
Multiple-choice field. A new custom field, Multiple choice, with 2 to 50 options and, optionally, a minimum and maximum: on sign-up, on the profile and on the record. A Choice can become multiple choice even with answers. The member list gets a filter per field ("Interests contains any of: Linux, Cloud"), the import accepts Linux; Cloud in one cell and offers to add missing options, the workflows' Profile field condition gets contains any of, contains all of and does not contain, and the campaign variable comes out "Linux, Cloud". See Custom fields.
Plan quotas. Each plan has its own quotas: AI (60 to 500 transcription minutes and 1,000 to 6,000 uses a month), SMS (from Growth up), WhatsApp (300 on Business, 500 on Scale), converted video minutes, campaign recipients (1,500 to 30,000 a month), workflow e-mails (40 to 350 a day) and storage (5 to 250 GB). On a monthly plan they renew on the 1st; on an annual plan, what's left adds up until renewal. At the limit, the video plays the original file, the AI buttons say so, the campaign tells how many fit and storage refuses only new uploads. Transactional e-mails are never limited. See Plan and extensions.
WhatsApp with platform messages. Every WhatsApp message goes out in an approved template, with a button that opens the right page of the community, and Memberfy sends on its own the payment confirmed or declined, the ticket, the event reminders (24 hours before, starting and live, with the map for in-person events), the proposal decision, the 1:1, the feedback and the HR to-dos. The community turns off what it doesn't want, and each person picks theirs in My Account › Notices. WhatsApp is on the Business and Scale plans. See Platform messages.
SMS and WhatsApp notices. The community turns SMS and WhatsApp on in Administration › Settings › E-mails and notifications, with a required daily cap, the month's usage against the plan's quota and a test to your own phone. Service notices go out (the event reminder, the PDI and 1:1 reminders, and the new Send SMS and Send WhatsApp workflow blocks) to phones in every country (for now, SMS to the United States is left out), never between 9 p.m. and 8 a.m. in the recipient's time zone, with at most 5 workflow messages per person per day in each channel (adjustable from 1 to 20), and only to people who consented at sign-up, login or import (only people the import creates) and verified their phone with a code. Each person picks channel and category in My Account › Notices; the SMS link removes them from this community only, and replying STOP stops the whole channel. See SMS and WhatsApp notices.
AI blocks in Workflows: Claude and ChatGPT. A workflow step asks the AI for a text or a JSON: a personal welcome, a ticket triage, a form summary. The call uses the community's own API key, kept in Variables and keys, and the AI limits card holds the spending per call, per run and per day. The history shows the model, the tokens and the duration, never the key, the prompt or the answer. See AI blocks.
New actions in Workflows. Publish a post, Issue a certificate, Recognize, Block in the chat, Schedule a 1:1 and Add a PDI action, which shows in the plan as "Created by the workflow …". And the admin now uses the same actions as the owner in workflows. Through the assistant, the AI limits and adjusting someone's points too. See Platform actions.

Improvements

Report a problem in the app. In the sidebar, below My account, a form to tell the Memberfy team what went wrong, with what you were doing and, if you like, a screenshot. The report arrives with the page and the app version, and you get a reference number. See Account and profile.
Simulate and email me. A workflow simulation sends you the e-mails the person would get, with [Test] in the subject, without counting as a send. See Simulate, test and estimate.
A deleted group's name can be used again. See Groups and org chart.
The site covers the custom domain and the new Workflows. Before, the Memberfy site didn't say how to connect your brand's domain. Now it explains that it sits next to the memberfy.net address, on any plan, and the pricing page lists webhook calls, Variables and keys, platform actions, calling another workflow and the run history, with fixed IPs from Business up. See Custom domain and Workflows.
Help in the site menu and Workflows on the platform page. The site menu gained a Help item, before Pricing, that opens this Help Center in your language, on phones and in the footer too. And the platform page gained a Workflows section: triggers, waits and conditions, Call webhook, platform actions, the run history and the assistant building the automation.
Workflows in the site's Platform menu. The Platform menu on the site gained a Workflows item that goes straight to the section, on desktop and on phones.
Campaigns on the platform page and in the site menu. The platform page gained a Campaigns section, and the Platform menu an item that goes straight to it: the e-mail library and sends, the block editor and test send, audience and scheduling, opens and clicks, automatic and default e-mails, opt-out by category, the sending reputation guard and the assistant building the campaign. See E-mail campaigns.
The Help Center shows how to give points by hand and segment by field. The articles said this was not possible yet. Now they explain the Workflows way: the Adjust points step in a Manual workflow, with Run now for people or an audience, and the Profile field condition with Send e-mail or a tag to segment the campaign. See Gamification and Custom fields.
A clearer New key in Variables and keys. The dialog says what a key is for and that nobody sees the value again; the Name adjusts as you type and shows how to write it in the block ({{env.CRM_TOKEN}}), the Value has a show and hide button, and Can only be sent to is optional: empty, the key can be used with any address. See Variables and keys.
The Messages bar is back. When collapsed, the chat is again the Messages bar in the corner of the screen.
Settings reorganized: one menu by topic, search and a page for each topic. Each page saves on its own, and old links keep working. See Community settings.
Custom domain: a prominent warning to turn off the DNS proxy. When you add the domain and next to the record, the screen explains how to leave the cloud gray on Cloudflare or turn off proxy, CDN or acceleration with other providers. See Custom domain.
Storage follows the plan. Before, going over the limit only warned. Now, at the plan's limit, new uploads of videos and files are refused with a notice, and nothing already stored goes offline. See Plan and extensions.
New security controls.

Fixes

The event's Private option now really hides the event. Before, choosing Private saved the event as subscribers-only, and it kept showing up for anyone with a plan. Now Private keeps the event to the team only, and the subscribers option shows its right name, Subscribers. See Who sees the event.
The Field condition with an operator now works correctly. Before, in workflows, the Profile field rule with an operator (and the Variable rule on a profile field) compared an empty value and didn't take the right path. Now it reads the field's current value. See Workflows.
An option removed from a choice. Before, whoever had picked a removed option kept showing the old value. Now the option leaves the profile, the filters and the variables, and comes back if the option does. See Custom fields.
Custom domain: with the DNS fixed, Check now tries to issue the certificate again on its own. Before, a certificate that failed with the proxy on stayed stuck even after the proxy was turned off. See Custom domain.

For developers

API

Event drafts (contract change): POST /api/events now creates a draft and only requires spaceId; publish: true keeps the previous behavior. New routes PATCH /api/events/{id} (only the fields sent, with updatedAt or If-Unmodified-Since; 409 if another save came first) and POST /api/events/{id}/publish (notifyByEmail; 422 with what is missing). GET /api/events takes status (DRAFT, all) for the team; the event carries status, publishedAt, updatedAt, readiness and the images' focal points. visibility takes private. The event.created webhook now fires on publishing. See Creation order.
New SMS and WhatsApp routes: GET and PUT /api/sms/settings and /api/whatsapp/settings (turning on needs dailyCap), POST /api/sms/test and /api/whatsapp/test, GET /api/whatsapp/templates, POST /api/sms/segments, POST /api/members/me/phone-verification and .../confirm, GET and PUT /api/members/me/notice-preferences, GET /api/members/me/contact-consents, GET /api/members/{memberId}/contact-consents and GET /api/contact-consent/texts. Sign-up and login accept smsConsent; the import, the smsConsent target with smsConsentAttestation. Workflows get the sendSms and sendWhatsapp blocks. See Order of creation.
Badges: GET and POST /api/badges, POST /api/badges/image, GET, PATCH and DELETE /api/badges/{id}, GET /api/badges/{id}/holders, POST /api/badges/{id}/grants (up to 100), GET and POST /api/members/{memberId}/badges and DELETE /api/members/{memberId}/badges/{badgeId}; completionBadgeId on the course and checkInBadgeId on the event; engagement in GET /api/members/{id} and certificatesVisibility in PUT /api/members/me. Webhook events badge.awarded and badge.revoked; in workflows, the badge.award and badge.revoke actions and the badge.awarded and badge.revoked triggers. Contract change: badges in the ranking (GET /api/gamification/leaderboard and GET /api/gamification) is now [{ id, name, imageUrl }].
Multiple choice: the MULTI_SELECT type in /api/member-fields, with minSelections and maxSelections; the value is the list of the options' value; GET /api/members?fieldFilter[<key>]=a,b; in the import, unknownOptions in the summary. A choice whose option was removed now reads null.
Quotas: GET /api/entitlements/community gains video.transcodeMinutes and campaigns.recipients, and each meter gains period, available and resetsAt; GET /api/campaigns/quota gains recipients. A campaign over the recipients: 429 quota_recipients; an upload over storage: 409 storageLimitReached.
SMS and WhatsApp: personDailyCap in /api/sms/settings; moments, upgradeRequired and blockedCountries in the settings; whatsapp.moments and whatsapp.marketing in /api/members/me/notice-preferences; the sendWhatsapp block is now { template, variables, link }; the import takes whatsappConsent. Turning WhatsApp on outside Business and Scale: 403 whatsapp.notOnPlan.

MCP: technical details

Event drafts: the new publish_event tool (team) publishes a draft and asks to confirm when it sends the e-mail notice, with how many people get it; with notify_by_email: false, it publishes at once. create_event creates the draft and publishes it at the end (as_draft: true stops at the draft; if something is missing, the draft stays and publish_missing says what); start becomes optional. update_event saves only the fields sent, with updated_at, and explains when another save came first. list_events takes status (DRAFT, all) for the team. visibility takes private. 877 tools. See Tools · Events.
14 new tools, 868 in total: get_sms_settings, update_sms_settings, send_sms_test (asks to confirm), count_sms_segments, get_whatsapp_settings, update_whatsapp_settings, list_whatsapp_templates, send_whatsapp_test (asks to confirm), get_my_notice_preferences, update_my_notice_preferences, list_my_contact_consents, request_phone_verification, confirm_phone_verification and list_member_contact_consents. The workflow guide describes sendSms and sendWhatsapp and gets 8 recipes (56). See Tools.
8 new tools, 876 in total: list_badges, get_badge, create_badge, update_badge, delete_badge (asks to confirm), award_badge (up to 100 people, with dry_run), revoke_badge (asks to confirm) and list_member_badges. create_course/update_course take completion_badge, create_event/update_event, check_in_badge; get_member carries engagement, and update_me, certificates_visibility. The ready-made recipe Give a badge (award_badges, 21 in total). See Tools · Content and engagement.
create_member_field and update_member_field take multi_select, min_selections and max_selections; update_member_field_values takes the list of options; list_members filters with field_filter; the import shows unknown_options.
update_sms_settings takes person_daily_cap; get_whatsapp_settings and update_whatsapp_settings handle moments; update_my_notice_preferences takes whatsapp.moments and whatsapp.marketing. The workflow guide builds sendWhatsapp with template, fields and the button's page, and the workflow recipes go up to 61.

26 octobre 2026

2026-10-26T23:59:59-03:00

Workflows: new editor and results
Run now, Scheduled and Webhook received
Call webhook and Variables and keys
Run history from the inside
The assistant learns to automate
Platform actions and Call workflow
Custom domain
My tickets
Simpler screens

Workflows: new editor and results

What it is. The Workflows editor now takes up the whole screen, with the blocks by category in an accordion with search, each block's panel one click away, a context menu, keyboard shortcuts and a minimap. Each workflow has one trigger, chosen in the family's block (Members, Purchases, Courses…), and every path ends in End: success or End: error. Actions have an error exit, the list shows Entered, Finished, Errors and Success, and the owner and the admins get a notice when a workflow goes over 20% errors.

Why it matters. Now you can tell whether each run went well and what to do when it did not. And messages get personal: the course name in the congratulations, the product and the amount in the thank-you for the purchase, with Insert variable in every text, including the e-mail.

Where it is. Administration › Workflows.

How to start. Open a workflow, click an e-mail block and use Insert variable to put {{course.name}} in the subject; connect the "ok" exit to End: success.

Also in this release:

Variables between blocks and the Variable condition, with operators by type (text, number, date, list, yes/no).
The Write to log block, which shows up in Logs › Workflows.
29 triggers with each module's lifecycle (downloads, posts, events, courses, spaces and forms), Someone comes back after N days away, First purchase only and the DM received.
Sending postponed by quota: the frequency limit, the daily limit, the sending reputation and the suspension postpone the step instead of skipping it.
On whose behalf: the community chooses whether workflows send DMs, comment and react on behalf of The whole team or Owner only; no one needs to agree to it or approve texts anymore.
Active workflows by plan: 3 on Starter, 10 on Growth, 30 on Business and no limit on Scale.
The trigger for newcomers is now called New community member, and the condition takes several tags, space access and visit, and event registration and attendance.

Run now, Scheduled and Webhook received

What it is. Three new triggers: Manual (Run now, for chosen people or an audience, with the count and the confirmation first), Scheduled (every day, week or month, for an audience) and Webhook received, where another system (a CRM, a form, n8n) calls an address and starts the workflow for the person. On the Someone has not signed in for N days trigger, Include who has already gone more than N days without visiting also brings in people who were already inactive. See Incoming webhook.

Call webhook and Variables and keys

What it is. The Call webhook block sends an HTTPS call to another system in the middle of a workflow (a CRM, a spreadsheet, n8n), with a maximum response time of 2 to 15 seconds and new attempts at 1, 5 and 15 minutes when the destination fails. Tokens live in Variables and keys, the community's vault: the value is stored encrypted, never comes back to the screen and only goes to the hosts you allow.

Why it matters. What happens in the community reaches your other systems right away, with no spreadsheet in between, and the answer can decide the next step.

Where it is. Administration › Workflows › Variables and keys, and the block under Integrations.

How to start. In Variables and keys, accept the personal-data notice and create the CRM_TOKEN key with the CRM's host; in the workflow, add Call webhook and use {{env.CRM_TOKEN}} in a header.

Example. A completed purchase calls the CRM with the name, e-mail and product; if the CRM answers with an error, the error exit sends a DM to the team.

On the Business and Scale plans, calls go out from fixed IPs, up to 10,000 a month, and the history shows where each one went out from. See Call webhook.

Run history from the inside

What it is. Each workflow's History now has the list of runs next to the detail, with filters by period, result and person. Each step shows what went in and what came out when it ran: the text sent, the e-mail's delivery, what the person had in a condition ("Has: VIP"), the status and duration of a webhook call. See History.

The assistant learns to automate

What it is. The assistant (Claude, ChatGPT) now knows Workflows from the inside: say the rule in your own words ("whoever buys the course gets 7 days of access to the mentoring") and it builds the workflow, simulates it and turns it on after your ok. It also suggests the workflow that automates what you just did (a campaign, certificates, invitations).

Platform actions and Call workflow

What it is. Workflows now do what the team does on screen: each platform action is a block (Change role, Adjust points, Register for event, Enroll in course, Give courtesy access, Send an in-app notice and others), and the Call workflow block runs another workflow and uses what it returns. So a shared welcome lives in one workflow, called by many.

Where it is. In the editor, under People, Content, Messages and Flow.

How to start. In a purchase workflow, add Give courtesy access, pick the plan and For how many days, and connect the "ok" exit to End: success.

A workflow never does more than whoever turns it on: an admin can see and simulate, but not change, a workflow with actions only the owner may do. See Platform actions and other workflows.

Custom domain

What it is. The community now opens at your brand's address (community.papodesysadmin.org) and at the Memberfy one (papodesysadmin.memberfy.net), at the same time, without redirecting. When the custom domain becomes Active, it becomes the Primary address: links, e-mails and search engines start using it. The security certificate is issued and renewed on its own, and the custom domain is included in every plan.

Why it matters. Before, a custom domain meant asking the Memberfy team, and the Domain field in the settings only stored a text. Now the owner or an admin does it all from the screen and follows each step, and anyone who saved the old link keeps coming in.

Where it is. Settings › General, in the Custom domain block (owner and admin). The Domain text field is gone.

How to start.

In Your domain, type the address and click Add domain.
At your DNS provider, create the record the screen shows (Type, Name and Target, with Copy), DNS only, no proxy.
Follow Waiting for DNS → Verifying → Certificate issued → Active, or use Check now. You get an e-mail when it becomes active.

Example. Papo de Sysadmin adds community.papodesysadmin.org, creates the CNAME community in Registro.br and, in about an hour, invitations already go out with the new address. To change later, Change domain keeps the old one up until the new one becomes active.

Each error (wrong record, A record, proxy on, root domain, CAA, the 7-day deadline) shows up on the screen with what to do. See Custom domain.

My tickets

What it is. The My tickets tab, in My Account, brings together the tickets for every event: the upcoming ones, with the entry QR and code, and the past and canceled ones. See Account and profile.

Simpler screens

Events: the management bar shows the sale's state ("Sales open · 79 of 80 seats"), ticket types are choice cards with a single button, and the checkout shows the amount on the button (Pay R$ 40.00).
Channel: Mute channel, who is in the conversation and search in the channel; deleting your own message has Undo.
Undo instead of confirming when removing a key result, a 1:1 agreement or your own channel message.
Surveys: the editor's bar has only the title, the state and the main action, and an identified survey whose introduction promises anonymity shows a warning with Fix the text.
Upvote: sorting and filtering in compact menus, and the topic's bar with Edit and Change state.
Performance review: the module has this name, and Open the cycle sits in the management bar, with the confirmation in a window.
1:1: logging only goes up to today; a future 1:1 is scheduled.
Spaces: a space's type does not change after it is created.
Sending reputation: the banner shows the community's own numbers against the limit.

Improvements

More webhook events: there are 93, with each module's lifecycle, member.returned and message.received. See Webhooks.
A space you cannot access says why and what the next step is.
Access request on the website: after you send the form, the page scrolls straight to the confirmation.
A workflow never does more than whoever turns it on: steps act with the role of whoever saved, turned on or ran the workflow, and a workflow with actions only the owner may do opens read-only for an admin. See Which role the steps act with.
Delete run and Clear history: one finished run, or all of them up to a date, leave the history and the numbers; they still count for whoever enters Only once. See History.
The menu updates right away: a space or section created, edited or removed shows up in everyone's menu without reloading, and anyone inside a space that was removed or that they lost access to goes right away to the no-access screen. See Visibility and access.
Workflow editor: a click on a block no longer marks the drawing as changed.
New security controls.
A leaner Monetization: the General tab of Monetization no longer has the This month, by currency block; the balance cards already show everything in the community's currency. See Balance and statement.
Dates in your language's format: dates and times show and are typed in the format of the language chosen in the app, no longer the browser's (in English, mm/dd/yyyy and 12 h). The calendar is still on the icon.
Clearer Business Information: submitting with something missing marks each field and scrolls the page to the first one; the partners block explains that you need to click Add Partner; and, after you submit, the Next: payout details button takes you to the payout account. See Business Information.
Payout details without waiting: you can send your payout details together with the Business Information, without waiting for the approval; both are reviewed together. See Business Information.

Fixes

The 1:1 history shows who canceled a meeting and the pair's last meeting.
The Billing page for community members now loads even when the community has not set up payouts yet (before, it kept loading forever); the card section still says that card payment is not available yet.
In Firefox, date fields (for example, the founding date in the billing information) accept a typed date again, and the calendar is still available from the icon.
The payout registration is no longer rejected when the revenue is typed with cents (3000.00) or when the address has no complement.

For developers

API

Workflows: POST /api/workflows/{id}/run, /stop, GET /api/workflows/{id}/summary, /variables and POST /api/workflows/variables, GET and PUT /api/workflows/settings; one trigger per design, endSuccess and endError, and design errors with the block (singleTriggerOnly, pathWithoutEnd, variableUnavailable). See Workflows.
Incoming webhook: POST /api/workflow-hooks, with the token in X-Memberfy-Hook-Token and the HMAC signature. See Incoming webhook.
GET /api/my/tickets and channel muting.
Workflows, part 2: the http, platformAction and runWorkflow blocks, the workflow.called trigger, platformActions and subWorkflow in GET /api/workflows/triggers, the vault under /api/vault, DELETE /api/workflows/runs/{runId} and POST /api/workflows/{id}/runs/clear, and the errors actionAboveRole, subWorkflowAboveRole (422) and workflows.actionsAboveRole (403). The run detail brings the drawing's version and what each step received and returned.
Team routes: POST /api/events/{id}/registrations, POST /api/courses/{id}/enrollments (free items) and POST /api/notifications/send (up to 100 people). See Creation order.
Custom domain: GET, PUT and DELETE /api/communities/custom-domain and POST /api/communities/custom-domain/check. PUT /api/communities/{id} with another domain returns 400 (param: "domain"); domain is now the primary address, written only by Memberfy. See Creation order.
Realtime: the menu.changed topic in the community room. See Realtime.

MCP: technical details

Workflows: run_workflow, stop_workflow, get_workflow_summary, list_workflow_variables, preview_workflow_text, get_workflow_settings, update_workflow_settings and the 5 incoming webhook tools. See Tools · Community.
mute_channel, unmute_channel and list_my_tickets.
Automation guide: the memberfy://guides/workflows resource, get_workflow_guide, suggest_workflow (team, no confirmation), 39 recipes, the workflow_playbook menu recipe and next_steps that suggest the right recipe.
delete_workflow_run and clear_workflow_runs (owner and admin, with confirmation); list_env, set_env and delete_env (the value never comes back); register_member_for_event, enroll_member_in_course and send_member_notice (owner, admin and moderator, no confirmation).
Custom domain: get_custom_domain, set_custom_domain, check_custom_domain and remove_custom_domain (owner and admin; only removing asks to confirm), and the same four for the SuperAdmin on another community (*_community_custom_domain). The next_steps show the DNS record to create. See Tools · Community.
The server now has 851 tools and 20 recipes in the menu.

25 octobre 2026

2026-10-25T23:59:59-03:00

Channel
Upvote
Log 1:1 and Community 1:1s
Performance Review: nomination, calibration, 9-box and matrix
Workflows
E-mail library and default e-mails
Ticket types and batches
Sending reputation

Channel

What it is. A new space module, in the Community tab of Add Space: the group's 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. See Channel.

Why it matters. The day-to-day conversation stays inside the community, without a separate WhatsApp group: whoever joins the space already has the history, and the staff moderates right there.

Where it is. Add Space › Community › Channel. Unread messages show up in the menu, next to the channel's name.

How to start. Create the space, choose in Who can post who writes (whoever can't only reads and reacts) and send the first message.

Example. An #event-announcements channel, where only the staff posts and everyone reacts, and a #networking one, open to everyone, with threads by topic.

Upvote

What it is. A new space module, in the Community tab: a board where members propose topics, vote (one vote per person, retractable) and comment, and the staff changes each topic's state (Planned, In progress, Done, Archived with a reason) and merges duplicates. See Upvote.

Why it matters. Members' ideas and requests no longer get lost in comments: the most voted rise, and whoever voted gets an e-mail when the topic changes state.

Where it is. Add Space › Community › Upvote. In a public space, anyone can read the board.

How to start. Create the space and propose the first topic; as you type, the board shows similar topics that already exist.

Example. A Product ideas board, where customers vote on what they want to see and follow what made it into the plan.

Log 1:1 and Community 1:1s

What it is. In the 1:1 space, Log 1:1 keeps the conversation that happened (or will happen) with your direct leader or a direct report, with the topics, notes and agreements, with no need for a recurring series. My 1:1s shows one card per person, with the pair's history. And the Community 1:1s tab lets the owner and the admin read every pair's 1:1s, read only and never anyone's private note.

How to start. In the 1:1 space, click Log 1:1, choose with whom, the date and what you talked about.

Performance Review: nomination, calibration, 9-box and matrix

What it is. The screens that were missing in Performance Review: the Nominations tab (each person nominates their peers, and the direct leader approves, swaps or removes), Calibration (adjusting the final rating with a mandatory comment), 9-box and Matrix (with the CSV). In each person's result, Take to the IDP turns what to develop into an action in the Development Plan. Opening the cycle also warns when someone's direct leader has no access to the space.

Workflows

What it is. Trigger-based automations: when something happens to a person (they join the community, buy, complete a course, go 30 days without signing in), they follow a path you design, with waits, conditions and actions: library e-mails, messages, comments, reactions, tags, groups, Slack posts and While, which repeats a stretch. See Workflows.

Why it matters. The welcome series, the reminder for people who disappeared and the course congratulations go out on their own, each person in their own time. Memberfy helps HR keep everyone engaged: the same workflows remind about a pending review, a 1:1 with no log or a goal with no check-in.

Where it is. Administration › Workflows, with the canvas editor on the computer and a list on mobile.

How to start. Click Templates and pick one of the 9 (six for engagement and three for HR); check it with Simulate with one person and Turn on.

Example. The Welcome series sends three e-mails in the first week of someone who joins; Win-back invites back whoever hasn't signed in for 30 days.

E-mail library and default e-mails

What it is. In Campaigns, an e-mail is now written once, in the E-mails tab, with one version per language, and used in as many Sends and workflows as you like. In the Default e-mails tab, the owner and the admin replace the text of the e-mails the platform sends on behalf of the community: welcome, invitations, import, approved access request, confirmed purchase and event registration. See E-mail campaigns and Default e-mails.

How to start. In Default e-mails, open Sign-up welcome, write your text and use Send test to me.

Ticket types and batches

What it is. An event sells several ticket types (full price, half price, VIP, group), each with batches that turn by date or when they sell out, with the event seats adding them all up. Whoever buys several tickets gives the others away by e-mail in My tickets, refunds can be per ticket, the registration questions can be per type, and the door sees the Proof tag on the types that ask for it. See Events › Ticket types and batches.

How to start. On the event page, Price and sale › New type.

Sending reputation

What it is. Memberfy tracks the unsubscribes and spam complaints of the community's Campaigns and Automations e-mails over the last 7 days. Near the limit, the owner and the admins get an alert; above it, the community's bulk sending is suspended for a while, and password, sign-in and sign-up e-mails keep going out. See Sending reputation.

Improvements

Channel on mobile. A thread opens full screen on tap and next to the conversation when there's room, with the touch gestures of a messaging app; bold accepts **text**.
1:1 meetings always in sight. Canceling a meeting or completing it early no longer leaves the series with fewer than 4 meetings scheduled ahead.
Mark as done, in a 1:1, only shows up from the day of the meeting.
Surveys. Switching the mode of a survey made from a template also switches the introduction written for the other mode, and the message about the round's length limit shows the right number.
The app loads faster, with compressed texts and emojis kept in the browser.
More webhook events. Tags, groups and profile fields, posts, comments and reactions, cart, first visit and space access, lessons and quizzes, tickets, subscriptions, coupons, surveys, forms, call for papers, certificates, Upvote, downloads, classifieds, parcels, visitors, attendance, support and bookings. See Webhooks.
Sales report by ticket type, and the events report with each type's tickets and check-ins.
New security controls.

Fixes

The link to turn off Channel e-mails leads to the right category.
The next event and live stream highlight on the Feed, and the event notice, now open the event. Before, clicking them did nothing.
The plan's member limit notice no longer mentions the Memberfy team.
An event without a date opens normally and accepts registrations.
A purchase canceled by the buyer gives the event seat back.

For developers

API

Channel and Upvote: new routes under /api/channels and /api/upvotes in the API Reference; API keys get the channels and upvotes modules (31 in total). See Authentication.
1:1: logging, changing and deleting a logged 1:1, the history by pair and, for the owner and the admin, GET /api/one-on-ones/pairs?all=1, read only.
Workflows: /api/workflows. E-mail library: /api/emails, and emailId in /api/campaigns. Default e-mails: /api/email-overrides. Ticket types: /api/events/{id}/ticket-types, quantity and registrationAnswers at checkout and ticketIds in the refund. See the API Reference.
Sending reputation: the routes that send answer 409 with data.code: SENDING_SUSPENDED during the suspension.
Webhooks: 62 events in 25 families; member.joined also arrives for people imported from a spreadsheet (source: "import"), and purchase.completed, purchase.refunded and event.registered carry the ticket type. See Webhook events.

MCP: technical details

Channel and Upvote: 29 new tools. See Tools · Content.
1:1: log_one_on_one, update_one_on_one_log, delete_one_on_one_log and list_one_on_one_pairs; get_one_on_one takes person and with_person. See Tools · Members.
Workflows: 23 tools, including the ones for whoever signs messages. See Tools · Community.
E-mail library and default e-mails: 19 tools; create_campaign and update_campaign take email_id. See Tools · Community.
Ticket types and batches: 17 tools; claim_free_product takes quantity, refund_purchase takes ticket_ids and sales_report takes group_by: ticket_type. See Tools · Events.
Sending reputation: the tools that send answer with the suspension's end date and the reason; get_community_context brings the reputation to the team.
The server now has 818 tools.

24 octobre 2026

2026-10-24T23:59:59-03:00

Goals & OKRs
1:1
Performance Review
Recurring survey and heat map
Questions on event registration
Lesson player

Goals & OKRs

What it is. A new space module, in the Planning & HR tab of Add Space, for the community's objectives and key results: the company sets its objectives, each group aligns to them and each person aligns to their group's, in a tree. Key results come in four types, with weight and owner, and progress comes from check-ins, with a status light and a reminder. See Goals & OKRs.

Getting started. The owner or an admin creates the space and the cycle; each owner checks in on their key results in My KRs.

1:1

What it is. A new space module, in the Planning & HR tab, for the recurring series of meetings between a direct leader and each direct report: an agenda for both, notes shared or private, agreements that can go into the Development Plan, a calendar invite and a reminder 24 hours before. HR and the indirect leader only see adherence. See 1:1.

Performance Review

What it is. A new space module, in the Planning & HR tab, for performance reviews in 90°, 180° or 360° cycles: the team builds the cycle, Memberfy assigns who reviews whom from the org chart, each person answers at their own pace, the rating is calculated on closing, the leader sees their team's results and, when the team releases them, each person sees their own. See Performance Review.

Peer nomination, calibration, the 9-box and the matrix already work through the assistant and the API; their screens come to the dashboard next. See Performance Review › Peer nomination, calibration, 9-box and matrix.

Recurring survey and heat map

What it is. A survey can repeat on its own (weekly, every two weeks, monthly or quarterly), one round at a time with the evolution between them, and an identified survey gets the Heat map, by group, tag or company, with the change against the previous round and a CSV. For anonymous surveys, the map is not available yet. See Surveys › Recurring survey and heat map.

Questions on event registration

What it is. An event can ask what the team needs to know about whoever is going (company, job title, T-shirt size, a document), with the Forms fields and the new Document (CPF or passport). On a free event, Going opens the questions with the profile already filled in; the person edits their answers until the start, the team and the organizers see everything in a list with CSV, and the marked answers show at the door. See Events › Registration questions.

Where it is. The Questions button, in the event bar.

Lesson player

What it is. Lessons get Previous lesson and Next lesson at the edges, Complete lesson, automatic completion when the video ends (uploaded video, Drop, YouTube and Vimeo) and resuming where the student stopped ("Continuing from 04:32", with Start over). See Courses › Taking the lesson.

Lesson ratings. Students give 1 to 5 stars, with an optional comment. The team sees the average, the distribution and the comments in the course's Ratings tab; with Show the rating average to students, students see the average too.

Improvements

Monthly AI quotas by plan. Each plan has its own transcription minutes and AI uses per month (Starter 120 minutes and 1,000 uses; Growth 600 and 5,000; Business 2,000 and 20,000; Scale 6,000 and 50,000), counting the whole community, the team included, and the AI usage this month card, in Settings › Plan, shows the usage. See Plan and extensions.
Higher transcription limits. For the AI-written Drop text, a member goes from 10 to 30 transcriptions and from 30 to 120 minutes of audio a day; the owner, admin and moderator no longer have a daily limit. The community has a monthly quota of transcription minutes, high enough not to block anyone. See Drops.
A 100% coupon shows as free in the price quote. Before, checkout could show an amount to pay until confirmation; now an order a coupon brings to zero shows as free from the quote, just as it will be charged.
Events module tabs translated. The Events space filters show in each person's language.
New security controls.

For developers

API

POST /api/ai/drop-description returns 429 when the community's monthly quota is reached; the plan variable ai.transcriptionMinutesPerMonth (default 6,000) joins the catalog.
Goals & OKRs, 1:1, Performance Review and recurring surveys: new routes in the API reference.
Registration questions: GET/PUT /api/events/{id}/registration-questions, GET/PUT /api/events/{id}/my-registration, GET /api/events/{id}/registrations and /registrations/export; the DOCUMENT field type in Forms.
Webhooks: event.registered carries the registration answers in registration. See Webhook events.

MCP: technical details

Ratings through the assistant: rate_lesson and get_course_ratings; courses_report brings averageRating and ratingsCount.
Goals & OKRs, 1:1, Performance Review (with peer nomination, calibration, 9-box and matrix) and recurring surveys: the new tools in Tools · Members.
Registration questions: 6 tools and answers in rsvp_event. See Tools · Events.
The server now has 722 tools.

23 octobre 2026

2026-10-23T23:59:59-03:00

Forms
Drops: AI text and cover
Drops in comments
Signature on brand-artwork certificates
Event check-in
Plan and extensions
Forms on your website
Live updates
Drops in lessons

Forms

What it is. A new space module for collecting structured data: the demo request, the sign-up for a program, the job application. The editor is already the screen the person filling it in sees, with 13 field types (name, e-mail, phone, company, job title, texts, choices, number, date, link and consent), steps, required fields and Lock to profile. See Forms.

Why it matters. What used to go to Google Forms or Typeform stays in the community: each submission reaches the responsibles by e-mail and goes into a list, one by one, with a status (New, In contact, Done), filters, search and CSV. Members find their name, e-mail and phone already filled in. With Save as member, whoever submits gets the invitation to the community with a tag named after the form.

Where it is. Add Space › Community › Forms, as One form or Several forms. In the editor, Settings has the Who fills it in, After sending, Deadline and cap and Notices tabs; Submissions opens the list.

How to start.

Create the Forms space and give the form a title.
Build the fields and, in Settings › Who fills it in, choose Members with access to the space and/or Anyone with the link (with an anti-bot check and required privacy consent).
Publish and Copy link.

Example. A school creates the form "March class waiting list", open to anyone with the link, with Save as member on and the coordinator as the responsible. Each sign-up lands in her inbox, the person gets "We got your submission" and the invitation to the community with the "March class waiting list" tag, and the coordinator marks In contact when she calls them.

Each submission also triggers the form.submitted event for webhooks, HubSpot and RD Station, and a visitor's submission never changes a contact that already exists in your CRM. If you already had HubSpot or RD Station connected, tick the A form was submitted event on the integration screen.

Drops: AI text and cover

What it is. After you record a Drop, AI writes the text from what you said: the post description, the short post text or the comment. And every video gets a cover: the app suggests three frames from the Drop itself, already picks the sharpest, and you can switch or use your own image. See Drops.

Why it matters. Recording was already quick; writing the text around it wasn't. Now the text comes ready to review, in the language you spoke, and the video shows up with a cover that shows what's in it.

Where it is. In a Drops post under New Content, in the Feed's New Status › Drops and in comments: the camera opens right away, counts 3, 2, 1 and, when you stop, the video already uploads in the background. Below the video, Cover; in the text field, "Transcribing your video…" and then Generate again.

How to start.

Record the Drop.
Review the text written by AI (or tap Generate again, up to 5 times per Drop).
Pick the cover and publish.

Example. The organizer records 40 seconds about the event's backstage. Moments later, the field reads "Behind the scenes of the stage setup: the crew arrived at 6 am…"; he changes one word, picks the second frame as the cover and publishes.

To write the text, the Drop's voice is transcribed by an AI provider; the transcript isn't kept after use (24 hours at most). See Terms of use › Personal data.

Drops in comments

What it is. The Allow Drops in comments switch, in Settings › General, lets members reply with a short video recorded on the spot, with the comment text written by AI. It starts off; only the owner and the admin change it. With it off, comments take text only, and Drops already posted keep showing. See General settings.

Signature on brand-artwork certificates

What it is. The certificate template with your brand's artwork now prints the signer's drawn signature, in the new Signature image 1 and Signature image 2 boxes. Before, the signature image only printed on the platform design. See Certificates.

How to start. In the template editor, upload the signature as a PNG with a transparent background, cropped close to the stroke, and draw the box right above the name. The signature keeps its proportion, shrinks if it is too wide and rests on the bottom of the box.

Event check-in

What it is. With Check-in at the door on for the event, every confirmed attendee gets a ticket with a QR and an 8-character code, in My ticket and in the registration email, and attendance is marked at the door. See Events › Check-in.

Why it matters. The list of who came is no longer made by hand, and the event's automatic certificate goes only to those who checked in, with a preview of who gets it.

Where it is. On the event's Check-in button, for the team and the organizers: Scan QR, List (code, search, mark by hand, undo, Export CSV) and Kiosk, a link for a tablet at the door that the owner or admin creates and revokes. Organizers without access to the space reach the door through Events I organize, in the account menu.

How to start.

In the event form, turn on Check-in at the door.
On the day, open Check-in and scan the QR codes, or create the Kiosk link for a tablet.
After the event, check Who gets the certificate to see who checked in.

At an online or hybrid event, opening the stream while signed in, while it is live, counts as attendance.

Plan and extensions

What it is. The Plan tab, in Administration › Settings, shows the community's Memberfy plan (Starter, Growth, Business or Scale), what it includes and the member bar. The Planning & HR and Coworking extensions are plan add-ons; without them, the Add Space tabs show Get the extension. See Plan and extensions.

Why it matters. The member cap only warns, at 90% and 100%, and never blocks anyone. Existing spaces of an extension stay, visible to the owner, admin and moderator.

How to start. Open Settings › Plan and check what is included; to change plans, talk to Memberfy.

Forms on your website

What it is. The Embed button, next to Copy link, gives two snippets to paste into your website's HTML: the Script (recommended), which adjusts its height by itself, and the iframe. The form shows compact, in the community's colors, and works as through the link. See Forms › Embed on your website.

Live updates

What it is. The notifications bell, Online now and Analytics' Realtime tab, the live event banner and campaign numbers update by themselves, right away, without reloading the page, even with the chat off. See Analytics and Messages › Notifications.

Drops in lessons

What it is. A lesson's video can be a Drop recorded on the spot: under Video source, Drops, next to Link and Upload video. The lesson's duration fills in by itself, and Generate lesson text from the video writes the editable Lesson text the student reads below the video. See Courses › Lesson Drop, cover and text.

Where it is. In a Video lesson, when creating or editing. On the lesson page, whoever can edit the course has Edit lesson and Edit course.

Improvements

Memberfy directory. hub.memberfy.net gathers communities by language, with search and categories, and each card opens the community in a new tab. Every community already appears; in Settings › General › Memberfy directory, the owner or an admin turns the listing off and picks the category, the cover and whether to show the member count. See Memberfy directory.
New video player. Every hosted video plays in a player with the bar at the bottom, Speed, Quality (with Auto), captions, picture-in-picture, fullscreen and YouTube's keyboard shortcuts (space or K, J and L, arrows, M, F). See Drops › The player.
"Discard changes?" Before, closing a create or edit window, or leaving a page editor, lost what you had written; now the app asks, with Keep editing and Discard.
The new space opens by itself. Before, only some spaces opened after being created; now every new space opens right away (a single-item space, on the item; a list space, on the list).
Content has a new icon, showing that the space holds text, images, video and Drops.
Faster lists. The Feed, events, chat conversations and spaces load with less waiting.
Last access every 5 minutes. The Last access in the members list is now updated at most every 5 minutes; someone who just signed in may show up a few minutes late. See Manage members.
Job title and bio in member import. The spreadsheet can now carry the profile Job title and Bio: in the Columns step, headers like Job title, Cargo, Função, Bio or Biografia come suggested. New people get both; existing members only get what was empty. Text over the limit (100 characters for the job title, 200 for the bio) is cut, and the row shows the value cut warning. See Import members from a spreadsheet.
Who is online, right away. The chat shows who is online as soon as someone comes in or leaves, without waiting for the next refresh.
Photos in seconds. Gallery and classifieds photos appear a few seconds after the upload. See Classifieds.
Large exports by email. Above 2,000 rows, the subscriptions, engagement and feedback dashboard exports are prepared in the background, and a secure link, which asks you to log in and is valid for 72 hours, arrives by email. See Subscription management.
Content loads as you scroll. The content space brings in posts as you scroll down the page.
Smoother video previews. Going from the cover to the video preview, and back, happens without jumps.
New menus on the Memberfy website. The top of the site gains Solutions, Platform and Resources, each in a floating panel: the pages by type of organization and use case, the modules, AI (MCP) and integrations, the Help Center, Releases, the API reference and the comparisons are one click away. On mobile, the three are grouped in the side menu.
Website home with the platform's numbers. The home page shows how many modules, AI tools and MCP recipes Memberfy has, counted automatically on every update. On mobile, the Request access button now has short text and no longer covers the logo.
New website pages: for Events, Schools and Clubs. Each one shows what Memberfy already offers that type of organization, and all three are in the Solutions menu.
New website page for residential buildings, in the Solutions menu.
Microphone settings in Drops. The recorder's Audio button turns Reduce noise, Cancel echo and Adjust volume automatically on or off, all on by default; the choice is remembered in the browser. See Drops.
Engagement. The Ranking module is now called Engagement; points are engagement points, and the list of the most active members is the leaderboard. Existing spaces don't change. See Engagement space.
Leave the community in Security. The Communities tab of My Account is gone, because each community is a separate account; Leave Community is in Security. See Account and profile.
Community request with a phone. The access request on the website takes an optional phone and a preference for contact by WhatsApp and/or SMS. See Getting your community.
Event time through the API and the assistant. A start time sent with an explicit time zone is now honored; before, it was read in the community's time zone.
Drops up to 10 minutes. Before, 3 minutes. The AI text also works for up to 10 minutes of speech. See Drops.
Choose cover. Every uploaded video (lessons, Video posts and short-post Drops) gets up to six frames to pick the cover from, with the video's duration. See Drops › The cover.
Post video with Drops. In a Video post, Video source has Drops, Link and Upload video. See Content.
New security controls.

For developers

API

Forms: team routes under /api/forms (with the X-CommunityId) and routes for whoever fills it in under /api/public/forms/{token}; see the API Reference.
Webhooks: the form.submitted event (form family), with the form, the origin, the member, the fields and the consent, without the internet address. See Webhook events.
Video cover: the videoPoster purpose and PUT /api/media/{id}/poster; signed links include posterUrl and posterMediaId.
Drop text: /api/ai/drop-description, asynchronous, with kind content, status or comment.
Drops in comments: dropsInComments in the community settings.
Realtime: POST /api/realtime/ticket and the WebSocket /api/realtime/socket (subprotocol memberfy-realtime), with rooms and invalidate notices; /api/chat/ticket and /api/chat/socket stay as aliases for one deploy. See Realtime.
Check-in: routes under /api/events/{id}/check-in, my-ticket and kiosks; webhook events event.checked_in and event.check_in_undone.
Plan: GET /api/entitlements/community and the catalog; a locked module returns 403.
Memberfy directory: public reads at /api/public/hub/communities and the community's options at GET/PUT /api/hub-listing (owner and admin). See Hub.

MCP: technical details

Image measures: the assistant now knows the measures of every image (certificates, covers, banners…) and gets the format right the first time. See Tools · Certificates.
Forms: 17 tools (list_forms, create_form, publish_form with dry_run, list_form_submissions, export_form_submissions_csv, submit_form and the rest) and the Collect with a form recipe (collect_with_form). See Tools · Members.
Drops: set_video_poster, remove_video_poster (with confirmation), create_drop_description and get_drop_description; video_media_id in create_short_post, create_post and create_comment; drops_in_comments in get_community_settings and update_community_settings. See Tools · Content and engagement.
Member import: job_title and tagline as column targets in preview_member_import and start_member_import. See Tools · Members.
Event check-in: 11 tools and the Event door prompt (run_event_door); check_in_enabled in create_event and update_event. See Tools · Events.
Plan and extensions: 11 tools (get_plan_entitlements, list_space_modules and, for the SuperAdmin, values, defaults and exceptions); MODULE_LOCKED on create_space and update_space. See Tools · Community.
Videos and lessons: upload_lesson_drop (admin), set_video_cover_frame, video_media_id on create_lesson and update_lesson and kind: lesson on create_drop_description. See Tools · Courses.
Memberfy directory: get_hub_listing and update_hub_listing (owner and admin, no confirmation) and, for the SuperAdmin, get_community_hub_listing and update_community_hub_listing (reason required to take a community out). See Tools · Community.
The server now has 634 tools and 19 recipes.

22 octobre 2026

2026-10-22T23:59:59-03:00

Messages
Drops
Improve with AI
PDI: company cycle and action linked to a course
Time Tracking: allowed radius
Recognition: by value and card
Feedbacks: export the numbers

Messages

What it is. Real-time chat between community members, in two-person conversations that arrive instantly, without reloading the page. It is on in every community, on every plan, for every role. See Messages.

Why it matters. Conversations between members used to leave the community for WhatsApp. Now they stay in it, with real privacy: only the two people read the conversation. Not the owner, not the admin, not Memberfy support: there is no screen, report or queue with the messages. And it works from day one: everyone starts Available to chat, told so the first time they open the chat, and each person becomes Unavailable whenever they like.

Where it is. In the header, the Chat button, between the notifications bell and your name, with the unread count and a green dot when someone is online. On a computer, it shows the Messages bar in the bottom-right corner, LinkedIn-style: expanded, it has Search conversations, the Conversations and People tabs (who is available, online or offline), the pencil New message and, in the ⋯ menu, your status; each conversation opens in a window beside it, with Minimize and Close. On smaller screens, the button opens a panel with the same tabs: from 600 px, as a sidebar on the right; on a phone, full screen. For the team, the Messages card in Settings, General tab.

How to start.

Open Chat, People tab, and tap someone online (or Send message on their profile card).
Write and send; the person gets it instantly.
If you like, in Settings › General › Messages, choose Who can start a conversation and To chat: Open (default) or Add first.

Add first. In this mode, people add each other before chatting, as in a contacts network: Add, Request sent (with Cancel request), Accept or Decline (without telling the person who asked) on the banner at the top of the chat window (incoming requests also on the bell) and, once connected, writing unlocks; the window's ⋯ menu has View profile, Clear history (for you only), Remove connection and Block. Someone not connected sees only the name, photo, profile tagline and job title; the team always sees the full profile and can be messaged by anyone without a connection, but needs one to start a conversation with a member. The request arrives on the bell, with Accept and Decline on the notification itself, and by e-mail.

Limits against spam. Each person has limits per community: 20 connection requests a day (100 a week, up to 200 waiting for an answer), 10 new conversations an hour (30 a day; existing ones never count), 30 messages a minute and the same text to at most 5 people an hour. Someone who joined less than 24 hours ago has half the request and new-conversation limits, and the team has double. The message says when it frees, in the community's time zone. See Messages › Limits against spam.

Example. In a community with Add first, Ana opens Chat › People, taps Bruno and, on the window's banner, Add. Bruno sees "Ana wants to connect with you" on the bell and taps Accept; Ana gets the notice and the conversation opens. She writes "I'll be at the meeting at 3 pm." Bruno is in another tab; since he hasn't read it in 10 minutes, he gets the email "Ana sent you a message", without the text. Anyone who bothers you can be blocked in Conversation options › Block, and nobody is told.

Drops

What it is. A video note of up to 3 minutes, recorded right there with the phone or computer camera, in a Video post, in a Feed short post and in comments. You record, review and publish, with no other app. See Drops.

Why it matters. A welcome to newcomers, the week's announcement or the answer to a question feel closer on video, and recording no longer means saving and uploading a file. Along with Drops, video streaming (quality adapts to the viewer's connection) is no longer beta and is now on in every community: every video uploaded from now on is prepared for streaming. Videos uploaded before keep playing as a single file and are converted on request, through support. See Content › Hosted video.

Where it is. The Drops button in the short post composer, in the comment box (including on the post page) and, in a Video post, on the line Or record a Drop (up to 3 min).

How to start.

Tap Drops and allow the camera and microphone (the browser only asks now).
Tap Record and, when you're done, Stop; at 3:00 the recording stops on its own.
Review and tap Use this Drop (or Record again). With a Drop, the text is optional.

Example. The coordinator records a 40-second Drop on her phone, upright, welcoming the new class, and publishes it as a Feed short post with no text. The video shows in the shape it was recorded and already plays while it's being optimized for streaming. In the comments, a member replies with another Drop.

Improve with AI

What it is. The Improve with AI icon (the little stars) in the app's long text fields: the AI reviews what you wrote, keeps the language and the formatting, and shows the before and after. On every plan, at no extra cost, for anyone who can write in the field. See Improve with AI.

Why it matters. The text of a post, event or product comes out clearer and error-free, without copying and pasting into another tool. The field only changes if you click Use this text, and Memberfy stores neither the text nor the instruction.

Where it is. At the right end of the rich text editor toolbar, labeled Improve, and in the bottom-right corner of long plain text fields (product, plan, space description, recognition message, short post and others).

How to start.

Write the text and click Improve with AI.
If you like, write an Instruction (optional), such as shorter or more formal, and click Improve.
Compare Before and After and click Use this text, Improve again or Discard.

Example. The organizer writes the event description in a hurry, asks for "more inviting, don't change the dates" and gets the revised version next to the original. She uses the new text, tweaks one sentence and saves the event as usual.

PDI: company cycle and action linked to a course

What it is. The cycle gives the whole company the same deadline to submit and to approve the PDI, with email reminders. And a PDI action can point to a community course: it shows the progress and becomes Done on its own when the person finishes the course. See PDI › The company cycle.

Why it matters. The PDI no longer depends on each leader remembering to nudge the team: there is one calendar, reminders go out on their own, and the leader sees the adhesion of the people below them. And a plan to learn something leads straight to the right course, without the person ticking the action by hand.

Where it is. In the PDI space, Manage PDI cycle › Open cycle at the top, for the owner and the admin; the cycle adhesion, per direct leader, in the Dashboard tab. In each action, the community course field.

How to start.

Click Manage PDI cycle › Open cycle and fill in the name, the deadlines to submit and to approve, the audience and the email reminders (by default, 7 days and 1 day before).
Ask each person to build their PDI and, in study actions, pick the course.
Follow who submitted, who was approved and who is late in the Dashboard.

Example. HR opens the 2027 PDI Cycle with submission by 11/30 and approval by 12/15. Whoever hasn't submitted gets the reminder a week before and the day before; the sales leader sees at the top of the space that 6 of the 8 people on her team have submitted. An action Take the negotiation course shows "3 of 8 lessons (37%)" and becomes Done when the course is finished.

Time Tracking: allowed radius

What it is. An optional virtual fence per time tracking space: the Workplace, the Radius (from 10 to 50,000 meters) and what happens Outside the radius: Block refuses a clock-in outside the radius or without location; Flag records the clock-in with the Outside the radius badge and the distance. See Time Tracking › Allowed radius.

Why it matters. A company that needs clock-ins at the workplace chooses the rule: refuse, or just make it visible in the timesheet and the CSV. Refused attempts are recorded for management without becoming clock-ins, without an NSR and outside the AFD and AEJ. Without a radius, nothing changes: no clock-in is refused.

Where it is. In the Time Tracking space, Establishment, AFD and AEJ tab, for the owner and the admin. The list of clock-ins refused by the radius is there too, and finance sees it as well.

How to start.

Set the Workplace by address search or with Use my location.
Choose the Radius and the mode, Block or Flag.
Check the refused clock-ins: who tried to clock in outside, when and how far away.

Example. A store sets a 200 m radius in Block mode. A salesperson who tries to clock in 350 m away is told they're outside the allowed radius and the clock-in wasn't recorded, and the attempt shows up for management. At the office, with Flag, the clock-in of someone visiting a client goes in with the Outside the radius badge.

Recognition: by value and card

What it is. On the wall, Filter by value shows only the recognitions of one community value (or No value). In the Dashboard, the By value block counts each value's recognitions in the period and the 5 most recognized people in each. And the Card button downloads a PNG image with the community's colors and logo, who gave the recognition, who received it, the value and the message. See Recognition › Filter and count by value.

Why it matters. The team sees which community values really show up day to day (and which nobody remembers), and whoever was recognized takes the praise outside the community, to LinkedIn or a group, without screenshots.

Where it is. In the Recognition space: the filter at the top of the wall, the By value block in the Dashboard (in Manage recognitions) and the Card button on each recognition, for whoever gave it, whoever received it and the team.

How to start.

On the wall, open Filter by value and pick a value; See all goes back to the whole wall.
In the Dashboard, choose the period and look at the By value block.
On one of your recognitions, click Card and share the image.

Example. At quarter close, the director sees in the Dashboard that Customer at the center had 42 recognitions and Simplicity only 3, and takes that to the meeting. Ana, recognized for Customer at the center, downloads the card and posts it on LinkedIn.

Feedbacks: export the numbers

What it is. In the Feedbacks Numbers window, Download CSV and Download Excel take what's on screen, with the chosen period and group: the totals, the adhesion, direct and about-another-person feedback, and the numbers by theme and behavior. See Feedbacks › Export the numbers.

Why it matters. The numbers go into the HR presentation or the board spreadsheet without retyping. And privacy stays the same as on screen: numbers only, never text, author or recipient; counts of 1 or 2 come out as < 3.

Where it is. In the Feedbacks space, the Numbers window, for the owner and the admin.

How to start.

Open Numbers and choose the period and, if you like, a group.
Click Download CSV or Download Excel.
The file comes with labels in your language, ready to open.

Example. Before the board meeting, HR picks the last quarter and the Product group, clicks Download Excel and pastes the team's adhesion and answered requests into the presentation, without exposing what anyone wrote.

Improvements

Video streaming in every community. Before, only beta communities had streaming; now every uploaded video is prepared for streaming, up to 720p for Drops. See Content.
Chat emails. A new category, Messages, in E-mails from this community, on by default, with an unsubscribe for just that category in the footer: the unread-message notice, which never carries the text, and the connection-request notice (at most one per pair of people every 24 hours). Someone unavailable gets neither.
PDI cycle reminders go out in the PDI category of E-mails from this community, at most one per day per person.
New security controls.
Messages closer at hand. When a conversation opens, the cursor is already in the message box. On a computer, minimized conversations become tabs with photo, name and unread count (those that don't fit go into +N), and a new message opens its conversation by itself, except while you are Unavailable. A short sound plays on send and on receive (Sounds, in the ⋯ menu, on by default), and the status, Read receipts, Sounds and Blocked people all live in that menu. See Messages.
The team stands out in the chat. In People, the Team comes before the Members, and team members have a ring in the community color and their role chip in the lists and tabs. With Add first, anyone can now talk to the team without a connection (the team replies, but still needs a connection to start with a member). Each contact's unread messages show in a bubble on the right. See Messages.
API keys for members, only if the owner allows it. In Settings › Integrations & APIs, the Members can create API keys option comes off in every community: members don't see their keys and existing ones stop, without being deleted, until the owner turns it on. Your keys now live in My Account › API keys, and no key reaches Messages, notifications, Feedback, development plans, Recognition, Time Tracking or Improve with AI. See Integrations & APIs.
Drops as a content type. In Content, New Content gained the shortcuts Text, Drops, Image and Video in its arrow (then New poll and Import content), and Drops became a type of its own: "Record a short video with your camera, up to 3 minutes". See Drops.

Fixes

Commenting on the post page works again. Before, the Comment button on a post's page didn't publish the comment; now it does, with text or a Drop. See Content.
Editing a short post from the card menu. Before, Edit in the short post card menu didn't open the editor; now it opens with the text ready to change. See Feed.
Editing a post comment keeps the new text. Before, after saving the edit, the comment still showed the old text; now it shows what you wrote.

For developers

API

Messages: routes under /api/chat (preferences, members for the People panel, online, conversations, messages, blocks, connections and community settings, with startMode FREE or CONNECTION) and /api/notifications (list, unread-count, mark as read, read-all, delete), with the X-CommunityId. Someone else's conversation answers 404 for every role; with the chat off, 403; with CONNECTION, a conversation or message without an accepted connection, 403. GET /api/members/{id} returns chatAvailable and, without a connection, limited: true. See Messages › In the API. Anti-spam limits: 429 with errors[0].code, limit, retryAt and Retry-After (see Responses and errors › Chat limits).
Drops: POST /api/media/upload-url with the purpose statusVideo, contentCommentVideo or statusCommentVideo (up to 100 MB), the upload and POST /api/media/confirm; the videoMediaId goes in POST/PUT /api/status and in creating and editing post and short post comments. videoMediaId: null removes it. Only whoever recorded the video can attach it. See Drops › In the API.
Improve with AI: POST /api/ai/improve-text with text (up to 20,000), fieldKind, format (html, markdown or plain) and optional instruction (up to 500); 400, 429 with Retry-After, and 503. See Improve with AI › In the API.
Recognition: valueId (id or none) in GET /api/recognitions, byValue in /dashboard, GET /api/recognitions/{id}/card (PNG; 403 cardDenied) and canDownloadCard on each recognition.
PDI: cycles under /api/development-plans/cycles (current, list, create, edit, close and adhesion; 409 cycleOpenExists for a second open cycle) and courseId on actions, with course and the progress.
Feedbacks: GET /api/feedbacks/dashboard/export?format=csv|xlsx, owner and admin only.
Time Tracking: PUT and DELETE /api/time-tracking/spaces/{spaceId}/geofence, GET /api/time-tracking/geofence-refusals; in BLOCK mode, POST /punches outside the radius returns 422 (geofenceOutside, geofenceNoLocation), and punches include outsideRadius.

MCP: technical details

Messages: 25 tools, only over the connected person's own conversations, connections and notifications: get_my_chat_preferences, update_my_chat_preferences (with availability_notice_seen), list_chat_members, list_chat_online_members, list_chat_conversations, get_chat_conversation, send_chat_message and delete_chat_message (with confirmation), mark_chat_conversation_read, clear_chat_history (with confirmation), list_chat_blocks, block_chat_member, unblock_chat_member, list_chat_connections, list_chat_connection_requests, request_chat_connection, accept_chat_connection, decline_chat_connection, remove_chat_connection (with confirmation), list_notifications, get_notification, mark_notifications_read, delete_notification (with confirmation), and get_chat_settings/update_chat_settings (with start_mode) for the owner and the admin. The text never goes into the assistant's log. New recipe: See who asked to connect and accept. See Tools · Members › Messages.
Drops: the assistant doesn't record, but create_short_post, update_post (type: status), create_comment and update_comment accept video_file_url or video_file_base64 (MP4, WebM or MOV, up to 100 MB); remove_post_video and remove_comment_video ask for confirmation. See Tools · Content.
Improve with AI: no tool; the assistant already rewrites the text in the conversation.
Recognition: list_recognitions with value, the by-value block in get_recognition_dashboard, and get_recognition_card.
PDI: get_current_development_cycle, list_development_cycles, get_development_cycle, create_development_cycle (with dry_run), update_development_cycle, close_development_cycle (with confirmation), get_development_cycle_adhesion and course_id on actions. See the recipe Open the PDI cycle and follow the adhesion.
Feedbacks: get_feedback_dashboard with format: "csv". See the recipe Download the feedback numbers as CSV.

21 octobre 2026

2026-10-21T23:59:59-03:00

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.

Create the Surveys space and choose who has access: they are the ones who will answer.
Click New survey, pick a template (NPS, satisfaction, event, course, eNPS or blank) and adjust the questions right on the screen.
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.

Create the space and, if you want, set up the community values.
Share the space: anyone with access clicks Recognize, picks the colleagues and writes the message.
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.

Create the space and choose who has access: they are the ones who can give and receive feedback.
Click Give feedback (or Ask for feedback), pick the person and write.
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.

Publish as usual: the box comes checked and shows how many people will get it.
For a fix or a test, uncheck the box: nobody gets an e-mail for that post.
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.

Create the space; the establishment step comes filled in with the company's CNPJ and legal name.
In Employees, register each person with CPF, hire date and job title.
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.

20 octobre 2026

2026-10-20T23:59:59-03:00

Parcels for companies

Parcels for companies

What it is. In the Parcels space, the recipient can be a company, not just a person. The parcel belongs to the company, and any of its current employees with access to the space sees it and picks it up.

Why it matters. Before, the front desk had to pick one employee for a package addressed to the company, and only that person was notified. Now the package belongs to the company: every employee with access gets the e-mail (or only the company's admins, if it prefers), and whoever is at the office picks it up. Someone who leaves the company stops seeing its parcels right away.

Where it is. In the Parcels space, Receive a parcel › Recipient: companies show up with the Company badge. The Queue gets the All companies filter. The Notify only the company's admins about parcels option is in the company record, under Administration › Members, Companies tab (owner and admin).

How to start.

Tap Receive a parcel and type the start of the company's name.
Pick the company (the one with the Company badge) and save.
If only the company's admins should be notified, turn the option on in its record.

Example. A package from Staples arrives for Acme. The front desk registers it for Acme; the employees see the card "For Acme" in My parcels, with the place and the code, and the first one to stop by taps I picked it up. If the company is closed, the parcel stays stored, with the Company closed badge, with no e-mail notice or reminder. Through the assistant, just say "a package arrived for Acme" (recipe 77).

Improvements

The member's phone goes along in webhooks and integrations. Before, events carried only the person's name and e-mail. Now they also carry the phone, when the person added one: HubSpot saves the phone on the contact and RD Station on the lead's mobile phone. See Webhooks.

For developers

API

Parcel for a company: GET /api/parcels/spaces/{spaceId}/members also returns companies, with type (member or company) on each item. Registering accepts recipientCompanyId instead of recipientMemberId. The parcel gains recipientType and recipientCompany (id, name, status, removed); on a company's parcel, recipient and recipientMemberId come as null. The queue filters by recipientCompanyId and q finds by the company's name. POST and PATCH /api/companies accept parcelNoticeAdminsOnly. See Parcels › In the API.
Phone in the payload: the member block of every webhook event becomes { id, name, email, phone, phoneCountry }. phone comes in E.164 (+5541999998888) or null; phoneCountry in ISO 3166-1 alpha-2 (BR) or null. It applies to every destination. See Webhook events.

MCP: technical details

search_parcel_recipients returns type; register_parcel accepts recipient_company_id (and recipient_member_id becomes optional: one of the two); list_pending_parcels and list_parcels filter by recipient_company_id.
The current employee sees the company's parcel in do_i_have_parcels and get_parcel, with the code, and picks it up with mark_parcel_picked_up (SELF).
create_company and update_company accept parcel_notice_admins_only, with no confirmation. See Tools · Parcels.

19 octobre 2026

2026-10-19T23:59:59-03:00

Integrating the community with another system no longer requires an account just for that: each person creates their own key, checks what it may do and revokes it whenever they want. And, the other way around, the community now notifies your systems on its own.

Personal API keys, with per-module permissions
Webhooks in Integrations & APIs
Ready-made integrations: Discord, Slack, Telegram, RD Station, HubSpot and shortcuts to Zapier, Make and n8n

Personal API keys, with per-module permissions

What it is. A key that a CRM, an automation (n8n, Zapier, Make) or a script uses to call the community's API on your behalf, without signing in. When you create it, you check, module by module, what it may do: read, create and edit and delete and destructive actions. With nothing checked, the key does nothing, and it never goes beyond what your role allows.

Why it matters. Before, an integration needed a member just for it, with the email and password stored in the outside system, and with all the power of that member's role. Now the key does only what you unlocked, can have an expiration and a list of IPs, and stops working the moment it is revoked. Money (refunds, payouts, checkout, cards), the account (password, sign-in, email, phone) and managing the keys themselves are out of reach of any key.

Where it is. Owner and admin: Settings, Integrations & APIs tab. Other roles: Integrations & APIs, in the account menu, below Billing.

How to start.

Click New key, give it a name and check only the modules and columns the integration needs.
If you want, add an expiration and the IPs of the server that will call.
Copy the key right away: it is shown only once.

Example. Rafael, an admin, creates the CRM key with read on Members and on Sales and subscriptions, locked to the CRM server's IP. The CRM starts pulling new subscribers on its own. Owner and admin see all of the community's keys in All in the community, can revoke any of them and follow the month's calls in the Usage block. See Integrations & APIs.

The 28 modules and the three columns: read, create and edit, delete and destructive actions.

Webhooks in Integrations & APIs

What it is. Notify your CRM, Zapier, Make or n8n when someone joins, buys, subscribes, registers for an event or completes a course. You register the destination URL, pick the events (13, in 6 families) and Memberfy sends a signed notice the moment it happens.

Why it matters. Before, to learn about a purchase or a new member, the outside system had to ask the API every so often. Now the notice arrives on its own, with the person's name and email, and the spreadsheet, the CRM or the team's group update in seconds. If the destination goes down, Memberfy keeps trying for almost two days and, if it doesn't come back, disables the webhook and sends an email.

Where it is. Settings, Integrations & APIs tab, Webhooks tab. Owner and admin.

How to start.

Click New webhook, paste the URL Zapier, Make or n8n gave you and check the events (the whole family or one by one).
Copy the secret: it's shown only once, and it's how the destination checks that the notice came from Memberfy.
Click Send test and see the destination's answer.

Example. Julia, the owner, connects the Purchases family to a Zapier trigger. Each completed purchase becomes a message in the team's channel. In the webhook's Deliveries section she sees each send, with the destination's answer, and resends what failed. If the destination's firewall only accepts known addresses, the Send from fixed IPs option makes deliveries come from two Memberfy IPs. See Integrations & APIs › Webhooks.

The destination URL, the events by family and the personal data notice.

Also new: the Usage block now counts the webhooks delivered each month, and the Administration › Logs page gets the API keys type, with everything the keys did. See Logs › API keys.

Ready-made integrations

What it is. Ready-made integrations: Discord, Slack, Telegram, RD Station, HubSpot and shortcuts to Zapier, Make and n8n. You pick the app, paste its credential, check the events and turn it on. No automation in between and no code.

Why it matters. Before, telling the team on Slack about each purchase, or taking new members to the CRM, took a webhook and a hand-built automation. Now the message reaches the channel ("Maria bought Career Mentoring.", with only the first name, in the community's language), the lead shows up in RD Station with the conversion, and the HubSpot contact gets the deal for the purchase and the renewal, without duplicates.

Where it is. Settings, Integrations & APIs tab, Integrations tab. Owner and admin.

How to start.

Click the app's card and follow the "How to connect …" guide to create the URL, token or key at the provider.
Paste it, check the events and confirm what the app will receive.
Click Turn on and then Send test.

Example. Júlia turns Telegram on: she creates the bot in BotFather, adds it to the team's group and uses Find my group. With each event registration, the group gets "Maria registered for October Meetup.". Disable pauses and keeps the settings; Remove integration deletes the credential and the delivery history. If the provider fails for 72 hours, the app is turned off and the owner and admins get an e-mail. See Ready-made integrations.

One card per app, with what it receives and its state.

Improvements

Edit webhooks. Before, changing a webhook's URL, events or fixed IPs meant creating another and deleting the old one. Now the detail has Edit, without changing the secret: deliveries already under way keep going to the old destination, changing the URL resets the failures and editing does not turn it back on. See Edit a webhook.
New security controls.
Website: the Platform page on memberfy.net gets an Integrations & APIs section, which shows the ready-made integrations as available, and the home page and the For Communities, For HR and For Coworkings pages now mention it with examples.

For developers

API

API key (X-Api-Key) instead of the token, always with the X-CommunityId of the key's community; with Authorization as well, 400. The key acts as its owner and the effective permission is the scope (<module>:<level>, 28 modules, read/write/delete) and, at the same time, the owner's current role. On a public route, a key without the scope proceeds as anonymous. See Authentication › API key.
Limit of 120 calls per minute per person in each community, adding up their keys, with 429 and Retry-After. Allowed IPs per key (up to 20, IPv4, IPv6 or CIDR).
Errors with a stable code: API_KEY_SCOPE_MISSING, API_KEY_BLOCKED, API_KEY_ROUTE_NOT_COVERED, API_KEY_IP_NOT_ALLOWED, API_KEY_RATE_LIMITED, API_KEY_WITH_AUTHORIZATION and API_KEY_PATH_INVALID. See Responses and errors.
/api/integrations/api-keys routes (list, create, view, rename and change IPs, revoke, usage) and /api/integrations/usage, with the sign-in token only. See API reference › Integrations.
The specification gets the apiKey scheme, and each operation states the scope the key needs or that it doesn't accept a key; the reference shows this next to API key.
GET /api/activity-logs gets the apiKeys source: key created, renamed, with IPs changed, revoked, and every write made with a key ("via key {name}").
Webhooks (Standard Webhooks): the envelope (id, type, version, occurredAt, community, data), the 13 events and the ping, the webhook-id/webhook-timestamp/webhook-signature signature with a Node example (standardwebhooks), deduplication by webhook-id and no guaranteed order. 8 attempts (1 min, 5 min, 30 min, 2 h, 6 h, 12 h, 24 h, about 45 h); 410 disables right away; 72 h without success disables, with an email to owner and admins; 429 honors Retry-After and doesn't count as a failure. https on port 443 only, no redirects, 10 s. See Webhooks.
Webhook events: the reference generated from the public catalog GET /api/integrations/events, with each event's JSON Schema.
Fixed IPs: 3.227.95.35 and 34.199.138.158, to allow in the firewall.
Management at https://developers.memberfy.net/api/webhooks (sign-in token of an owner or admin, never an API key). Creating, sending a test, turning back on, resending and changing the URL share a limit of 10 per minute per community; up to 10 webhooks per community.
Edit webhook: PATCH /api/webhooks/{id} (url, description, events, fixedIps, only what changes). Applies to later events; deliveries under way keep their destination; changing the URL resets failureCount; does not turn it back on; updated history line with before and after. See Webhooks › Edit a webhook.
Ready-made integrations: /api/apps at https://developers.memberfy.net (catalog, installation PUT/DELETE, with ?remove=true to remove, test, POST /api/apps/telegram/chats, deliveries and resend), with the same owner or admin token. See Webhooks › Ready-made integrations.
GET /api/logs accepts type=apiKeys, with actor.via = api_key on calls made with a key.

MCP: technical details

list_integrations (new, read-only, any role): scope: mine (default) lists your keys; scope: community (owner and admin) lists everyone's, with member_id and status. Scopes come with the screen's names; the secret never does. No creating, editing or revoking keys through the assistant. See Tools · Community.
list_activity_logs accepts source: apiKeys, and the community list in list_integrations suggests that query in next_steps.
New recipes: Which API keys do I have?, Which community keys are active? and What did the n8n key do?. The server now has 445 tools.
list_integrations also shows the webhooks to owner and admin (type: webhooks, or no type): status, failures in a row, the last delivery and, when it's failing, the latest failed deliveries. Read-only: creating, testing, resending and deleting a webhook is on screen only; the full URL and the secret never come back.
list_logs accepts type: apiKeys.
list_integrations with type: apps (or without type), for owner and admin: each app ever turned on, with state, events, failures in a row, last successful delivery and the latest failed deliveries; the settings never come back. No turning on, testing or disabling apps through the assistant. New recipe: Is any app or webhook failing?.

18 octobre 2026

2026-10-18T23:59:59-03:00

Whoever works at one of the community's companies now knows, without asking the front desk, what the company pays for them. And the companies record no longer talks about "residents": it works for a coworking space, an association, a customer community or any other.

Employees see what they get through the company

What it is. People on a company's team see what they get through the company: plans, content and credits. The What you get through your company card shows up for every employee, not only the company admin, with the company's active plans and products, the spaces and content each one unlocks and the company credits the person can use, with a notice when a batch is about to expire. No prices and no billing: those stay with the company admin.

Why it matters. Before, employees only saw the team and did not know what was included. Now they know the meeting room is paid with company credits and the course is already unlocked, without asking the front desk and without subscribing again to what the company already pays for.

Where it is. In My company › Team, in the account menu. On the Billing page, people with access through a company see the Through your company {name} card at the top, with the company's plans and the See my company link.

How to start.

Register the company and its offers in Administration › Members, Companies tab.
The company admin buys a plan in My company › Purchase.
Each employee opens My company and sees what they have.

Example. Acme subscribes to the Private office monthly plan, which unlocks the wall and the meeting rooms and gives 20 credits a month. João, an Acme employee, opens My company and sees the plan, both spaces and the company's 20 credits, 5 of them expiring at the end of the month. See Companies.

What's new

A lifetime 100% coupon now unlocks plans, for companies too. A 100% coupon with a forever duration closes a plan purchase with no payment, through Get it free, and renewals charge nothing while the coupon covers them. It works for a person and for a company: the company admin buys through the company checkout with the coupon, and the confirmation says "Purchased for {company}". With a once or repeating duration, checkout refuses the plan and asks for a card. A one-off product with 100% works as before. See 100% coupon.
Abandoned carts in Sales, with an optional recovery e-mail. In Monetization › Sales, the Sales | Abandoned switch shows who opened the checkout of a paid product and did not buy within an hour (PIX and boleto wait for their own deadline), with the contact, the product, the amount and the chosen payment method; whoever pays within 7 days shows as Recovered, with the amount. The owner and admin can turn on Send recovery e-mail (it comes off): one e-mail per cart, with the Resume purchase button, never sent to whoever unsubscribed or already got the failure notice for that order. Carts are deleted 90 days after the abandonment. See Abandoned carts.

Improvements

Companies stop being "resident companies": the record works for any community. A company is just a name and a team, with a company admin; coworking became an optional block, turned on with the Coworking switch ("Company in the coworking space: type, offers, billing and dates."). Nothing changes in what is already registered. See Companies.
Subscriptions show since when they are past due. In Members › Subscriptions, a past-due subscription shows Past due since, and the timeline records each time it goes into and out of past due with the reason (no card, expired card, declined card, retries exhausted or reported by the processor) and Payment settled when it comes back. Subscribers see the same in Billing, in the Late payment history. See Past due.
Abandoned cart data is now in the terms of use. The Personal data section says what is kept, what for, on what legal basis and for how long. See Terms of use.

Fixes

The unpaid renewal notice is also sent when the processor reports the past due. Before, when it was the payment processor that marked the subscription as past due, the subscriber did not get the "We could not renew …" e-mail.
A canceled or expired subscription no longer goes back to "past due". Before, a late notice from the processor or the automatic charge could mark as past due a subscription that had already ended.
The "On this page" index in articles shows apostrophes, quotes and "&" correctly. Before, section titles with these characters showed codes such as ' in the index instead of the apostrophe.
The reply counter and "Edit" on comments show in your language. Before, a comment's reply count and the Edit menu item stayed in Portuguese in every language.
Account details say they apply to this community. Before, the member edit dialog labeled name, e-mail and phone as (Global) and My Account said the information was shared across all communities; since each community has its own account, that was no longer true. See Account and profile.

For developers

API

POST /api/checkout and POST /api/checkout/calculate-price: a coupon that brings a plan (FOREVER only, no add-ons or trial period) or a one-off product to zero takes the free-purchase path and answers with free: true; with companyId, for the company too, and the response echoes companyId. On a plan, a 100% ONCE or REPEATING coupon answers 400 on couponCode. See API reference › Checkout.
The company routes move from /api/resident-companies/* to /api/companies/*, and the reference tag becomes Companies. The old paths no longer respond. See API reference › Companies.
GET /api/companies/mine gains benefits for anyone on the team of an active company: items (active plans and products, with spaces and contents) and credits (balance, expiringSoon), with no prices; null once the company is closed.
GET /api/auth/me gains viaCompany (companyId, name, plans) or null.
GET /api/abandoned-carts (owner, admin and finance): the ABANDONED and RECOVERED carts, with contact, product, plan, amount, abandonedAt, recoveredAt, recoveredAmount and emailSent; filters productId, planId, status, from, to and search. POST /api/checkout/carts records the cart when the purchase panel opens. See API reference › Sales.
GET and PUT /api/notification-settings gain abandonedCartEmailEnabled. Heads-up: the PUT now keeps an omitted field; before, omitting salesNotificationEmail cleared the notice e-mail.
GET /api/manage/subscriptions, GET /api/manage/subscriptions/{subscriptionId} and GET /api/subscriptions/{id} gain pastDueSince; the details carry in events the types PAST_DUE, RECOVERED and EXPIRED, with reason (no_card, card_expired, card_declined, retries_exhausted, provider, paid, staff).

MCP: technical details

The 11 *_resident_company* tools are now called list_companies, get_company, get_my_company, create_company, update_company, close_company, list_company_members, invite_company_member, update_company_member, remove_company_member and list_company_invitations. Arguments, roles and confirmation do not change. The old names answer as an unknown tool.
The catalog group is now called Companies (companies).
get_my_company returns benefits and answers "what do I get through my company?". See Tools · Companies and the recipe What I get through my company.
list_abandoned_carts (new, read-only, owner, admin and finance): the abandoned and recovered carts, with the screen's filters; suggests turning on the recovery e-mail when there are abandoned carts without one. See Tools · Finance.
get_my_subscription (new, read-only, any role): one of your subscriptions with pastDueSince and the past-due history; when past due, suggests pay_my_subscription_now. get_subscription and list_subscriptions bring pastDueSince and the past-due events.
update_notification_settings gains abandoned_cart_email_enabled, without confirmation; both fields become optional and only the one given changes. The server now has 444 tools.

17 octobre 2026

2026-10-17T23:59:59-03:00

The resident company becomes a subscriber, billed to its CNPJ and with access for the whole team. Also: adjustments to member management and a large API review, which now calls a member what it used to call a profile.

What it is. Resident companies now subscribe to plans and pay with a CNPJ, with access for the whole team and a credit wallet. The subscription, the purchase, the card and the billing are in the company's name, not in the name of whoever clicked buy.

Why it matters. Before, each employee needed their own subscription, or the company stayed outside billing. Now the startup in room 3 pays for a single plan, billed to its CNPJ, and its five employees get the plan's access. The plan's credits go to the company, and any employee books the meeting room with them.

Where it is. For the team, in Administration › Members, Companies tab: the Coworking block picks the plans and products the company can buy and stores the billing details, and the company detail shows Copy purchase link, the subscriptions, the purchases and the Company credits. For the company admin, in My company, with the Purchase, Billing and Credits tabs.

How to start.

Edit the company, turn on Coworking and choose what it can buy under Plans and products.
On the detail, click Copy purchase link and send it to the company admin.
They open the link, buy in My company › Purchase with the company's CNPJ and follow everything in Billing.

Example. Acme Tecnologia subscribes to the Private office monthly plan, with 20 credits a month. The partner, the company admin, pays with Acme's CNPJ; the billing e-mails go to Acme's finance team and to her. João, an employee, books Room 2 picking Company balance under Pay with, and the company statement shows Used by João.

What else comes with it:

Access for the team: the company's plan covers everyone with a live link to the team. A closed company, or one whose planned exit has passed, gives no access and is not billed.
Billing: Pay now, plan changes, add-ons and cancellation, as on a member's billing page. Company purchases have no trial period.
E-mails: billing e-mails go to the billing e-mail and to the company admins; the sales notice shows the company and Bought by.
Bookings and Scheduling: the employee picks Company balance or My balance; a time the company covers shows free, with the company icon; the booking shows who paid, and the refund goes back to whoever paid.
Sales and subscriptions: the search also finds the company by name.

See Resident companies, Credits and Bookings.

Improvements

Adding someone who already belongs to another community through member management now works right away. They get the link to create this community's password: the account belongs to each community, and the other community's password does not open this one. See Invite members.
People pickers say "members". In the people search (to pick assignees, hosts, recipients), the field now says Search members... and, with no results, No members found, instead of "profiles".
New security controls.

Fixes

The new card used in Pay now becomes the default card. Before, whoever paid an overdue renewal with another card kept the old card for the next renewals. See Pay now.

For developers

API

GET /api/ledger with an entryType that does not exist now answers 400, with param: "entryType", instead of an internal error. The accepted types are in the reference.
GET /api/status signed out now carries canEdit, canDelete and canModerate as false, in the same shape as for a signed-in viewer.
Profile becomes member across the API. The /api/profiles/* routes are now /api/members/*: the list is GET /api/members, creating is POST /api/members, inviting is POST /api/members/invite, the member card is /api/members/{id} (with /email, /phone, /tags, /role, /fields), tags live in /api/members/tags, and your own things live in /api/members/me (edit), /api/members/me/communities, /api/members/me/downloads, /api/members/me/email-preferences and /api/members/me/decline. Also changed: /api/hierarchy/members/{id}, /api/credits/members/{memberId} and the picture, POST and DELETE /api/upload/avatar/member, with an optional memberId for the team to change someone else's. The old routes no longer exist. See Manage members and Account and profile.
memberId instead of profileId in every request and response (and *MemberId instead of *ProfileId); the X-ProfileId header becomes X-MemberId, and the SDK swaps setProfile for setMember. See Authentication and JavaScript SDK.
The session is the member. Sign-in, sign-up and GET /api/auth/me return this community's member, flat, with id equal to the memberId; profiles[] is gone. See Authentication.
Undoing is DELETE. Taking back a reaction (on a post, status, comment, course, lesson or gallery image) is DELETE on the same path as the reaction; POST only adds or changes. Removing an event recording is DELETE /api/events/{id}/recording. See Responses and errors.
Translated authentication errors. Sign-in and role 401 and 403 come in the standard envelope, with errors[], in the language of Accept-Language (English without a recognized language). A member from another community answers 404, the same as an id that doesn't exist. See Responses and errors.
Resident company as subscriber. POST /api/checkout and POST /api/checkout/calculate-price accept companyId (buying on behalf of the company: its admin only, CNPJ required, no free trial). GET /api/subscriptions, GET /api/purchases/me and GET /api/manage/purchases accept ?companyId=; the /api/subscriptions/{id}/… routes treat the company admin as the subscriber. GET /api/dashboard/customers also lists paying companies, with type (member or company). See Resident companies.
Company credits. GET /api/credits/companies/{companyId} and /entries (with usedBy); POST /api/credits/grants and /adjustments accept companyId instead of memberId; GET /api/credits/me carries company. Bookings: payWith (own or company) on POST /api/bookings and on rescheduling, creditPayer on every booking, and affordableWith and companyWallet in search, availability and Scheduling. See Credits.
Breaking change in /api/resident-companies: the route no longer accepts or returns planProductId, productId, monthlyValue, plan and product. Use offerProductIds (write), offers (read) and billing { legalName, taxId, email }; the answer carries purchaseLink.

MCP: technical details

Resident company: create_resident_company and update_resident_company swap plan_product_id and product_id for offer_product_ids and billing and return purchaseLink. get_resident_company brings subscriptions and credit_balance; get_my_resident_company, for the company admin, brings billing, subscriptions, purchases and credit_balance. See Tools · Resident companies.
Billing by the company admin: list_my_subscriptions and list_my_purchases accept company_id; manage_my_subscription, quote_plan_change and change_my_plan work on the company's subscription. New: quote_my_add_on, add_my_add_on and pay_my_subscription_now, which ask for confirmation and only take PIX or boleto (card, only in the app). See Tools · Subscriptions.
Credits and bookings: new get_company_credit_balance and list_company_credit_entries; grant_credits, adjust_credits and revoke_credits accept company_id; create_booking, create_booking_for_member and reschedule_booking accept pay_with. There are 442 tools. See Tools · Credits.
update_member_profile is now update_member, and update_my_profile is update_me (only name, tagline, language, phone and phone_country). The *_profile_id arguments become *_member_id. update_avatar no longer has scope. add_reaction, react_to_comment and react_to_gallery_image accept remove: true to take a reaction back, and reacting to gallery images through the assistant works again, now also with 🎉. See Tools › Members.

16 octobre 2026

2026-10-16T23:59:59-03:00

Today the coworking got two operations tools: the record of the companies that occupy the space, and the inspection round that turns each problem into a ticket.

Resident companies
Inspection rounds

Resident companies

What it is. The record of the community's companies, each with its team. In a coworking, the Coworking block stores the residence type, the company's plan and product, and the dates. One person on the team can be the company admin and look after colleagues without depending on the front desk.

Why it matters. The front desk no longer keeps the list of who works for each company in a spreadsheet. The company adds and removes its own staff, and the community team sees everything in one place. Plan and product are a reference, not charged: billing is still the subscription the company buys.

Where it is. Administration › Members, Companies tab, for the community team, and My company, in the account menu, for people on a company's team.

How to start.

In Administration › Members, click New company and fill in the name. In a coworking, turn on Coworking and choose the residence type, the plan and/or the product, and the start.
Open the company, click Invite and tick Company admin for the person who will look after it.
The company admin invites colleagues by e-mail from My company; each one joins the team on accepting the invitation.

Example. Acme Tecnologia occupies room 3. The admin registers the company as a Private office and invites the partner as company admin. She invites the four employees, who accept through the e-mail. When Acme moves out, the admin clicks Close and decides, in the same step, whether the team leaves too.

Finance sees the Coworking block without editing; the moderator sees only the name, badge and team. See Resident companies.

Inspection rounds

What it is. The walk the team takes around the building to check everything is in order, done from a phone, in the Support space. Each spot is marked Ok or Problem, and each problem instantly becomes a maintenance ticket in the queue.

Why it matters. Nothing gets lost between the round's notes and the repair: the problem enters the queue with the description and the photo, and the room's screen in Bookings keeps the history of rounds and tickets for each item.

Where it is. In the Support space, Rounds tab (team only). The history of each room, desk or piece of equipment is in the History tab of the item's screen in Bookings.

How to start.

In the Rounds tab, create a New sector (a floor, for example) and add the spots: rooms from Bookings or free places, such as Kitchen.
Tap Start round, mark each spot and, on a problem, describe it and take a photo.
Tap Complete round. Anything left unmarked shows as Pending in the history.

Example. At 7:40 am, the front desk walks the 2nd floor: both rooms are ok, but the kitchen light is out. One tap on Problem, one sentence, one photo, and the caretaker gets the new-ticket e-mail.

The owner and the admin set up the sectors; the owner, the admin and the moderator walk the rounds; finance follows along. See Inspection rounds and Bookings.

Improvements

Cards, lists, the side menu, notifications, search and the "Back" buttons became real links. Cmd/Ctrl+click, the middle mouse button and "Open link in new tab" now work, and a normal click still opens right away, without reloading the page.
Companies now live in Members, work for any community and, in a coworking, store the company's plan and product. See Resident companies.
Profiles no longer have the Person/Company type. Companies are now registered in Members › Companies. See Resident companies.
Billing for anyone removed from the community is suspended. The subscription stays on record until it is canceled.
Profile name and photo now apply per community. Changing your name or photo in one community no longer changes it in the others you belong to.
Someone who already belongs to another community creates the new community's password through the invite link. Invites, spreadsheet imports and approved community requests always send the email with Set my password (valid for 7 days): accounts are per community. An invitee without a name starts with the part of the email before the @. See Invite members.
New security controls.

Fixes

The limit message when uploading several media files at once showed a placeholder instead of the number; it now shows the right limit.
The invitation e-mail when adding a member from member management is sent again.

For developers

API

Resident Companies tag: GET and POST /api/resident-companies, GET /api/resident-companies/mine, GET and PATCH /api/resident-companies/{id}, POST /api/resident-companies/{id}/close, GET and POST /api/resident-companies/{id}/members, PATCH and DELETE /api/resident-companies/{id}/members/{profileId}, GET /api/resident-companies/{id}/invitations, GET /api/resident-companies/invitations/mine and POST /api/resident-companies/invitations/{invitationId}/accept and /decline. See Resident Companies.
Rounds in Support: GET and POST /api/support/sectors, PATCH and DELETE /api/support/sectors/{sectorId}, POST /api/support/sectors/{sectorId}/spots, PATCH and DELETE /api/support/spots/{spotId}, GET and POST /api/support/rounds, GET /api/support/rounds/{roundId}, POST /api/support/rounds/{roundId}/items and /complete, and the resource history at GET /api/support/resources/{resourceId}/history. See Support.
POST /api/auth/support-entry trades the link from Memberfy support's Enter for an owner session, valid only in that community. See Auth and SuperAdmin.
The token belongs to the community: POST /api/auth/login takes X-CommunityId, the token is valid only in that community (from another community, 401) and PUT /api/auth/change-password returns a new token in data.token. See Authentication.
GET /api/auth/me returns in profiles only the profile of the session's community, and avatarUrl is that profile's photo. See Auth.

MCP: technical details

14 resident-company tools: list_resident_companies, get_resident_company, get_my_resident_company, create_resident_company, update_resident_company, close_resident_company, list_resident_company_members, invite_resident_company_member, update_resident_company_member, remove_resident_company_member, list_resident_company_invitations, list_my_company_invitations, accept_company_invitation and decline_company_invitation. Closing, removing and declining ask to confirm; the company admin's invitation stays pending until accepted. See Tools · Resident companies.
13 round tools: list_inspection_sectors, create_inspection_sector, update_inspection_sector, delete_inspection_sector, create_inspection_spot, update_inspection_spot, delete_inspection_spot, list_inspection_rounds, get_inspection_round, start_inspection_round, mark_inspection_spot, complete_inspection_round and get_support_resource_history, and the run_inspection_round recipe. See Tools · Support.
The server now has 437 tools and 13 ready-made recipes.

15 octobre 2026

2026-10-15T23:59:59-03:00

Today Downloads takes a whole batch of files in one go, and bringing content in from elsewhere is one click away on the create button.

What's new

Polls in the Feed and in Content. The team (owner, admin and moderator) creates a poll from the arrow next to New Status or New Content, under New poll: 2 to 10 options, single or multiple choice, an optional deadline and, in the Feed, who sees it (Public, Members or Subscribers). Members vote, change and remove their vote, and see the results after voting or once the poll closes; the team always sees them, and who voted for what. All of it through the assistant too. See Polls.
Many files at once in Downloads. In Repository mode, the arrow next to New file opens Upload multiple files: pick the files, and each one becomes an item, published as soon as it finishes uploading (or kept as a draft, visible only to the team). See Upload many files at once.
Downloads take audio and video (MP3, WAV, MP4 and MPEG) up to 4 GB, with upload progress and a clear list of formats. Other files keep up to 200 MB each; the upload area shows both groups, and the upload shows the speed and time left. See Accepted files.
Downloads with folders and an audio and video player. New file uploads the file right away, New folder groups several, and audio and video (MP3, WAV and MP4) play on the item's page. See File or folder and Listen and watch.
Import content from the create button. In Content and Feed spaces, the arrow next to New Content (in the Feed, New Status) opens Import content. Only the owner and admins see this option. See Import content.

Improvements

Posts for Subscribers work, and everyone sees only what they may. A status with Subscribers visibility now shows to people with an active subscription and to the team, and the Feed and recommendations show each person only what they may see.
The Gallery loads as you scroll. The next images show up on their own when you reach the end of the list, with nothing to click. See Gallery.
The event page shows what each person can see. Whoever lacks the plan or the ticket sees the sales page, with the button to subscribe or buy; members-only events ask people to sign in. See Who sees the event.
Paid ticket badge. In the Feed and in the Events space list, the card of an event sold through a paid product shows Paid ticket to whoever has not bought it yet.
Form action buttons stay visible at all times.
New security controls.

Fixes

Product, event, call for papers and community images (logo, favicon, sharing image) that disappeared when replaced by another of the same format now stay online; if you saw an image disappear, upload it again.
Creating a post with the same title as a deleted post no longer fails.

For developers

API

A poll field on POST /api/status and POST /api/content, and the routes GET /api/polls/{id}, POST and DELETE /api/polls/{id}/vote, PUT /api/polls/{id}, POST /api/polls/{id}/close and GET /api/polls/{id}/votes. poll comes in feed, status and content items and in recommendations. See Polls.
GET /api/events/{identifier} requires X-CommunityId and carries requiresPlan and requiresPurchase; on the sales page, the livestream, recording and address come null. See Events.

MCP: technical details

Seven new tools: create_poll, get_poll, vote_poll, retract_poll_vote, update_poll, close_poll and list_poll_votes, and the recipe ask_community_poll. See Tools · Content.

14 octobre 2026

2026-10-14T23:59:59-03:00

Today the campaign audience gets exclusions: besides choosing who receives it, the team says who does not. And the Dashboard is no longer just numbers: clicking an indicator or a chart point opens the list behind it.

Exclude people from a campaign's audience

What it is. Below who is in the audience (Everyone, or groups, tags and people), the new Exclude box takes groups, tags and people. Anyone matching an exclusion does not receive it, even if they are in an included group. The Audience preview and the send dialog show how many the rule removed: "1,240 in the selection, 312 excluded by the rule". Repeating campaigns get it too.

Example. Groups Inscritos 2023 and Inscritos 2025, excluding Inscritos 2026: it reaches those who signed up before and have not come back.

Where to find it. Administration › Campaigns, in the editor's E-mail and audience step. See The audience.

Audience exclusion through the assistant

What it is. Ask the assistant "send to Inscritos 2023 and 2025, minus those in 2026": it builds the audience with the exclusion, shows the summary sentence (how many in the selection, how many the rule removed, how many receive it) and repeats it before sending. See the recipe Send to 2023 + 2025, minus those in 2026.

From the Dashboard number to the filtered list

What it is. Clicking an indicator or a chart point on the Dashboard opens the list behind the number, already filtered to the same period: Active members opens the week's active members (the total matches the card); an Engagement point, that day's active members; Revenue and Sales, the sales of the period or the day; Presence and Bookings, the list of the day or the week; Campaigns, the campaigns sent in the period.

Why it matters. Seeing that 42 people were active is good; knowing who they are is what lets you act.

Where it is. Administration › Dashboard. On the list, the period shows as a chip with an × to remove. The days are the community's time zone days. Growth, New content and the Engagement card still have no list. See From the screen to the list.

Members and campaigns filtered by period

What it is. The Members list takes "Active from … to …" and "Joined from … to …", and the Campaigns list, "Sent from … to …", from the Dashboard or from the page address. Whoever joined and already left does not show up under Joined. Through the assistant: "who was active in the last 7 days?", "who joined this month?", "which campaigns went out last week?". See Filter by period, Filter by send period and the recipe Who was active, who joined and what was sent.

Analytics: who is here, where they come from and where buyers give up

What it is. The new Analytics page shows who visits the community, who is in it right now and at which step buyers give up. It is Memberfy's own and works with no setup. Four tabs:

Realtime: how many people are online now (logged-in members and visitors) and in the last 30 minutes, minute by minute.
Overview: visits per day, the most viewed pages and spaces, and where people come from.
Search engines and LLMs: how often search engines and AI assistants read the community's pages.
Purchase funnel: from the storefront to payment, how many went through each step and who stopped at each one.

Note on visits. Visits are not unique people: someone who came on three different days counts as three visits.

Where to find it. Administration › Analytics, for the owner and the admin; finance sees only the Purchase funnel. On the Dashboard, the Online now card takes you there. See Analytics.

Engagement, with the statement of each activity

What it is. The Engagement page shows the period's numbers compared with the previous period, activity per day, the most engaged people and the statement: one line per activity (post, comment, reaction, event registration, completed lesson, attendance…), with who did it, where and when. The statement has filters by person, kind and space, a link to what was done and CSV export.

Where to find it. Administration › Engagement, for the whole team (owner, admin, moderator and finance). The Dashboard's New content and Engagement cards open the statement already filtered. See Engagement.

Logs get their own page

What it is. The Logs left the Members tab and became a page in Administration, with everything the community records in one place: team, platform, AI assistant, members, e-mails, imports, finance and moderation. You can search, filter by person and period, and open each record to see what changed. The old address takes you straight to the new page.

Where to find it. Administration › Logs, for the owner and the admin; finance sees the financial records. See Logs.

Google Analytics with the community's purchases

What it is. With the community's Google Analytics 4 ID, Memberfy now sends, besides visits, the e-commerce events (storefront, checkout, purchase and refund), sign-up, login and the waitlist. The new optional API secret (Measurement Protocol) field makes purchases reach your GA4 even when a PIX or boleto is paid later, with the page closed. Once saved, the secret never shows again.

Where to find it. Settings, next to the Google Analytics ID. See Google Analytics.

Members list with columns, sorting and search across all fields

What it is. In the Members list, the team chooses the columns (job title, tagline, phone, groups, tags, plan, member since and each custom field), sorts by clicking a column header and searches every field at once: name, email, job title, tags, groups, custom fields and phone. Case and accents don't matter. The pagination also shows above the list. See The list.

What it is. The Custom fields tab is now called Form and gets three field types: Email, Phone and Link, each checked for the right format. A text field can have a validation rule (for example, a 6-digit registration number), with the message the person sees when it is wrong. And the Ask on sign-up option shows an optional field on the sign-up form.

At sign-up. The sign-up form asks for the required fields and those marked Ask on sign-up, in the list's order; the account is created only when everything is filled in the right format. See Custom fields and Sign-up and entry.

Profile: job title, a new edit screen and a nudge to add a photo

What it is. The profile gets a Job title (for example, Product manager at Acme), shown under the name on the profile and in the people search. The Edit profile screen was redesigned in two columns, with the profile type as cards and, in the same place, job title, phone and the community's fields. And whoever still has no photo sees a bar inviting them to complete their profile, which can be dismissed with Not now. See Account and profile.

A seven-step purchase funnel, from visits to payment

What it is. The Analytics Purchase funnel now starts at Visits and runs to Paid: seven steps, each with a line explaining who counts in it and the share of visits that got there (% of visits). It also shows how many went straight to a product, the orders that came in without going through the app (direct link, assistant, API) and since when there is data.

More than one product. The Product picker selects several products and plans at once, with search.

Who stopped. Who stopped here opens a dialog with search by name or email, pages and the products each member stopped on.

Where. Administration › Analytics, Purchase funnel tab. See Analytics.

Gallery: bulk upload with each photo's progress

What it is. When you upload several photos at once, each one shows its progress (Optimizing, Uploading 42%, Processing, Ready or Failed, with Retry), and the button becomes the batch's progress: Uploading 12 of 30 · 40%, Processing, Done or 3 failed · try again. Photos are reduced in the browser before uploading (up to 3840 px on the longest side, no visible loss), so even 50 MB ones go up fast.

Without being stuck in the dialog. Minimize keeps the upload going in a floating pill while you browse; closing the tab mid-upload asks for confirmation. In the gallery, the photo shows as Processing until it's ready. See Gallery.

Publication date on posts

What it is. The owner and the admin pick a past date for a post, an article or a status, under More options › Publication date. The post lands in the Feed and in the space's list at that date, with the time in the community's time zone.

Why it matters. Whoever brings a community over from another platform, or records something that went out earlier, keeps the original order without firing news about old content: a post with a past date notifies no one and earns no ranking points. Future dates aren't accepted (this isn't scheduling).

Where. In the form to create or edit a post or status, right before Publish. See Publication date.

Posting on behalf of another member, through the API and the assistant

What it is. Through the API and the assistant, the owner and the admin can publish a post or a status in another member's name, to bring over the community's history with each post's author. Only for someone with a role below yours, always silently (nobody earns points or gets notified), and who posted it is recorded in the Logs. See Posting on behalf of another member.

Content import from a spreadsheet

What it is. The new Import content button brings posts, articles and short posts into the community from an .xlsx or .csv spreadsheet, with each one's original date and author, matched by email. You choose where each column goes, check a preview with the summary and the first 10 rows, and only then import. The import runs in the background, with progress, a button to cancel and, at the end, a report you can download as a CSV.

Why it matters. Whoever comes from another platform brings the whole history in the right order, without setting off notices about old content: nothing is notified and no one earns points. Importing the same spreadsheet again doesn't duplicate anything, and the images in the text become hosted on Memberfy.

Where it is. In the header of Content and Feed spaces, for the owner and admins.

How to start.

Export the posts from the old platform to a spreadsheet, with title, text, date and the author's email.
Click Import content, upload the file and check the columns and the options.
Read the preview and click Import.

Example. A newsletter with 800 issues since 2019 becomes 800 articles in the Archive space, each on the date it went out. See Importing content from a spreadsheet.

Links become a player or a card

What it is. A link in the text of a post or a status now shows up as a player or a card, as on social networks. YouTube videos (live streams and the start time set in the link included), Vimeo and Loom, music and podcasts from Spotify and SoundCloud, Instagram posts and reels, LinkedIn posts and Google Maps play or show right there. News and sites become a card with title, image, description and domain; a page without an image gets a page snapshot. App stores become an app card, WhatsApp shows up without revealing the number, GIFs show as images and shorteners lead to the final address.

Why it matters. A link stops being raw text: the live stream video plays inside the post itself, and a shared news story shows what it's about before the click.

Where it is. In the post and status editors: paste a link and the preview shows up right away, below the text. Up to 5 per post, ready a few seconds after saving. All images are hosted by Memberfy; some sites block reading and show up with just the domain. The spreadsheet and Substack imports also turn links into players and cards. See Links become a player or a card.

Gallery: photos that load without breaking

What it is. While a gallery photo loads, its spot pulses in the community's color instead of showing the broken-image icon. When you open a photo, the bands around it are filled with the photo itself, blurred, instead of black bars; the same goes for the photos of Classifieds ads. See Gallery.

Free trials that charge at the end, one per person

What it is. A plan with Free Trial? now really starts with no charge, and billing happens when the trial ends: on a card, automatically; with PIX or boleto, the charge arrives by email before the end and follows the renewal schedule. With Require Card for Trial?, the card is asked for upfront.

One trial per person in each plan. It covers every billing option of the plan and is counted by email and by card: whoever already had the trial, even after canceling or switching options, pays from day one. Coupons don't apply during the trial, which is already free.

Why it matters. Before, a trial could end without the first charge ever happening. Now a trial turns into paying subscribers at the end instead of open-ended free access. See Free trial.

Request a community on the website, with an answer by email

What it is. Whoever requests a community at memberfy.net/en-us/request-access passes a quick anti-bot check, sees right away whether the address is free and gets the "We received your request" email. Once the Memberfy team approves it, the community is created with its address already live and 90 free days on the chosen plan, no card, and the new owner gets the email with the plan and the Set my password button. See Getting your community.

Improvements

Images up to 50 MB across the app: Gallery, profile photo, Classifieds ads, email campaigns, Downloads covers, product images, logo and social media image, parcel and Support photos, and images the assistant receives by link. The favicon stays at up to 2 MB. See Gallery.
Gallery: optional title and drag and drop. A photo's title starts empty instead of the file name, and can stay blank or be cleared later. Photos can be dragged onto the upload dialog or anywhere on the gallery page. See Gallery.
Photos up to 50 MB when creating or editing a member: the Avatar in New Member and in member editing takes the same limit as the rest of the app. See Invite members.
The sales of a day opened from the Dashboard use the community's time zone, not your computer's: the list shows the same sales the chart counted.
The connector tells the assistant when the tool list changes and how to update it: disconnect and reconnect the connector and open a new conversation. See The assistant can't see a tool.
Clearer opt-out labels: the scope of someone who asked not to receive e-mails shows as Campaigns only (still gets the community's other e-mails) or All e-mails (gets only account security and purchase e-mails), with a hint of what still arrives. See E-mail campaigns.
The assistant now has 403 tools: it imports posts from a spreadsheet, shows how a link will look in a post, reads Analytics and who is online, the engagement statement and the Logs, uses the members list's columns and search, creates email, phone and link fields with a validation rule and Ask on sign-up, and stores the Google Analytics API secret. See Tools.
Reliability improvements and new security controls.
One photo per person: changing your own photo, in My Account or in Edit profile, changes the account photo and the community profile photo together. Before, My Account could show two photos, one of them empty. The staff changes another member's photo only on the community profile and only for someone with a role below theirs. See Profile photo.
Unified member name: invite with a name and one name per person. The name typed when inviting (in New Member, through the API or the assistant) or in the import spreadsheet becomes the new account's name, and the invitation email already goes out with it. Changing your own name changes it everywhere. The team changes someone else's name only in its own community and only for someone with a role below theirs. See Name.
Lighter gallery bulk upload: the upload list shows small thumbnails, without opening the original photos on the page. See Gallery.
The assistant sees the gallery and classifieds photos: each image comes with a link for it to look at and the time the link expires, which lets it, for example, find duplicate photos. See the recipe Find the duplicate photos in the gallery.
More stability and better performance in the processing the platform does in the background.
Website: the Pricing page on memberfy.net now shows Analytics (with Google Analytics 4), Engagement and the fields asked at sign-up, in every plan.

Fixes

Public galleries showed broken images to visitors who weren't logged in. Now whoever visits a public space sees the photos normally. See Gallery.
The assistant failed to change a member's role, tags, groups and manager. It works again.
Names that showed as the email's username. Someone who joined by invite or import showed in some places as maria (from maria@memberfy.net) and in others with the typed name. Now the invite's name goes to the account. To fix someone who was already like that, edit the Community Display Name: if the person is only in your community, the account name is fixed too. See Name.
The assistant's actions in the Logs read as sentences, in the reader's language, no longer as an internal code. Changes to the community settings show the translated field name.

For developers

API

Checkout of an option with trialDays: the first trial starts with no charge and is billed at the end by the renewal; requiresCardForTrial requires a card method (400 on paymentMethod). One trial per plan, per email and per card; whoever already had it goes through the normal checkout, and two simultaneous checkouts of the same trial get 409 (trialAlreadyUsed).
Gallery: title is optional in POST /api/gallery/images (no title, ""), and PUT /api/gallery/images/{imageId} takes "" or null to clear it. Same for add_gallery_image and update_gallery_image in the assistant.
New POST /api/community-requests (public, rate-limited per IP, with an anti-bot check), used by the website form to request a community.
Campaigns: the audience takes exclude (groupIds, tags, profileIds); a group or person outside the community is refused with 422. The audience preview returns candidatesBeforeRule and excluded.byRule. See the API Reference.
GET /api/profiles/list takes activeFrom/activeTo and joinedFrom/joinedTo, and GET /api/campaigns takes sentFrom/sentTo: YYYY-MM-DD dates, inclusive, in the community time zone; an invalid date or a start after the end returns 400.
Analytics: GET /api/analytics/overview, /pageviews, /funnel, /funnel/members, /online and /realtime, with X-CommunityId. Engagement: GET /api/reports/engagement/activities (also as CSV), and GET /api/reports/engagement returns compare. Logs: GET /api/logs.
GET /api/profiles/list takes fields= (phone, groups, plan, custom fields), searches every field and takes sortBy=jobTitle or a custom field. The profile has jobTitle.
Custom fields: EMAIL, PHONE and URL types, pattern, patternMessage and askOnSignup. New GET /api/member-fields/signup (public); POST /api/auth/register takes fields and, without a required one, returns 422 on the field.
PATCH /api/communities/{id}/settings takes gaApiSecret. PUT /api/communities/{id} no longer takes payoutEnabled and signupModel (400 on the field): both change only in the settings. See Creation order.
POST|PUT /api/content and POST|PUT /api/status accept publishedAt (ISO 8601, past or now; owner and admin only, otherwise 403; future or invalid, 400) and authorProfileId (posting on behalf of another profile in the community, only with a role below yours: 403 otherwise, 404 if the profile isn't in this community). Responses include publishedAt, and lists and the feed sort by it. See Content › In the API.
Post import from a spreadsheet: POST /api/import/spreadsheet (analysis), POST /api/import/spreadsheet/{id}/preview, POST /api/import/spreadsheet/{id}/start, GET /api/import/spreadsheet/{id} and GET /api/import/spreadsheet, owner and admin only; one import per community at a time. See Import.
POST|DELETE /api/upload/avatar/profile on someone else's photo needs a role above theirs (403 on profileId); your own photo changes together on the account and the profile.
POST /api/media/urls and GET /api/media/{id}/url accept visitors who aren't logged in for the media of public spaces.
Analytics: GET /api/analytics/funnel returns the visit step, untrackedOrders and collectionStartedAt, and accepts productIds; GET /api/analytics/funnel/members accepts productIds, page and search and returns each member's products. New POST /api/media/upload-urls to upload images straight to storage.
Link embeds: POST /api/embeds/resolve ({ url }, any member) returns a link's player or card; 422 for an invalid link or a private address, 429 with Retry-After (30 per minute per person and 300 per community; links not in the cache, 10 and 60). Posts and statuses carry embeds (up to 5, in text order), filled in the background. See Embeds.
Person name: POST /api/profiles/invite accepts people: [{ email, name }] (emails still works); PUT /api/profiles/{id} and PUT /api/members/profile accept name, and responses include name. Changing someone else's name requires a role above theirs (403 profile.nameRoleTooHigh, on name) and the profile in the X-CommunityId community (403). See Person name.

MCP: technical details

create_campaign, update_campaign and preview_campaign_audience accept exclude: { group_ids, tags, profile_ids }; the preview and the confirmation of send_campaign and schedule_campaign carry audience_summary. See E-mail campaigns.
list_members takes active_from/active_to and joined_from/joined_to; list_campaigns takes sent_from/sent_to. See list_members.
New: analytics_report, get_online_now, list_engagement_activities and list_logs; engagement_report returns compare_summary. See Reports and charts.
list_members takes include, custom_field_keys, sort_by: jobTitle and sort_by_custom_field; create_member_field and update_member_field take the email, phone and url types, pattern, pattern_message and ask_on_signup; update_community_settings takes ga_api_secret. See Tools · Members.
analytics_report accepts product_ids, step: visit and, in funnel_members, page and search; the funnel returns step_labels and funnel_notes. Images by link up to 50 MB. See analytics_report.
create_post and create_short_post accept published_at and author (profile id, e-mail, name or link); update_post accepts published_at. See create_post.
list_gallery_images, list_classified_ads and get_classified_ad return image_url, thumbnail_url, url_expires_at and url_valid_seconds on each image; get_media_url, get_download_url and get_lesson_media_url also return url_expires_at and url_valid_seconds. See list_gallery_images.
update_avatar on someone else's photo follows the same role rule as the API.
New: analyze_content_import, preview_content_import, start_content_import and get_content_import, to import posts from a spreadsheet (admin). See analyze_content_import.
New: preview_link (any role, read-only, no confirmation), on top of POST /api/embeds/resolve. create_post, create_short_post, update_post, list_posts and open_link bring embeds. See preview_link.
invite_member and invite_members send the name with the invite; update_member_profile and update_my_profile accept name (display_name and full_name remain as synonyms). See update_my_profile.

13 octobre 2026

2026-10-13T23:59:59-03:00

Today brings member import from a spreadsheet, custom fields and a new campaign editor. Earlier on, the room door panel, the Parcels locker list, taking a room out of use from a ticket and per-recipient variables in campaigns arrived. E-mails now use the community's color, and the moderation queue works fully again.

Import members from a spreadsheet
Custom fields
New campaign editor
Suspension of joining and sales

Import members from a spreadsheet

What it is. Bring the list from any .xlsx or .csv spreadsheet into the community: an event's attendees, a member base, a class. You say where each column goes (e-mail, name, phone, tags, groups, consent or a custom field), choose role, groups and tags for everyone and check a summary before importing.

Why it matters. Before, you could only paste e-mails, and the rest of the data was lost. Now name, phone, company and ticket type come in too, and existing members just gain the groups and tags.

Where. Administration › Members › Invite Members, Import spreadsheet tab.

How to start.

Write the List origin (it goes in the invitation e-mail) and choose the file.
Check the columns: the recognized ones come first; mark the consent one, if there is one.
Read the Summary and click Import. The import runs in the background and you get the report.

Example. A spreadsheet of 220 attendees, with the column Agreed to receive news: only the 97 who marked Yes get in, with Ticket type becoming a tag. Each one gets the invitation with the origin and the link Thanks for the invitation, but I do not want to join; whoever declines can no longer be imported or invited by the community. See Import members from a spreadsheet.

Custom fields

What it is. Extra registration details for each member: company, job title, city, a date, yes/no or a list of options. A required field asks, on the next visit, whoever lacks the value to complete their registration.

Why it matters. The community keeps what it needs to know about each person, and uses it in campaigns: {{field_company}} becomes each person's company.

Where. Administration › Members, Custom fields tab. The values show on the member's record (team) and in My Account (the person themself); other members don't see them. See Custom fields.

New campaign editor

What it is. The campaign editor starts with the subject, the preview text and the audience and, in the second step, shows the e-mail as it arrives, with the community's logo and colors and the owner's contact in the footer. You write inside the block, drag blocks into place and insert variables with a button, custom fields included. The product, event and course blocks take 1 to 6 items, in a grid of 2 per row, and the picker only shows what can go in the e-mail.

And more. The list became a table with status, audience, sent, open rate and click rate; at the top, Last 30 days compares sent, opens, clicks and unsubscribes with the previous 30 days and refreshes every minute (Updated at …, with the Refresh button). Duplicate creates an identical draft to reuse a campaign. The Dashboard chart gained the Campaigns tab.

Where. Administration › Campaigns. See E-mail campaigns.

Suspension of joining and sales

Memberfy can now suspend people joining and sales for a community, for example while assessing a report of invitations without consent. While suspended, the community doesn't accept invites, imports, sign-ups or new sales; existing members keep their access and subscriptions renew. The team sees the reason in a fixed notice and by e-mail. See Suspension of joining and sales.

Door panel

What it is. A tablet at the room's door shows whether it is free or busy and the day's bookings. Whoever booked taps Start meeting, on the tablet or in My bookings. If the community wants, a room nobody starts within the grace period is released for others.

Where. On the Bookings room, with one secret link per tablet; the panel options in the space settings. See Door panel.

Parcels: locker list and reminder

What it is. The community registers its lockers by name, and the front desk picks one from the list when registering a parcel. With a reminder delay set, whoever has not picked up gets an e-mail reminder, up to the maximum number of reminders.

Where. Configure space in Parcels, under where parcels are kept and in the Lockers tab. See Parcels.

Support: room out of use and Report

What it is. From the ticket itself, the team takes the room out of use for a period, canceling bookings with a full credit refund, and returns it when the repair is done. The Support Report shows open, resolved and overdue tickets and average times by category, assignee and room.

Where. On a ticket with a room and in the Support management bar. See Support.

Campaigns that fit each person

What it is. The campaign subject and text take variables: {{first_name}}, {{leader}}, {{groups}}, {{points}}, {{plan}}, {{member_since}} and more. Each person reads their own data, and {{leader|our team}} covers whoever lacks it. And the community's e-mails (campaigns, invitations, notices, certificates) now use the community's primary color on buttons and links instead of a fixed green.

Example. "{{first_name}}, {{leader|the team}} wants to hear from you" arrives as "Maria, Bruno wants to hear from you".

Where. Administration › Campaigns, with the editor's Insert variable button or by typing the variable in the text. See Per-recipient variables and Colors.

Improvements

Invite Members: the window gained Groups and Tags at the top, for all invitees, and shows the result for each e-mail: invited, updated (already a member and got the groups and tags) or skipped, with the reason. Before, one invalid e-mail brought down the whole list. See Invite members.
Consent notice: the invite window reminds you that only people who asked to receive e-mails should be added and links to the Invitation policy.
Terms of use at sign-up: creating an account, setting the password from an invitation and creating a community now record acceptance of the Terms of use.
Interface details: the Esc key in a picker inside a window closes only the picker, without losing what was filled in, and the campaign editor's block bar no longer covers the content.
Store: an add-on card opens its details, like a product's. And Feature in the store, in the product and add-on forms, adds the Featured badge and moves the item to the top of a store that shows every product. See Store.
Monetization: the Products and Options tables search every product, not just the first 20, and now have pages. See Products.
Dashboard: the sparklines and the chart show the previous week as a dashed line, and on a phone tapping the line shows the day and value. See Dashboard.
Missing image: a course, event, content, download, ad, room, product, plan or add-on with no image shows a gradient in the community's colors instead of a gray frame. See Colors.
Credits: the statement shows the booking's room and time on each entry. See Credits.
Parcels: a parcel page with no photo no longer shows an empty frame.
Community e-mails: the header is more compact.
Website: the For Coworkings, Pricing and Platform pages at memberfy.net now show the door panel, the locker list and parcel reminder, taking a room out of use from Support, campaign variables, the week-over-week Dashboard, featuring in the Store and e-mails in the community's color.
Website, second round: the Platform, Pricing, For Communities and For Coworkings pages on memberfy.net now show member import from a spreadsheet, custom fields and the new campaign editor; the migration questions now say members come in by spreadsheet, only those who consented.
Help Center: new Invitation and member import policy: who can be invited, what is forbidden, warnings, strikes and the 14-day appeal. Plus the Terms of use, also in the footer.
New security controls.

Fixes

Assistant: creating subscription plans through Claude or ChatGPT works again. Before, the request failed. See Tools · Sales.
Moderation queue: approving or rejecting posts, articles, courses, events, gallery images and short posts works again. It used to fail, and only classifieds and downloads could be decided.

For developers

API

Campaigns: GET /api/campaigns/variables lists the variables; text with a variable that does not exist is refused with 400 on save, schedule and send.
Products: GET /api/products takes search (title, slug and, for management, the internal name), with page and limit up to 50; isHighlighted is now editable in the form.
Member import: POST /api/members/imports, /preview, /start, the history, the errors CSV and the original file; declining the invite at POST /api/invite-opt-out/{token} and POST /api/profiles/me/decline. See Member Imports.
Custom fields: /api/member-fields and PUT /api/profiles/{profileId}/fields; fields in GET /api/profiles/{id} for the team and the member themself. See Member Fields.
POST /api/profiles/invite reads the community from X-CommunityId, takes groupIds and tags and returns one result per e-mail in data.results.
Campaigns: GET /api/campaigns/stats, GET /api/campaigns/block-items and POST /api/campaigns/{id}/duplicate; the product, event and course blocks take productIds, eventIds and courseIds (1 to 6).
Suspension: invite, import, sign-up and sale answer 403 with code: COMMUNITY_SUSPENDED.
Door panel, booking check-in (checkedInAt, canCheckIn), Parcels lockers, room out of use from a ticket and the Support report: see the API reference.

MCP: technical details

In the second batch, 16 new tools; the server now has 394. By role: owner and admin 394, finance 289, moderator 265 and member 170. And 11 ready-made recipes.
Import (7): analyze_member_import (spreadsheet by link or CSV text), preview_member_import, start_member_import (asks for confirmation, with the origin), get_member_import, list_member_imports, get_member_import_file and withdraw_from_community; recipe import_members. See Tools · Members and the recipe Import a spreadsheet through the assistant.
Custom fields (6): list_member_fields, create_member_field, update_member_field, reorder_member_fields, delete_member_field (asks for confirmation) and update_member_field_values.
Campaigns (3): get_campaign_stats, list_campaign_block_items and duplicate_campaign; create_campaign and update_campaign take product_ids, event_ids and course_ids.
invite_member and invite_members take groups and tags and return the result per e-mail (invited, updated, skipped with the reason). get_community_context includes member_entry (the suspension).
In the first batch, 12 new tools (the server reached 378).
Door panel (4): list_room_panels, create_room_panel, revoke_room_panel and check_in_booking; update_space takes bookings.door_panel. See Tools · Bookings.
Lockers (4): list_parcel_lockers, create_parcel_locker, update_parcel_locker and delete_parcel_locker; reminder_after_days and reminder_max_count on the space. See Tools · Parcels.
Support (3): close_resource_for_ticket (asks for confirmation), reopen_resource_for_ticket and get_support_report. See Tools · Support.
Campaigns (1): list_campaign_variables; the text tools explain {{name}} and {{name|fallback}}, and an unknown variable comes back as one sentence with the field and the next step. See E-mail campaigns.
Products: highlighted on create_product, update_product and update_products; list_products takes search, page and limit, and suggests the next page. See Tools · Sales.

12 octobre 2026

2026-10-12T23:59:59-03:00

Today the coworking modules arrive: Attendance, Bookings, Scheduling, Parcels, Visitors and Support, plus the Team Dashboard.

Attendance

What it is. A space that records who is on site: members tap I've arrived and I'm leaving, staff see who is here, register guests and fix visits, and a kiosk on the front desk iPad welcomes visitors without a login.

Where to find it. When creating a space, on the Coworking tab. See Attendance.

Room bookings with credits

What it is. Members book rooms, desks and stations paying in credits, which come from a monthly plan, a product or a manual grant by staff. There is a search for what is free, rescheduling, maintenance blocks and a calendar invite (.ics) by email with every booking.

Where to find it. A Bookings space, on the Coworking tab; credits under Monetization. See Bookings and Credits.

Scheduling time with people

What it is. Members book a time slot with a person in the community (mentoring, class, appointment). A time offered by a member is always free; the credit-priced band is staff-only.

Where to find it. A Scheduling space. See Scheduling.

Parcels

What it is. The front desk registers letters and packages with a photo and location, the recipient gets an email notice and confirms pickup. There are returns, discards and a history.

Where to find it. A Parcels space, on the Coworking tab. See Parcels.

Visitors

What it is. The member pre-registers the guest (name, day and time), the front desk marks the arrival with one tap and the host is notified. The Attendance kiosk recognizes who is expected, and the guest does not count as a member.

Where it is. When creating a space, in the Coworking tab. See Visitors.

Support

What it is. Maintenance tickets and requests, with photos. The team triages the queue, assigns, replies and resolves; who answers is set by tag, group or person, the expected deadline is per category and counted in service hours, and the internal note never shows to the resident.

Where it is. When creating a space, in the Coworking tab. See Support.

Team Dashboard

What it is. The community's day on one screen: four indicators with a comparison to the previous week, pending actions (moderation is approved or rejected right there), 14-day charts and insights. It refreshes by itself.

Where it is. Side menu, under Administration › Dashboard. See Dashboard.

Improvements

New security controls.
Home is now always the first item in the menu.
Complete translations in all 10 languages.

For developers

API

Attendance: /api/attendance/spaces/{spaceId}/... (check-in, check-out, guest-check-in, overview, present, visits, kiosks), GET /api/attendance/me/visits, PATCH and DELETE /api/attendance/visits/{visitId} and the kiosk routes under /api/attendance/kiosk/....
Bookings: /api/bookings (search, availability, amenities, bookings, cancel, reschedule, no-show and calendar.ics) and /api/bookings/resources with exceptions and price-rules.
Credits: /api/credits/me, /api/credits/me/entries, /api/credits/profiles/{profileId}, POST /api/credits/grants, POST /api/credits/adjustments and GET and PUT /api/credits/settings.
Scheduling: GET /api/scheduling/config, /api/scheduling/hosts, /api/scheduling/pending and PUT /api/scheduling/resources/{resourceId}/listing.
Parcels: /api/parcels/spaces/{spaceId}/... (overview, members, parcels), GET /api/parcels/me/parcels and /api/parcels/parcels/{parcelId} with photos, pickup, return, discard and reopen.
Visitors: /api/visitors/spaces/{spaceId}/... (invitations, me, today, hosts) and /api/visitors/invitations/{id} with arrive and undo-arrival.
Support: GET /api/support/config, GET /api/support/summary, /api/support/tickets (list, open, read, edit, delete), assignees, cancel, reopen, comments, photos and GET /api/support/resources/{resourceId}/open-count.
Dashboard: GET /api/dashboard/summary.

MCP: technical details

65 new tools; the server now has 340. By role: owner and admin 340, finance 254, moderator 228 and member 151.
Attendance (12): get_attendance_overview, check_in, check_out, list_present, list_visits, list_my_visits, update_visit, delete_visit, check_guest_in and the kiosk links. See Tools · Attendance.
Parcels (16): register_parcel, list_pending_parcels, mark_parcel_picked_up, do_i_have_parcels and the rest. See Tools · Parcels.
Bookings and Scheduling (30): search_booking_rooms, check_availability, create_booking, create_booking_for_member, reschedule_booking, get_booking_ics, search_scheduling_hosts and the rest. See Tools · Bookings and Scheduling.
Credits (7): get_credit_balance, list_credit_entries, grant_credits, adjust_credits, revoke_credits, get_credit_settings and update_credit_settings. See Tools · Credits.
26 new tools; the server now has 366. By role: owner and admin 366, finance 278, moderator 252 and member 167.
Visitors (9): create_visitor_invitation, list_visitor_invitations, get_visitor_invitation, update_visitor_invitation, cancel_visitor_invitation, list_visitors_today, search_visitor_hosts, mark_visitor_arrived and undo_visitor_arrival. See Tools · Visitors.
Support (16): create_support_ticket, list_support_tickets, get_support_overview, update_support_ticket, add_support_comment, add_support_photo, cancel_support_ticket, reopen_support_ticket and the rest. See Tools · Support.
Dashboard (1): get_dashboard. See Reports and charts.

11 octobre 2026

2026-10-11T23:59:59-03:00

Today community staff can build courses without leaving the app.

Build the course in the app

What it is. Owners and admins create the course under New course (title, address, description, level, tags and cover), add video, text, link or image lessons to modules, reorder with up and down buttons, and use the Manage course bar to publish, go back to draft, archive or delete. The Students tab shows who started the course, the progress percentage, the last activity and who finished; moderators see it too, read-only.

Why it matters. Before, only the assistant or the API could build a course. Now staff does it all on screen, with warnings before publishing an empty course and before deleting something students have progress in.

Where it is. In the Courses space, New course; then the course page, with the Content and Students tabs.

How to start.

Click New course, fill in the General tab and create it. It starts as a draft.
Under Content, add the modules and lessons.
Under Manage course, click Publish.

Example. A school builds Excel from Scratch with 3 modules, checks the Students tab the next week and sees who is past the halfway mark. See Courses.

"A single course" space

What it is. When you create a Courses space, under How the space works, choose List of courses (the default) or A single course. With the second, whoever opens the space lands straight on the course, with no list. The space and the course are created together, with the course as a draft. You can change the mode later under Edit space.

Why it matters. For a mentorship or a program with just one course, members skip a list with one item.

Example. A 90-day mentorship becomes a space with one course. See Courses.

Certificate when the course is completed

What it is. In Edit course (or New course), on the Certificate tab, the owner or admin turns on Issue a certificate?, picks a template from the Certificates module (the Platform default comes selected) and adjusts the text. Whoever completes the course after that gets the certificate by email and finds it in My certificates.

Why it matters. The team no longer issues them one by one. It is one certificate per person per course, the workload comes from the sum of the lesson durations, and people who completed before it was turned on do not get one (no retroactive issuing).

Example. The school turns on the certificate for Excel from Scratch with the brand template; each student who finishes the last lesson sees "Your certificate is being generated" and, within seconds, the View certificate button. See Courses.

Certificate for attending events

What it is. In the event form, the owner or admin turns on Issue a certificate?, picks the template (the Platform default comes selected) and adjusts the text, which now also accepts the event date. Whoever confirmed attendance with Going gets the certificate by email about 1 hour after the event ends and finds it in My certificates.

Why it matters. The team does not have to issue them one by one after every event. There is no check-in yet: someone who confirmed and did not go also gets it, and the team can revoke theirs. An event that ended before the switch was turned on does not issue.

Where it is. In the create and edit event forms; the event needs an end date and time. See Events.

Classifieds

What it is. A new kind of space where members post ads for jobs, services or items for sale, with a category, up to 6 images and a term, and other members show interest with a message. The advertiser and the team see who is interested, with the account's email and phone, and mark each interest as seen or answered. The ad disappears on its own when the term ends.

Why it matters. The community's informal exchange (a job, a service, something for sale) gets a category, a term and a contact funnel, instead of getting lost in the feed. The platform does not intermediate sales, payments or negotiations: the value is information only.

Where it is. When creating a space, choose the Classifieds module and set categories, terms, whether it shows value and whether it requires approval. Approval is optional, and the term counts from the first approval. See Classifieds.

Lessons in sequence and module release

What it is. On the course's Publication tab, Require sequence makes the student open a lesson only after completing the previous one. On each module, Release sets a fixed date or days after enrollment: the module opens at midnight in the community's time zone, and leaving the course and coming back does not restart the count.

Why it matters. Guided courses, for cohorts or on a weekly rhythm, without the team opening module by module. The student sees when each module opens, and the team previews everything.

Where it is. On the course, in the tab and buttons above. See Courses.

E-mail campaigns

What it is. A new area, under Administration, where the team writes an announcement by e-mail and sends it to the community. Build the e-mail with text, button and image blocks, choose the audience (everyone, or groups, tags and people), check the preview of who receives it and who is left out, send yourself a test and, at the end, Send now. The whole team creates drafts and tests; only the owner and admins send.

Why it matters. Notify the cohort or the whole community without leaving Memberfy, with care: each community has a sending quota (2 per day, 14 per week), someone who unsubscribed never returns to an audience, and the delivery, open and click numbers appear as totals, with nobody's name. Security e-mails, receipts and legal notices always arrive.

Where it is. Administration › Campaigns. Each person chooses what to receive under E-mails from this community, in My Account. See E-mail campaigns.

The community around the course

What it is. The course gained a Course discussion and a Lesson discussion, with replies and the seven reactions; Leave course (progress is kept); the Instructor and What you will learn on the page; the Saved filter; the student count (from 10); and the Course leaderboard, which the team turns on in the form.

Why it matters. Students ask questions to the cohort inside the lesson, see who teaches the course and follow their own progress, without leaving the platform.

Where it is. On the course page and in each lesson; the team sets the instructor and leaderboard in the course form. See Courses.

Scheduling and automatic campaigns

What it is. E-mail campaigns can now be scheduled: once, every day or on weekdays, in the community's time zone, with Pause, Resume and Cancel campaign. The report shows numbers only (delivered, opens, clicks, bounces and complaints). There are new blocks with the community's content (Latest posts, Upcoming events, New courses, New classifieds, A course, An event, A product) and Upload image. The Automatic tab comes with Weekly updates ready, switched off: the owner or an admin turns it on after confirming.

Why it matters. The team builds the notice once and it goes out on its own. Only what the whole audience can see goes in, and a week with nothing new sends no e-mail. To protect the e-mail reputation, a community's first sends are limited to 500 people and a campaign with many invalid addresses or complaints pauses by itself, warning the owners. Scheduled, repeated and automatic sends count toward the sending quota.

Where it is. Administration › Campaigns, Campaigns and Automatic tabs. See E-mail campaigns.

Quizzes in courses

What it is. A Quiz lesson, with single-answer questions, a Passing score (%) and Attempts allowed (unlimited if empty). Options are shuffled on every attempt, the best score counts, and passing completes the lesson; when the attempts run out, the lesson stays as not passed and the student moves on. The course gains a Final grade (the average of the quizzes) and, optionally, a Minimum grade for the certificate (%): whoever falls below sees why. Whoever fails sees only the score; the correct answers appear after passing. The team tests in Team preview, recording nothing.

Why it matters. It gives the course a test with automatic grading, with no one on the team grading, and lets you tie the certificate to performance.

Where it is. When adding a lesson, Lesson type › Quiz. See Courses.

Hosted video and files in lessons

What it is. The Video lesson now accepts, besides the YouTube, Vimeo or Loom link, a hosted video uploaded from your computer (MP4, WebM or MOV, up to 500 MB), and there is a new lesson type, File (PDF, Word, Excel, PowerPoint, ZIP or image, up to 50 MB). You can create the lesson without the file, as Content coming soon, and publish the course earlier; replacing and removing also work.

Why it matters. Paid content stays private: only the enrolled student, with the lesson unlocked, and the team reach the file, through temporary links (1 hour for video, 5 minutes for files).

Where it is. When adding a lesson, Lesson type › Video or File. See Hosted video and file.

Video on the platform page

The Memberfy site has a new video section: video hosted in courses already plays inside the community itself, with no account on a third-party video service. Adaptive streaming, from 240p to 4K, is in invite-only beta and is not yet available to all communities. It is also mentioned on the Communities and HR pages.

Product kinds, free products and waitlist

What it is. Every product now has a kind (Digital, Physical, Course, Event or Download); courses, events and downloads are created with their own product, as a draft and free, and you can sell a course or an event without selling the whole space. A zero price creates a free product (and a zero-price billing option creates a free subscription), with no payment and no fee, and a 100% coupon on a one-off product turns into a free purchase. When the seats run out, the member joins the waitlist: when a seat opens up, the next person gets a 24-hour offer by email. A plan can include products, and access can have a deadline. Finance can also edit price, seats and publication.

Why it matters. The team sells courses, events and one-off files, with limited seats and a queue, and delivers free content with the same purchase flow. The My purchases block shows members what they bought or got for free.

Where it is. Monetization › Products, at the top of the General tab. See Products.

Downloads

What it is. A new space module for sharing files (spreadsheets, e-books, PDFs, templates) in a repository or as a single file, free, sold through a product or included in a plan. The team organizes them by category, members can upload items (with optional approval), and each item shows its download stats. For PDFs, you can turn on stamping: the downloaded file carries the name of whoever downloaded it.

Why it matters. Paid or exclusive material stays in a private area, with a temporary link (5 minutes) per download, and the stamp discourages sharing.

Where it is. When creating a space, choose the Downloads module. See Downloads.

Hosted video in posts, events, gallery and classifieds

What it is. Posts accept hosted video (MP4, WebM or MOV, up to 2 GB), events keep their hosted recording, and gallery and classifieds images are stored in a private area, with a thumbnail, and shown through a temporary link. Uploads show their progress, with Cancel upload.

Why it matters. Video plays inside the community, with no account on a third-party service, and paid content doesn't leak through a link.

Where it is. In the post, event, gallery and ad forms. See Content, Events and Gallery.

Adaptive streaming (invite-only beta)

Hosted video is now delivered in adaptive quality, from 240p to 4K, with a quality selector in the player. It is in invite-only beta: talk to us to join.

Improvements

New security controls.
The lesson duration can be filled in on any lesson type (text, video, link or image).
The certificate prints the workload with its unit ("2 hours", "0.36 hour").
Each student's progress bar now counts only the lessons that exist, and deleting a lesson or module warns how many students have progress there.
Before you delete a course certificate that would be issued again (the person is still entitled to it), the app warns that a new certificate goes out on its own within 15 minutes, with an email to them. To avoid that, remove the person from the course requirements first.
Before you delete a Courses space, the app warns that its courses are deleted too: they leave the list, students lose access, and certificates already issued stay valid.
The AI assistant shows the same warnings before you confirm the deletion.
Confirming attendance closes when the event ends: after the end, only "Not going" is accepted.
The event end must be after its start.
The platform default certificate template is now simply called "Certificate", because it serves courses and events.
The AI assistant turns on the event certificate and lists the events of every Events space.
Moderators and finance read the course lessons without enrolling, including in a course of a paid space.
Removing a post's cover or an event's image now works.
You can replace the image of a gallery photo while keeping its title and tags (the image goes back to moderation).
Login and sign-up e-mails go ahead in the sending queue, even during a large campaign.
Each person chooses, in their profile, what to receive from each community (everything, only notices, or nothing besides security e-mails and receipts).
Finance becomes part of the team: where the moderator acts as team (moderation, events, content, members, groups and tags, certificates, reports), finance acts too. Money, community settings, editing courses and spaces, sending campaigns and assigning roles remain with the owner and admins only.
On mobile, the Administration menu opens and closes, and starts closed.
Login and sign-up e-mails go out faster, even during a large campaign.
The owner sees the video and file storage usage under Settings › General, with a warning from 80% of the limit. The limits only warn and never block an upload.
Finance can now edit products (Monetization and Price and sale of courses and events), including the price and publishing. Creating and deleting stay with owners and admins.

Fixes

The workload is shown with the decimal separator and plural of each person's language.
Recreating a section or a space with the name of a deleted one no longer fails.

For developers

API

GET /api/courses/{id}/enrollments: the Students tab list, paginated (owner, admin and moderator).
PUT /api/courses/{courseId}/modules/order and PUT /api/courses/module/{moduleId}/lessons/order: save the order of all modules (or of a module's lessons) at once.
moduleConfig.mode (single or multi) on Courses spaces and course on POST /api/spaces, which creates the space and the course together. A second course in a single space, and switching to single with 2 or more courses, return 409.
The course's stats.enrollments only comes back for staff. See Order of creation.
certificate (enabled, templateId, text) on POST and PUT /api/courses and in course on POST /api/spaces; GET /api/courses/{id} returns certificate to staff and userCertificate (PENDING or ISSUED) to the student who completed. Errors on certificate.templateId and certificate.text.
GET /api/certificates/templates works without spaceId for owner and admin, with q to search by name.
Classifieds: GET and PUT /api/classifieds/spaces/{spaceId}, GET and POST /api/classifieds/ads, GET, PUT and DELETE /api/classifieds/ads/{id}, the interests at /api/classifieds/ads/{id}/interests, the images at /api/upload/classifieds/ads/{adId}/images and the queue at /api/moderation/classifieds. See Classifieds.
Courses: requireSequential on POST and PUT /api/courses; availableAt or availableAfterDays on modules; locked, lockReason and unlocksAt on the course GET; 409 when completing a locked lesson. Moderators and finance receive lesson content without enrolling.
Images: PUT /api/events/{id} accepts bannerUrl and featuredImageUrl (null removes) and PUT /api/upload/gallery/images/{imageId} replaces the file of a gallery image.
Campaigns: GET and POST /api/campaigns, GET, PUT and DELETE /api/campaigns/{id} (draft), POST .../audience-preview, POST .../test, POST .../send, GET /api/campaigns/quota and GET /api/campaigns/opt-outs; the person's preference at GET and PUT /api/me/email-preferences; public unsubscribing at /api/public/unsubscribe/{token}. See E-mail campaigns.
Courses: POST /api/courses/{courseId}/leave; discussions at /api/courses/{courseId}/comments (with lessonId for the lesson) and reactions; POST and DELETE .../favorite; GET .../leaderboard; instructorProfileId, learningPoints and leaderboardEnabled on create and edit; instructor, learningPoints, studentsCount and isSaved in the response.
Campaigns: POST /api/campaigns/{id}/schedule (scheduleKind DAILY or WEEKLY), .../pause, .../resume, .../cancel, GET .../runs, .../report and .../preview; GET /api/campaigns/automatic and PUT /api/campaigns/automatic/{systemKey}; POST and DELETE /api/upload/campaigns/image; blocks latestPosts, upcomingEvents, newCourses, newClassifieds, course, event and product.
Quiz: lesson type: quiz with quiz (passPercent, maxAttempts, questions); POST and GET /api/courses/{courseId}/lesson/{lessonId}/quiz/attempts; userFinalGrade, finalGrade and certificateMinGrade; userCertificate.status BELOW_MIN_GRADE.
Lesson media: POST /api/courses/lesson/{lessonId}/media/upload-url, .../media/confirm and DELETE .../media; GET /api/courses/{courseId}/lesson/{lessonId}/media returns the temporary link; awaitingMedia and the file type on POST /api/courses/lesson; GET /api/communities/media-usage.
Products: kind (digital, physical, event, course, download) and the GET /api/products?kind= filter; price accepts 0; capacity on PUT /api/products/{id}; includedProductIds on POST and PUT /api/subscription-groups and includedInPlanIds on PUT /api/products/{id}; product in course and event responses. The waitlist at /api/products/{id}/waitlist. Free purchase without paymentMethod (paymentMethod: "FREE").
Downloads: GET and PUT /api/downloads/spaces/{spaceId}, GET and POST /api/downloads/items, GET, PUT and DELETE /api/downloads/items/{id}, the files at /api/downloads/items/{id}/files, POST /api/downloads/files/{fileId}/download, GET /api/me/downloads, GET /api/downloads/items/{id}/stats and the queue GET /api/moderation/downloads/pending.
Hosted media: video in posts, recordings in events and private images in the gallery and classifieds, with a temporary link.
The new errors are in Responses and errors.

MCP: technical details

New: list_course_enrollments (moderator or above), reorder_course_modules and reorder_lessons (admin).
create_space and update_space accept mode; create_space accepts course; create_course accepts mode. list_spaces and get_course show the mode.
enroll_in_course: already_enrolled is only true for an in-progress or completed enrollment. See Tools · Courses.
Course certificate: create_course, update_course and create_space accept certificate; get_course and list_courses show it and warn when the template is archived; list_certificate_templates works without a space for owner and admin, with q; complete_lesson says the certificate arrives by email and suggests list_my_certificates.
12 new Classifieds tools (225 in total): get_classifieds_space_settings, update_classifieds_space_settings, list_classified_ads, get_classified_ad, create_classified_ad, update_classified_ad, delete_classified_ad, express_classified_interest, list_classified_interests, update_classified_interest_status, list_my_classified_interests and withdraw_classified_interest. create_space accepts the classifieds module, and the moderation queue accepts the classifieds type. See Tools · Content.
Courses: require_sequential on create_course and update_course; available_at or available_after_days on the module tools; get_course shows the locks; complete_lesson passes the 409 through.
Images: whatever the app lets you add, the assistant adds, replaces and removes: remove_banner and remove_featured_image (plans, calls for papers and events), remove_image (courses and posts), remove_logo, remove_favicon and remove_share_image (settings), video_url and remove_video (posts) and the file replacement in update_gallery_image.
10 campaign tools: list_campaigns, get_campaign, create_campaign, update_campaign, preview_campaign_audience, send_campaign_test, send_campaign (owner and admin only, with confirmation and consent), get_campaign_quota, delete_campaign and list_campaign_opt_outs. See Tools · Community.
Courses: leave_course and favorite_course; comments and reactions accept course and course_lesson; get_leaderboard accepts course; create_course and update_course accept instructor, learning_points and leaderboard_enabled; list_courses accepts saved. The server now has 237 tools.
11 campaign tools: schedule_campaign, pause_campaign, resume_campaign, cancel_campaign, list_campaign_runs, campaign_report, preview_campaign, list_automatic_campaigns, update_automatic_campaign, upload_campaign_image and delete_campaign_image. See Tools · Community.
Quiz: submit_quiz_attempt and list_quiz_attempts; create_lesson and update_lesson accept quiz (with max_attempts); create_course and update_course accept certificate_min_grade. The server now has 250 tools.
Lesson media: upload_lesson_media (by link or base64 up to 25 MB), remove_lesson_media (with confirmation) and get_lesson_media_url; create_lesson accepts type: file and awaiting_media. The server now has 253 tools. See Tools · Courses.
Downloads (13 new tools; the server now has 275): get_downloads_space_settings, update_downloads_space_settings, list_download_items, get_download_item, create_download_item, update_download_item, delete_download_item, upload_download_file, remove_download_file, reorder_download_files, get_download_url, get_download_stats and list_my_downloads. See Tools · Downloads.
Seats and free products: join_waitlist, leave_waitlist, my_waitlist_position, list_waitlist and claim_free_product. create_course and create_event return the product; update_product, create_product and update_plan accept kind, seats and included products.
Media: get_media_url, remove_post_video and remove_event_recording; create_post, update_post and update_event accept hosted video and recordings. By role: moderator 178, finance 203 and member 120.

10 octobre 2026

2026-10-10T23:59:59-03:00

Today the assistant (Claude, ChatGPT, Cursor) started accepting images everywhere the dashboard does.

Profile picture and featured image, through the assistant

What it is. You can ask the assistant "change my picture to this one" and give the link or file of an image. It changes your picture in the community or, if you ask, your account picture (the same in every community). Moderators and above also change or remove the picture of people in the community. And when creating or editing an event or a call for papers, the assistant accepts the square featured image (1:1), besides the banner.

Why it matters. Before, only the dashboard changed pictures and featured images. Now the assistant does it in the same conversation where it builds the event, and it can use an image it generated itself.

The formats are JPEG, PNG, WebP and GIF; SVG becomes PNG. A file can be up to 5 MB.
If the image can't be used, nothing changes, and the assistant tells you why.
Changing a picture doesn't ask for confirmation.
The community banner is still changed only in the dashboard.

Example. "Change my picture to this one: https://example.memberfy.net/me.png. And set this square image as the featured image of the November Meetup." See the recipe Change your picture and set a featured image and Images.

Courses for members

What it is. Members find the community's courses, open the course and the lesson (video, text, link or image), start, resume where they left off and finish, with progress tracked.

Why it matters. The courses screen used to show only sample content. Now what the team builds is what members see. Creating and editing courses on screen comes to the dashboard later; until then, the assistant (MCP) or the API builds the course. See Courses.

AI assistant switched on by role

What it is. The owner decides who can connect an AI assistant (Claude, ChatGPT, Cursor) to the community, with three switches in Settings › AI assistants: Members, Staff (moderator, finance and admin) and Admins. Turning off cuts access at once; turning on again restores it with no reconnecting.

Heads up: all start turned off. That includes communities that already used the assistant: anyone who is not the owner loses access until the owner turns it on. The owner always has access. If someone's assistant stopped working, this is why: ask the owner to turn on your group's switch. See General settings.

On the website

The website got a country selector. On pages for countries outside Brazil, PIX and boleto are not offered, and numbers follow each country's format.

Improvements

New security controls.

For developers

This part is for people who integrate Memberfy through code. To use what is above, none of it is needed.

MCP: technical details

New tool in Members: 210 in total. update_avatar (all roles; no confirmation) takes member (optional), scope (community, the default, or account), remove, image_url and image_base64. Any role changes their own picture; someone else's needs moderator or above, and only for people in the connected community; scope=account is always your own. By role: owner and admin, 210; moderator, 124; finance, 104; member, 87. See Tools · Members.
Featured image 1:1 on events. create_event and update_event accept featured_image_url and featured_image_base64; update_event checks the images before changing the event. In create_event, a refused image becomes warnings.
Call for papers. create_call_for_papers and update_call_for_papers accept the featured image as a file too (featured_image_base64), and update_call_for_papers checks the images before changing the call.
No API route changed. See Images.

API: courses and the AI assistant

The course GET omits lesson content for anyone who cannot see the space.
Enrolling again in a course returns 200.
GET /api/communities/settings is a new route (read by the team); PATCH .../settings accepts mcpMembers, mcpStaff and mcpAdmins (owner and SuperAdmin only), and POST /api/communities/domain and authorize/info return mcpAllowed. See Authentication.
In MCP, get_community_settings shows assistant_access and update_community_settings accepts assistant_members, assistant_staff and assistant_admins (owner only).

8 octobre 2026

2026-10-08T23:59:59-03:00

Today's highlights:

Refunds from Monetization: the community refunds a buyer from the Sales tab, without waiting on the Memberfy team, and chooses whether they keep access.
Payouts that go to the bank right away: a payout goes to the bank the moment it's requested, with no manual approval, and the account receives exactly the amount requested.
The whole sale, with its timeline: the Sales tab shows one line per sale with its status, and each sale opens into a detail with everything that happened to it, in order.
Refunding part of a sale: on card and PIX, the community returns just part of the amount, as many times as needed, up to the total.
The Store in three sections: the storefront shows products, plans and add-ons, a plan can be link only, and a product opens into details with the Buy button.

Then come the improvements and the fixes. At the end, separately, what matters to developers.

Today's changes are for communities that sell in reais (communities in Brazil). Selling and paying out in dollars is still on its way.

Refunds from Monetization

What it is. The new Sales tab in Monetization lists every purchase in the community (one-time products, plans and add-ons) with the buyer, the amount, the net, the payment method and the refund status. The Refund button lives there. In the dialog, you say whether the buyer keeps or loses access, and Memberfy returns the money.

Why it matters. Before, returning a sale meant writing to the Memberfy team and waiting. Now the owner, the admin and finance refund right away, and decide on access at the same time: keep it for a discount agreed after the purchase, or remove it when someone gives up.

Keep or revoke access. On a one-time product or add-on, revoking removes access to the product. On a subscription, revoking cancels the subscription right away, and the dialog warns you before you confirm. Even with access kept, the purchase shows as Refunded, with the amount and the date.
On card and PIX, Memberfy returns the money through the same payment method. The platform fee goes back too, in proportion to the amount returned, and the community only returns the part it received. You can return the whole amount or just part of it (see Refunding part of a sale).
A refund that waits for balance. If the community's receiving account doesn't have the balance for its part yet, the refund stays Pending: waiting for balance and goes out on its own when balance comes in, in order of arrival. The access choice applies right away, and the amount is reserved: it isn't available for payout.
Boleto returned directly. A paid boleto isn't returned by the payment provider. The community returns the money directly to the buyer, by PIX or bank transfer, and records the return in the same dialog (it can be just part of it). Nothing leaves the community's balance and the platform fee doesn't come back.
The buyer gets an e-mail with the amount and whether access continues; the community gets a refund notice.

Where it is. Monetization › Sales, on the purchase's row. For a subscription, also under Members › Subscriptions › View details › Charge history, next to each paid charge.

How to start.

In Monetization › Sales, find the purchase by the buyer's name or e-mail and click Refund.
Under What about access?, choose Keep access or Revoke access and, if you like, write the reason.
Click Refund R$ …. On a boleto, check I already returned it to the buyer, fill in the amount and the date, and click Record return of R$ ….

Example. Maria bought the R$ 297 course by PIX and you agreed on a discount after the purchase. You refund it keeping access: the R$ 297.00 goes back to her by PIX, she stays in the course, and the sale shows as Refunded in the Sales tab.

The refund dialog on a subscription.

See Sales and Refunds and disputes.

Through the assistant. The same works in a conversation with Claude or ChatGPT: "Refund maria@memberfy.net's course purchase. She keeps access." The assistant finds the purchase, asks whether access continues and only refunds after your yes to a summary. There's also the ready-made recipe Refund a buyer. See Recipes.

Payouts that go to the bank right away

What it is. When an owner or admin confirms a payout, Memberfy sends the transfer to the bank at that moment, with no manual approval from anyone. The credit is expected the next business day.

Why it matters. Before, the request stayed Pending until the Memberfy team made the transfer by hand. Now the money leaves when you ask, and the history shows the real state: Processing until the bank confirms, Completed when the credit lands, or Failed, with the reason.

The account receives exactly the amount requested. The payout fee comes out of the balance, on top of the amount.
The maximum comes already worked out. The dialog shows what's available, the maximum (already without the fee and without what's reserved for refunds) and the minimum. The Withdraw the maximum button fills in the amount.
If the bank refuses it, the payout ends up Failed, the amount and the fee go back to the balance, and the history gives the reason. Once the account is fixed, just request it again.

Where it is. Monetization › Dashboard › Request Payout. The history is under Monetization › Payments › Payout history.

How to start.

In Monetization › Dashboard, click Request Payout.
Type the amount under How much you want to receive or click Withdraw the maximum, and check the fee and what leaves the balance.
Click Confirm payout.

Example. With R$ 1,000.00 available, the maximum is R$ 996.33: the account receives the full R$ 996.33 the next business day, and R$ 1,000.00 leaves the balance.

See Payouts.

The whole sale, with its timeline

What it is. The Sales tab now shows one line per sale, with the buyer, the product, the Status, the amount and the net, the payment and the date. Each sale opens into a detail: the summary, the Refund button and the timeline, with the payment, the balance release, the reserve, each step of a refund and the e-mails the buyer received.

Why it matters. Before, to understand what had happened to a purchase you had to piece together the list, the refund history and the statement. Now the answer to "what happened to Maria's purchase?" is on one screen.

The status, in a word. Paid, Processing, Waiting for balance, Refunded, Partially refunded, Returned directly, Disputed, Awaiting payment, Failed… Hover to see a refund's amount, date and access.
The Status filter uses the same names as the column and replaces the old filters.
The ⋮ menu on each line leads to View details and, while there is something left to return, to Refund. Clicking the line also opens the detail.

Where it is. Monetization › Sales.

How to start.

In Monetization › Sales, search for the buyer by name or e-mail.
Click the sale (or ⋮ › View details).
Read the timeline from top to bottom; a future date is when something will still be released.

Example. Maria asks when the money from her purchase reaches the community. In the detail, the timeline shows the PIX payment on 10/8, the release for payout on 11/7 and the 4% reserve coming back on 12/7, with the scheduled badge on what hasn't happened yet.

See Sales.

Refunding part of a sale

What it is. On card and PIX, a refund can be part of the amount: from R$ 0.01 up to what can still be refunded. A purchase accepts several partial refunds, up to the total. And in an order with a plan and add-ons paid together, each purchase is refunded on its own.

Why it matters. Before, on card and PIX only the whole remainder of the charge could be refunded, and a purchase that shared its charge with others wasn't refunded through Memberfy. Now a discount agreed after the purchase, or returning just one add-on, goes through the Sales tab itself.

The platform fee goes back in the same proportion as the amount returned, and only the community's share leaves the balance.
A partial refund usually stays Processing for a few minutes while the reversal is confirmed; the status updates on its own.

Where it is. Monetization › Sales, under Refund, in the amount field.

How to start.

In Monetization › Sales, open the sale and click Refund.
Change the amount to what you want to return and choose whether access continues.
Confirm. The Refund button stays on the sale for what's left.

Example. From a R$ 197.00 PIX sale, the community returns only R$ 50.00, a discount agreed with the buyer. Access continues, and the sale shows as Partially refunded.

See Refunds and disputes.

The Store in three sections

What it is. The Store now sells by plans. The storefront is organized into up to three sections, in this order: Products (the one-off ones), Plans (each plan once, with the "from" lowest price) and Add-ons. An empty section doesn't show. Clicking a product opens its details, with Buy and Copy link, and plans gained the Public or Link only visibility.

Why it matters. Before, a billing option (Monthly, Annual) showed in the Store as if it were a standalone product, and an add-on could be bought alone, outside the plan. Now the person picks the plan, then the option, and an add-on is only bought through its plan. And you can have a plan that shows up nowhere and only opens through a link: for an invitation, a partner, a cohort.

Each add-on shows the viewer's state: Add (summed to your subscription, at the prorated amount), You already have it, Available on the X plan with Upgrade, or Subscribe to the X plan to add it.
The storefront picker (Choose products) also has the three groups: picking a plan picks all of its options, and a billing option is never picked on its own.
Link only hides, it doesn't protect. The plan disappears from the pricing page, the Store and the picker, but whoever has the address (/pricing/<address>) buys normally.
Every billing option belongs to a plan. An option without a plan shows in Monetization › Options with the No plan badge, and isn't for sale. Deleting a plan that still has options is refused, with their names.
Stock with reservation. On a product with Control Stock?, the unit is reserved on the order. Once they run out, Sold out shows in the Store, in the direct-link catalog and in the purchase window, in place of the Buy button, and checkout refuses. A boleto holds the unit until it's due; the unit comes back if the payment fails, if the PIX or the boleto expires, or if a refund removes access. Partial refunds and chargebacks don't return it. In Monetization › Products, admins see "N available" or Sold out. See Products.

Where it is. The Store is the space you created; the plan's visibility is in Monetization › Plans, in the Plan visibility field.

How to start.

In Monetization › Plans, edit a plan and choose Link only under Plan visibility, if you want to hide it. Copy the Plan link.
Open the Store and click Choose products. With Chosen products, check what the store sells, in the three groups.
Open the Store as a member: click a product to see its details, then Buy.

Example. A school sells the one-off course Excel from Scratch, the Student plan (Monthly and Annual) and the Group mentoring add-on. The Store shows the course under Products, the plan Student, from R$ 49 under Plans and the mentoring under Add-ons, which, for someone who doesn't subscribe, says Subscribe to the Student plan to add it. The March cohort plan, just for that cohort, is Link only and goes out by email.

See Store, Plans and Add-ons.

Other news

Creating a space asks only what changes the space. Before, some modules asked for options that changed nothing (Feed post types, Gallery layout, Ranking options, course sequence). Now each module asks only what counts: Link asks for the address, Certificates asks Who issues, Store asks for the storefront and Call for papers asks how many calls. If a setting isn't saved, the space already exists and the window offers Try again, without creating a second space. See Spaces.
Who can open a call, on screen. In a call space with Several calls, creating and editing the space now show Who can open a call: Staff (the default), Admins or Members. Before, this rule could only be changed through the assistant. See Call for papers.
The storefront when creating a Store. Step 3 of creating a Store, Storefront, chooses what it shows: All active products (the default) or Chosen products. Before, the store started out showing everything, and the choice came later. See Store.
Counters in the Help Center. The MCP and API home pages show how many tools and recipes the assistant has and how many endpoints the API has, with the total in each of the same 8 product areas and a link to each page. The numbers come from Memberfy itself, in production, every time the Help Center is published.
Sale times in the community's time zone, and View subscription. The sales list, the detail and the timeline show times in the community's time zone (that of the business information's country), with a note saying which one, instead of the viewer's time zone. A refund waiting for balance shows its Last attempt. And on a plan sale, the View subscription button opens the subscription in Members › Subscriptions. See Sales.
The community's time zone in subscriptions, the statement and payouts too. Subscription, statement and payout dates and times follow the community's time zone, not the viewer's. See Balance and statement and Payouts.
The assistant's tools on the website. The MCP page on the Memberfy website shows the 207 tools in the same 8 areas as the Help Center, and the 4% reserve for 60 days on every sale.
Images on products and plans, through the assistant. create_product and update_product take the product's banner (16:9) and featured image (1:1), by link or file; create_plan and update_plan send the images to every option of the plan (a plan has no image of its own). An invalid image changes nothing: the assistant stops and explains. Details in Tools · Sales and plans.

Improvements

Sales that switch on and off right away. When the payout registration changes status, the community's sales switch on or off at the same moment. Before, the change could take up to 1 hour to apply. See Business information and payout account.
Clearer declined-payment messages. The messages the buyer sees when a payment is declined are clearer. See Checkout.
A 30-day release period, for every method. Before, PIX was available on the day of payment, boleto 1 day after clearing and card after 30 days. Now every sale becomes available for payout 30 days after payment, with any method, and each sale shows the date under Releases on. On a card sale in installments, each installment is released on its own date. See Balance and statement.
A 4% reserve for 60 days, with every payment method. Before, only card had a reserve, held for 30 days. Now 4% of the gross amount of each sale, by card, PIX or boleto, is held for 60 days to cover disputes and goes back to available on its date. See Balance and statement.
The balance shows where each amount comes from. The Dashboard separates Pending (sales before their release date, with the next release), Retained (the dispute reserve) and Available for Payout. When a refund or a dispute takes available below zero, the amount owed appears, and it comes out of the next sales released. Before, a negative balance showed as zero.
A R$ 10.00 minimum payout. A payout below that is refused, and the dialog shows the minimum before you type the amount. See Payouts.
A R$ 3.67 payout fee. Memberfy's fee per payout is still R$ 3.67, charged on top of the amount requested: the account receives the full amount. The dialog shows the fee and the total that leaves the balance before you confirm. See Platform fee.
No advances and no automatic transfers. Money only leaves when an owner or admin requests a payout. The Automatic Transfers section is gone from Settings › Payout Settings, and the Transfer Interval line is gone from Monetization › Payments. See Business information and payout account.
Clearer payout registration texts. The messages and e-mails about the payout registration (the review, the activation, sales switched off and refused details) are more direct and no longer name the payment provider. In the sales-switched-off e-mail, the field is now called Payout status. See Business information and payout account.
New security controls. We applied new security controls to Memberfy. Nothing changes in how you use it: everyone keeps seeing and doing the same as before.
The plan window in three columns. On wide screens, creating or editing a plan shows three columns side by side: the plan's identity, the benefits and the billing options, with the add-ons below across the full width. On a phone it stays one column. See Plans.

Fixes

An add-on bought alone. Before, anyone who had the plan could buy an add-on as a loose subscription, with its own cycle and billing date. Now checkout refuses it for everyone, with a message that shows the way: together with the plan or summed to the current subscription. See Add-ons.
The total balance. Before, the Total balance on the Dashboard could add up the gross and the net of the same sale and show more than the community had. Now it adds up pending, retained and available, and matches the statement.
Card payments. A change yesterday left cards unavailable at checkout for every community; we caught it and they were working again the same day.

For developers

This part is for those who integrate Memberfy through code. To use what's above, none of this is needed.

API

Sales and refunds. Three new routes, for the X-CommunityId community, for owner, admin and finance: GET /api/manage/purchases (the sales, with the status, productId, paymentMethod, refunded, from, to and search filters), GET /api/manage/purchases/{purchaseId} (one sale, with all its refunds) and POST /api/manage/purchases/{purchaseId}/refunds (refunds it, with access KEEP or REVOKE, a required idempotencyKey and, on boleto, settledOutside). Each sale has refundedAmount, refundableAmount, refundMethod and refundBlockedReason. See Sales and Responses and errors.
New balance. GET /api/payouts/balance now returns pending (before, always zero), owed, withdrawableBalance, maxPayoutAmount, minPayoutAmount, pendingRefunds and balances[], one line per currency, with ?currency= to choose the currency of the payout calculation. available can be negative. Statement entries have availableAt, one per installment on a card sale in installments, and accept the currency filter.
Status and timeline. GET /api/manage/purchases accepts the situation filter (one or more) and each sale has situation; GET /api/manage/purchases/{purchaseId} has the timeline, with each event already translated by Accept-Language.
Store in three groups. GET /api/storefront/spaces/{id}/products returns products, plans (each plan once, with fromPrice) and addOns (with availability owned | add | upgrade | subscribe), plus notices for whoever manages it. PUT gains planIds and refuses a lone billing option in productIds.
Plan and option always together. POST/PUT /api/products refuse a billing option without a plan (400 subscriptionGroupIds); a PUT /api/subscription-groups/{id} that would leave an option without a plan answers 400 productIds with the names; DELETE with live options refuses and names them. Plans gain visibility (public | link_only), the public list hides link_only (except the viewer's own plan) and GET /api/checkout/subscription-groups/{slug} opens the plan by its address. POST /api/checkout and /checkout/calculate-price refuse an add-on as the main product (400 productId) and an option outside every plan.
Partial refunds. POST /api/manage/purchases/{purchaseId}/refunds accepts amount (default: the remainder) on card, PIX and boleto, and refunds one purchase on its own in an order with several.
Payouts. POST /api/payouts answers 201 with the payout in the state it ended up in (PROCESSING or FAILED, with failureCode and failureMessage) and refuses with 400 an amount below the minimum or above the maximum. See Payouts.

MCP: technical details

Three new Finance tools: 207 in total. list_purchases and get_purchase (read-only) and refund_purchase (kind: money, asks to confirm; on boleto, settled_outside records the money returned directly). A purchase that can't be refunded through Memberfy yet is refused before the summary, with the reason in refund_blocked. New prompt Refund a buyer (refund_buyer): 10 prompts in all. By role: owner and admin, 207; finance, 103. See Tools · Finance.
Status, timeline and partial refunds. list_purchases accepts situation and returns situation_label; get_purchase has the timeline; refund_purchase accepts amount to return just part of it on card and PIX.
Images on products and plans. create_product and update_product accept image_url/image_base64 (+ image_type) and featured_image_url/featured_image_base64 (+ featured_image_type), sent through POST /api/upload/product/{id}/banner and /featured; update_product gains remove_banner and remove_featured_image. In create_plan the top-level images go to every option (each option can bring its own); in update_plan, to every option of the plan. On failure: the single-item tools check the image before changing anything (create_product undoes the product if the upload fails after creating); create_plan never rolls back for an image and returns the reason in warnings; update_plan checks first and reports a refused upload for one option in warnings. The audit log now keeps only the size of *_base64 arguments. See Tools · Sales and plans.
get_balance returns one line per currency, with pending and its release dates, retained with its return date, owed, the withdrawable amount, the fee, the maximum, the minimum and pending_refunds. list_ledger_entries has each entry's releases on date and accepts currency. request_payout refuses on the first call an amount below the minimum or above the maximum, and the result shows the payout's real state. community_overview gained money_by_currency.
Bulk editing and a Store with plans. update_products and update_plans (up to 20 items; the price asks for confirmation, images go by link or file) are two new tools in Sales and plans: 209 in total, 27 in Sales and plans. create_product accepts short_description. update_storefront accepts plan_ids (whole plans; a billing option is still refused in product_ids), create_plan and update_plan accept visibility (public or link_only) and list_storefront_products returns the three groups, with the add-on's state for whoever asks and the suggested next step. See Tools · Sales and plans.
Stock in the MCP. create_product, update_product and update_products accept has_stock and stock_quantity (what's available right now; 0 is sold out); list_products returns availability and sold_out, and the Store (get_storefront, list_storefront_products) returns sold_out, without the count. A sold-out add-on gets no purchase next step.

API: stock

POST /api/checkout for a one-off product with stock takes the unit on the order; with no unit left, it answers 409 Sold out (param: productId), and an open PIX or boleto for the same product answers 409 with the open payment in data.openPayment. hasStock without stockQuantity and hasStock on a subscription answer 400. GET /api/checkout/products returns soldOut. The management lists of plans and products (GET /api/subscription-groups, GET /api/products) belong to the owner, the admin and finance; other roles read only what is public. See Responses and errors.

7 octobre 2026

2026-10-07T23:59:59-03:00

Today's highlights:

Change plan: subscribers move to another plan, or from monthly to yearly, on their own, in Billing. Before confirming, they see how much they pay now, the next charge and what happens to extensions, the contract and the coupon. The same can be asked of the assistant.
Store: a new type of space that shows the community's products and sells them right there, with every active product or only the ones you choose, in the order you want.

Then come the other news, the improvements and the fixes. At the end, separately, what matters to developers.

Change plan

What it is. The subscriber moves their own subscription to another option: to a bigger plan, to a smaller one or to another billing interval. The subscription changes in place, with the same history; there's no need to cancel one and subscribe to another.

Why it matters. Before, the Change plan button only took people to the community's plans: to switch, they subscribed to the new plan and canceled the old one, or wrote to the team. Now they sort it out on their own, and the community doesn't lose someone who just wanted to move up or down a plan.

To a more expensive plan, with the same billing interval, the switch takes effect right away: we charge now, to the default saved card, only the difference prorated for the days left until renewal (with the platform fee, when the buyer pays it, and in installments, when the yearly option allows). If the difference is too small (fewer than 3 days or less than US$ 10), it switches without charging. The next charge comes at the new price, on the same date.
To a cheaper plan, one at the same price or one with another billing interval, or when an extension would end, the switch is scheduled for the end of the period already paid. The dialog shows the date and the reason.
Before confirming, the person sees the amount now, the next charge and its total, the extensions that continue (with the new price) or end, the contract kept or new, the coupon that stops applying and the scheduled switch that will be replaced.
Undo. A scheduled switch shows on the card as Scheduled change, with Undo, until the PIX or boleto for that period's renewal is generated.

Where it is. Billing, on the plan card, Change plan.

How to start.

In Billing, click Change plan. The list has the options from the pricing page, including those with the other billing interval.
Choose the option and read the summary.
Confirm with Pay US$ … and switch (takes effect now) or Schedule change.

Example. Ana subscribes to Growth Monthly (US$ 25) and, mid-month, moves to Business Monthly (US$ 89). There are 15 days left until renewal: she pays US$ 32.00 now on the saved card and, from the renewal on, US$ 89 a month. Diego, on the same Growth Monthly, picks Growth Annual: since the billing interval changes, the switch is scheduled for the end of the month already paid, and the charge on that date already comes at the yearly price.

Some rules: with no saved card, a switch that takes effect now can't be confirmed (Add card opens the form on the same page); with the card declined or payment down, nothing changes and nothing is charged; you can't switch during the free trial, with the subscription past due, with a scheduled cancellation, on a complimentary subscription or with the renewal open. Only the subscriber changes their own plan. See Change plan.

Through the assistant. The same works in a conversation with Claude or ChatGPT: "How much does it cost to move to Growth yearly?", "Change my plan to Growth monthly", "Do I have a plan change scheduled?", "Undo the switch". The plan can be given by name, by the pricing page link or by id. Before charging, the assistant shows the same summary and waits for your yes. There's also the ready-made prompt Change my plan. See Tools · Subscriptions.

Store

What it is. A new type of space, created in Add Space, that shows the community's products for sale: standalone courses, tickets, materials, extensions. Whoever sees the store clicks the product and pays in a window, with the payment method, the platform fee (when the buyer pays it) and the total, without leaving the community.

Why it matters. Before, a one-time product was only sold through its direct link, outside the community menu. Now it has a storefront inside the community, with the same visibility rules as any space: a subscribers' store only appears to subscribers, and anyone without access sees "This space is restricted".

Two modes. All active products shows every active product in the community, and a new product joins on its own once it's activated. Chosen products shows only the checked ones, in the order they were checked.
Buying even without a direct link. Whoever sees the store can buy what it shows, even if the product's direct link is off.
Only the owner and the admin configure the store.

Where it is. In the community menu, Add Space › Store. Then, in the store itself, Choose products.

How to start.

In Add Space, choose Store, give it a title, pick the visibility and click Create Space.
In the store, click Choose products and choose All active products or Chosen products.
With Chosen products, check the products in the order they should appear and click Save.

Example. An Extensions store, visible only to Subscribers, in Chosen products mode, with the Planning & HR extension first and the Coworking one second. Subscribers buy the extension right there; non-subscribers don't see the store.

The store seen by the owner.

See Store.

What's new

The assistant does 16 more things. Talking to Claude or ChatGPT, you can now react to a comment, see the home page numbers and recommendations, the ranking page and your points history, recalculate a member's points, see the event categories (and pick one when creating an event), see a Store's products, follow a batch of certificates being issued, see and edit profiles (yours and, for admins, the members'), see your subscription's charges, the community's fee and how many community e-mails were delivered and opened. For example: "Why are my points like this?", "Did the invitations arrive?", "What fee do I pay?". See Tools and Recipes.
Sell a one-time product by direct link. In the product form, under Monetization › Products, the new Sell by direct link switch puts the product in the community's product catalog and gives it a purchase link, with a Copy link button, to share wherever you like. The link only sells while the product is Active; when it's off, the product leaves the catalog and anyone opening the link is told it is no longer available. See Sell by direct link.
Exclusive access screen, with the way to subscribe or buy. Before, someone opening a locked space saw neither the content nor why. Now they see This space is exclusive, with the reason (it requires a plan or a purchase) and a See plans or See products button; anyone not signed in sees Sign in. A link to a space the person can't see shows This space is restricted. See The exclusive access screen.
New app version notice. When a new version of Memberfy comes out, "A new version of the app is available" appears at the top, with a Reload button (or Later). If you have typed something and not saved it, the notice asks before reloading, so nothing is lost.
The Memberfy website, now in English. The Memberfy website is now available in English, Spanish, Italian and German, alongside Portuguese. A language switcher at the top changes the language and keeps you on the same page. Links from this help center to the website now open in your language.
Memberfy's prices in US dollars. In English, Spanish, Italian and German, the website's pricing page now shows Memberfy's prices in US dollars (US$): plans from US$ 10 to US$ 99 a month on the annual plan (US$ 13 to US$ 129 monthly), member packs, extensions and fees. In Brazilian Portuguese they stay in reais. Nothing changes in what your community sells: your members still pay in Brazilian reais.
Comparison with the best-known platforms, and a clearer description of live streaming. In English, Spanish, Italian and German, the website's pages that compare Memberfy, such as the table on the pricing page, now compare it with Circle, Skool and Mighty Networks, and the page comparing Memberfy with Circle was rewritten for readers outside Brazil: price, fee per sale, payment processing and team. In every language, the website now describes event live streaming precisely: a YouTube, Vimeo or Mux stream on the event page.
Country selector with flags on the website and the Help Center, and a version for Portugal. The selector at the top of the website and of the Help Center now lists countries, each with its flag and name (Brasil, Portugal, México, Schweiz…), and the website has a version for Portugal. In the Help Center, the link to the website opens your country's version.

Improvements

A product with subscribers is no longer deleted by mistake. Before, deleting a product that still had an active subscription or a purchase with access took it off the list, but the subscription kept renewing. Now the deletion is refused: the window shows "This product cannot be deleted", how many subscriptions and purchases hold it, and offers Unpublish, which takes the product off sale and keeps access for those who already have it. See Products.
Bank account checked right away. Before, a bank account in someone else's name (a partner, for example) was only refused long after it was sent. Now the Payment Settings tab warns on save, under the document field, that the account must have the same holder as the Business Information. See Business information.
New security controls. We applied new security controls across Memberfy. Nothing changes in use: everyone keeps seeing and doing the same as before.
Posts and events open from the Logs. Before, in Members › Logs, only subscriptions and courses were clickable. Now a post or event row opens the item itself, in the space it lives in. See Activity logs.
The help center loads in one piece, even on a slow connection. Before, on a slow connection, the help center looked broken for a few seconds: text changed size and position several times while the fonts arrived, one at a time. Now the fonts come from the help center itself, and text appears at its final size and position from the first moment.
We explain refunds and disputes better. The new article Refunds and disputes says it plainly: in a refund, the buyer gets back the full amount they paid, the platform fee is returned along with it, and the community only returns the part it received. In a dispute of a sale in installments, the community returns everything, interest included. With examples in numbers.
A cleaner header on phones. Before, on a phone, your name competed for room with the community's name in the app header. Now, on phones, the header shows only your photo.
Payment Settings in your language, and fitting on phones. Before, the Settings › Payment Settings tab (bank details and payouts) had text only in Portuguese, and on phones the buttons ran off the screen. Now the tab is translated into the app's 10 languages, and the buttons stack on phones. See Payouts.
Product status in words when deleting. Before, the delete window for a product or a plan showed the status as code (ACTIVE, DRAFT). Now it shows Active, Draft or Inactive.
Website addresses in each country's language. The addresses of the website's pages in other languages are now in each country's language: the pricing page in English, for example, is now memberfy.net/en-us/pricing. The Help Center's links already go to the new addresses.

Fixes

Event e-mails in the community's language. Before, the event registration, reminder, live stream and cancellation e-mails arrived in English for communities in German, Spanish, Italian and European Portuguese. Now they come in each one's language.
Billing history. Before, a paid charge showed "Pending" next to "Paid on…". Now it only shows what applies.
Feed with a course without tags. Before, the feed stopped loading when it showed a course created without tags. Now it opens normally.
Translated validation messages. Before, some required or invalid field messages reached communities in German, Spanish and Italian in English. Now they come in the community's language.

For developers

This part is for anyone integrating with Memberfy through code. You don't need any of it to use what's above.

API

Preview a plan change. POST /api/subscriptions/{id}/change-tier/quote (new) returns, with no side effect, what change-tier would do: whether it takes effect now (IMMEDIATE) or is scheduled (SCHEDULED) and why, the amount now, the possible installments, the next charge and its total, the extensions, the contract, the coupon and the scheduled change that would be replaced.
change-tier charges the difference. POST /api/subscriptions/{id}/change-tier now accepts paymentMethodId (the saved card; default: the default card) and installments, and answers 200. It refuses with 400 when there's no saved card and 409 when the renewal is open, and returns the payment error when the card is declined or processing doesn't respond; in those cases nothing changes.
scheduledChange now comes on GET /api/subscriptions/me and on the subscription detail (null when no change is scheduled). The scheduled change is read and undone with GET and DELETE /api/subscriptions/{id}/scheduled-change.
target.spaceId in activity logs. GET /api/activity-logs returns the item's spaceId in target when it is content, event, status or course (null if the item was deleted or isn't in a space). New optional field; nothing changed for other types.
SDK cache. /sdk.js and /sdk.mjs are now sent with Cache-Control: max-age=60, so a new deploy reaches SDK users within a minute.

See the API reference.

MCP: technical details

Plan change. Four new tools in Subscriptions, in the part about your own subscription, for any role, only on your own subscription: quote_plan_change (read-only), change_my_plan (kind: money, asks to confirm; a switch that takes effect now charges the saved card), get_scheduled_plan_change (read-only) and cancel_scheduled_plan_change (asks to confirm). The target goes in target: the plan name with billing ("Growth yearly"), the /pricing/{plan}/{option} link or the option id. New prompt Change my plan (change_plan). manage_my_subscription still covers cancel, pause, resume and reactivate. See Tools · Subscriptions.
16 new tools: 204 in total. react_to_comment, get_feed_stats, get_feed_recommendations, get_ranking_dashboard, list_my_points_history, recalculate_member_points, list_event_categories (and category in create_event and update_event), list_storefront_products, list_certificate_fonts, get_certificate_batch, get_member, update_member_profile, update_my_profile, list_my_subscription_charges, get_community_fees and get_email_stats. None asks for confirmation. By role: owner and admin, 204; moderator, 123; finance, 100; member, 86. See Tools.

6 octobre 2026

2026-10-06T23:59:59-03:00

A lot shipped at once today, and most of it changes the daily routine of whoever runs a community. The six highlights:

AI assistants: connect Claude, ChatGPT or Cursor and just say what you need, like building a course, opening a call for papers, inviting a cohort or checking this month's sales. The assistant covers every module of the community.
Set up monetization before approval: products, plans, options, coupons and offers start as drafts while your business information is under review; publishing and selling wait for approval.
Certificates: a new space for issuing certificates to a whole cohort, with a PDF, a verification page and an Add to LinkedIn button.
Subscription management: the list of who subscribes to what, with your team's actions on each subscription, now under Members.
Installments with interest and Pay now: the annual plan in up to 12 card installments, and late payers settle up without subscribing again.
My Account in tabs: profile, password, communities, assistants and payments, each in its own place.

After them come the other new features (among them the Activity logs, with who did what in the community, and the Gamification tab, to decide how much each action is worth), improvements and fixes, each with what changes for you. At the end, set apart, is what matters to developers, including a change to the API paths that requires updating integrations.

AI assistants: your community in a conversation

What it is. Memberfy now works inside Claude, ChatGPT, Claude Code and Cursor. You connect the assistant once, and from then on you write what you want the way you'd ask someone on your team. The assistant does the work in your community and tells you what it did.

Why it matters. Plenty of tasks that take several screens today become a single request: building a course with modules and lessons, creating this month's event with tickets, opening the conference's call for papers with tracks and a committee, inviting a cohort, issuing certificates, putting together the monthly report with a chart. The assistant does what the app lets you do, in every module: reorganizing sections and spaces, moving a post, editing modules and lessons, starting an event's live stream, editing coupons and offers. And members use it too: proposing a talk, enrolling in a course, RSVPing, viewing or canceling their own subscription. The assistant acts with your role and in one community only. Anything that touches money or deletes something waits for your "yes" to a summary before it happens; everything else happens right away, like a click in the dashboard. And you can disconnect it whenever you like.

Where to find it. In the sidebar, under your name, My Account › AI assistants. Owners and admins also find it in Settings › AI assistants, along with the list of every assistant connected to the community.

How to start.

In My Account › AI assistants, click Copy next to MCP server address. The steps for each assistant are right below it.
In Claude, open Settings › Connectors › Add custom connector, name it Memberfy, paste the address, then click Add and Connect.
In the Memberfy window that opens, pick the community and click Allow. To check, ask: "Which community are you connected to, and with what role?"

The server address with the Copy button, and the steps to connect Claude, ChatGPT, Claude Code and Cursor (the screen in Portuguese).

Requests you can paste into Claude.

"Build a 4-module course on Excel for beginners, with 3 lessons in each, and a US$ 97 product. Keep everything as a draft." The course, modules and lessons appear in your courses space; you add each lesson's content from the dashboard.
"Invite these 30 people to the Cohort 3 group: ana@memberfy.net, bruno@memberfy.net, …" The assistant shows you the list first and, after your ok, reports who got the invite, person by person.
"How did sales do this month compared with last month? Make a chart." The numbers come with the chart right in the conversation.
"Issue the completion certificate to the September cohort group." Before issuing, it does a dry run and tells you how many people will get one and who is left out.
"Open the call for papers for Congress 2027, with the tracks Product, Data and Career and proposals until November 30. Make Ana and Bruno reviewers for Data and show me before publishing." The call appears as a draft in the Call for papers space, with the tracks and the committee; you publish it when you approve.

In Claude, eight common requests come ready-made in the + button of the message box, under Connectors › Memberfy: the monthly report, inviting a cohort, issuing certificates, a certificate template with your brand's artwork, creating a course, creating an event, opening a call for papers and reviewing proposals.

See MCP overview, Connect Claude, Connect ChatGPT, Recipes and Create a call for papers.

Set up monetization before approval

What it is. Products, billing options, plans, add-ons, coupons and downsell offers can be created and configured before the community's Business Information is approved. Everything starts as Draft. What waits for approval is going live: publishing (the Active status) and selling.

Why it matters. The Business Information review takes up to 7 business days. Before, that was dead time: you couldn't even create a product. Now you use the review to set up your plans, prices and coupons, and on approval day you just publish.

Where to find it. The Business Information is under Settings › Business Information. Products and plans are under Monetization › Products, Options and Plans.

How to start.

In Settings › Business Information, fill it in and click Submit for Review.
While the review runs, create the billing options, the plan, the add-ons and the coupons. They stay as Draft.
When the status changes to Approved, switch the options and products to Active.

Example. Escola Excel submits its Business Information on a Monday and, that same afternoon, sets up the Student plan with the US$ 15 monthly and the US$ 144 annual options, the Mentoring add-on and the LAUNCH coupon. Trying to publish before approval shows: "To publish and start selling, the community needs approved business information. Meanwhile you can create and configure everything as a draft." Approved the following week, the school publishes the options and starts selling the same day.

Good to know.

Editing approved Business Information pauses sales. It goes back to review, and checkout refuses new purchases until it's approved again. Only edit it when you need to, and submit it for review right away.
The currency comes from the country. A draft's price is in the currency of the Business Information's country (or in reais, without it). If the community is approved in another country, adjust the currency and the price before publishing.
The same through the AI assistant. If you ask for a course, an event or a plan already published and the community isn't approved yet, the assistant creates everything as a draft, undoes nothing and tells you the next step is the Business Information.
The dashboard tells you where things stand. While the community can't sell yet, the top of Monetization shows the situation (not submitted, under review with the expected answer date, rejected with the reason, or sales suspended after an edit) and the Open Business Information button.
Nothing is lost if you try to publish early. Choosing Active without approval saves the rest of the form and keeps the product as a draft, with the notice "Your other changes were saved." With approval, choosing Active on creation publishes right away.

See Business information, Products and Plans.

Certificates

What it is. A new space module for issuing completion, attendance or training certificates. Each person gets the certificate as a PDF and as an image for social media, with a code and a QR that anyone can check on a public page.

Why it matters. A certificate is no longer a file you make by hand, one at a time. You issue it to the whole cohort at once, members get it by email and add it to LinkedIn in one click, and anyone who sees it can confirm it's genuine.

Where to find it. In the sidebar, Add Space under a section, then the Certificates module. Inside the space, Manage certificates shows the Issued certificates and the Templates.

How to start.

Create the space with the Certificates module and choose Who issues: admins only, or the whole team.
In Manage certificates › New template, choose Platform design (your community's logo and colors; you only fill in the text) or Your own artwork (your designer's image, where you mark where the name, date and QR go). Then Activate it.
Click Issue certificate, pick the template and, under Recipients, choose members, groups or tags. Confirm.

Example. The September cohort of your Excel from Scratch course has finished. You issue the Certificate of completion to the September cohort group, with 8 hours of coursework: all 37 people get the email, download the PDF and post it on LinkedIn with the verification link. If someone was included by mistake, the certificate can be revoked or reissued.

The member's certificate: the PDF, the image, LinkedIn, the verification link and the social media images (the screen in Portuguese).

See Certificates.

Subscription management

What it is. A new tab in Members with every subscription in your community: who subscribes to what, how much they pay, when the next charge is and what state it's in.

Why it matters. Your team can now handle on screen what used to have no place to be done: spotting who's past due and sending them a payment link, giving a discount for a few months, extending the period for someone who had a problem, giving a speaker a complimentary plan. Every action asks for confirmation and is logged, with who did it and when.

Where to find it. In Members › Subscriptions. Owners, admins and the finance role have access; finance gets there through the Members menu item, which opens straight on that tab for them. Anyone who saved the old Monetization link lands in the new place.

How to start.

Open Members › Subscriptions and use the filters: Past due, Canceling, the plan or the start date.
Click the row (or View details in the ⋮ menu) to open the subscription, with its charges, timeline and actions.
Pick the action: Send payment link, Apply discount, Extend period, Add add-on, Cancel subscription or Reactivate.

Example. A speaker from your conference will be part of the community until the end of the year. In New subscription, pick the person and the plan, choose Complimentary with an end date of December 31 and confirm: she sees the plan's spaces at no charge, and the complimentary subscription ends on its own. To send the list to your accountant, Export CSV.

Filters by status, plan and date, and each subscription with its amount, next charge and payment method (the screen in Portuguese).

See Subscription management.

Installments with interest and Pay now

Card installments, with interest

What it is. Buyers can split a card payment into up to 12 installments, with Memberfy's installment interest: 4.29% in total from 2 to 6 installments and 6.00% in total from 7 to 12. Paying in full, by PIX or by boleto, has no interest.

Why it matters. An annual plan fits more budgets, and you decide who pays the interest. By default it's the buyer, and you receive the same as a one-time payment. If you'd rather advertise "interest-free", the community absorbs the interest and the buyer pays only the list price.

Where to find it. In Monetization › Options (or Products): in the option's ⋮ menu, Edit, then the Payment & Pricing tab and the Who pays the installment interest? field.

How to start.

Open the billing option (the Annual one, for example) with Edit.
In the Payment & Pricing tab, choose Buyer or Organization under Who pays the installment interest?
Save and check your pricing page: the card shows the installment amount and the total.

Example. Growth Annual costs R$ 1,188.00. With the buyer paying the interest, the page shows "12× R$ 104.94 on your card (total R$ 1,259.28)", and you receive the same as a one-time sale. With the organization paying, the buyer pays 12× R$ 99.00, and the R$ 71.28 of interest comes out of what the community receives.

The installment with interest, the card total and the one-time price by PIX or boleto (the screen in Portuguese).

See Annual in installments.

Pay now

What it is. A button on the member's Billing page to pay a late renewal right away, with the saved card, another card, PIX or boleto.

Why it matters. Before, anyone who missed a renewal had to subscribe again: a new subscription was created and the old one was left hanging. Now the same subscription is brought up to date, with the same date, coupon and add-ons. You get the payment back without chasing it by hand.

Where to find it. For the member, in the sidebar under their name, Billing. The Pay now button only appears on a past-due subscription.

How to start. There's nothing to set up. When someone falls behind, send them the link with Send payment link in subscription management. The member:

Opens Billing and sees "The renewal was not paid. Pay to keep your access."
Clicks Pay now and chooses Saved card, Another card, PIX or Boleto.
Confirms. By card, the answer is immediate; by PIX or boleto, the page updates on its own when the payment comes in.

Example. A member's card expired and the Growth Monthly renewal failed. They get your link, open Billing, pay with a new card and, within the same minute, the subscription goes from Past due back to Active. The new card is saved for the next renewal.

See Pay now.

My Account in tabs

What it is. Your account page is now organized in five tabs: Profile, Security, Communities, AI assistants and Payments.

Why it matters. Everything has its place, and each tab has its own address, so you can send someone straight to it ("go to My Account › Security and change your password"). Changing your password is always at hand, and a wrong current password is flagged right in the form.

Where to find it. In the sidebar, under your name, My Account.

How to start.

Open My Account.
In Profile, adjust your name, photo and bio in the community.
In Security, change your password: at least 8 characters, with an uppercase letter, a lowercase letter and a number.

Example. A member asks where to change their password. Instead of explaining the way there, send them your community's address followed by /account?tab=security, and they land right on the tab.

See Account and profile.

More new features

The community's language. Before, only the Memberfy team could change the community's main language, which is the language of its emails. Now the owner and admins change it through the AI assistant ("change the community language to Mexican Spanish") or through the API. See Languages.
Renewal by PIX and boleto. Members who pay by PIX or boleto now get the renewal charge by email five days before it's due, and it also shows up on their Billing page. Fewer forgotten renewals, fewer lost subscribers. See Renewal.
Add-ons at checkout. Subscribers tick the extensions on the same page as the plan and pay for everything in one payment. Existing subscribers can add an extension later from Billing, with Add an extension. See Add-ons.
Last chance (downsell). Someone who skipped an add-on gets a discounted offer for it by email after paying. You set the discount and how long it lasts. See Downsell.
Annual in installments and contract length. The whole year in one purchase, in up to 12 card installments; and a monthly plan can have a minimum term, such as a 6-month contract. See Annual in installments and Contract length.
Coupons at checkout and on renewals. Buyers enter the code when they pay, and a "forever" or "for a few months" coupon keeps applying on renewals without you having to remember. See Coupons.
Copy the plan's link. In each plan's and option's menu, Copy link grabs the direct address of the pricing page, ready to paste on Instagram or WhatsApp. See Plans.
Activity logs in Members › Logs. Before, there was nowhere to see who did what. Now the owner and admins have a timeline with the team's actions on subscriptions, everything an AI assistant did in the community (connecting, disconnecting, each tool used and what was refused) and the member actions that earn points. You can filter by source, person and period, open the before → after of each action and send the filtered link to someone on the team. See Activity logs.
Gamification in the dashboard. Before, how much each action is worth could only be changed through the API. Now the owner and admins turn points on or off and change the value of each action (posting, commenting, completing a lesson, attending an event…) under Members › Gamification. The new value applies from the next action on, and points already earned don't change. See Gamification.

Improvements

Order page. Every payment now has its own page: it shows the PIX or boleto, confirms on its own when the payment comes in, and lets you cancel a PIX or boleto that won't be paid. The confirmation then shows the summary and what was unlocked, so buyers aren't left wondering. See Checkout.
Billing page redone. Members see everything about their subscription on the plan card: amount, next charge, add-ons and contract. The charge history now shows up, and they can cancel right there without contacting support. See Member billing.
A clearer statement. Each sale, payout or chargeback is now a single line, with how much it changed your balance. One click opens the line and shows what came in and each debit, such as the platform fee and installment interest. See Balance and statement.
Members and Monetization reorganized. People are now together: Members has the tabs Members, Subscriptions, Groups, Tags, Org chart, Gamification and Logs. Monetization kept the money: Dashboard, Payments, Products, Plans, Options, Coupons and Fees. Payout account is now called Payments, and Billing options became Options. See Manage members and Monetization overview.
The AI assistant asks less. Memberfy's two-step confirmation now covers only what touches money (coupons, prices, payouts, subscriptions, offers) and what deletes, removes, revokes or cancels. Inviting, changing roles, changing settings, issuing certificates and deciding proposals happen on the first request; before issuing certificates, the assistant does a dry run and shows who gets one. Claude keeps its own permission prompt, which you can set to "always allow" in the connector settings. See Money and confirmation.
The assistant writes with formatting. Posts, event descriptions, the call for papers text and the proposals the assistant writes reach the app with bold, italic, lists, links and subheadings, as if they had been written in the editor. See Markdown text.
CPF or CNPJ kept. Buyers used to type their tax ID on every purchase. Now it stays on their account and comes filled in next time. See Checkout.
Invite with a link to create a password. People invited without an account used to get a temporary password. Now they get a link, valid for 7 days, to create their own, and every invitee gets the email, bulk invites included. See Invite members.
Who can post. Each space's rule (Anyone, Staff or Admins) wasn't always saved. Now it's stored and enforced on every post. See Spaces.
Who pays the fees. New products and options start with Buyer: you receive the full price without changing anything. See Platform fee.
Links the platform sends. Payment, certificate verification, invite and offer links have new, standard addresses. The ones already sent keep working.

Fixes

A plan subscribed twice. Someone who already subscribed to a plan could buy it again. Now checkout tells them they already subscribe and, if they have an unpaid PIX or boleto for that plan, reuses it instead of creating another. See Checkout.
A paid PIX stuck on "waiting". When the payment confirmation was slow, the order sat still. Now Memberfy fetches the result on its own, and access opens as soon as the payment is confirmed.
Card renewal. The subscription period could move forward before the card was approved. Now it only moves when the payment is confirmed.
Wrong current password. Getting the current password wrong while changing it used to sign the person out. Now the warning appears in the form, and they stay signed in to try again.
One password rule everywhere. Each screen asked for something different. Now it's always the same: at least 8 characters, with an uppercase letter, a lowercase letter and a number, and no special character required. See Sign-up and access.
Reserved addresses. A section with an address like admin or pricing hid a platform page. Now those names, and any starting with _, are refused when you create the section. See Sections.
Asterisks in the assistant's posts. Before, posts created by the AI assistant showed asterisks and other symbols instead of formatting. Now the text arrives formatted.
Reacting and commenting on a status outside a space. Before, reacting to or commenting on a status posted outside a space gave an error. Now it works like any other.
Product or option created twice. Before, when creating a product or a billing option, the screen showed an error even though everything had been created, and a second click created a copy. Now creation shows success, and there's no duplicate.

For developers

This part is for anyone integrating Memberfy through code, or who wants the MCP server's technical details. None of it is needed to use what's above.

API

Breaking change: the community left every path. Community routes no longer carry /api/communities/{communityId}: the community comes only from the X-CommunityId header. The old paths were removed, with no transition period, and answer 404. Without the header, the routes answer 400 with errors[0].param = "X-CommunityId".
- /products, /coupons, /subscription-groups (with downsell-offers and reorder), /fees and /fees/simulate, /ledger, /payouts, /reports/*, /business-information and /payout-settings move to /api/<same>.
- Team subscription management moves to /api/manage/subscriptions; /subscriptions/me and /purchases/me move to /api/subscriptions/me and /api/purchases/me.
- The nested checkout is gone: use /api/checkout/*. E-mail stats, /webhooks/email/stats/{communityId}, move to GET /api/emails/stats.
- Only the SuperAdmin routes under /api/admin/communities/{communityId}/fee-overrides/... and the community's own routes keep the id in the path: PUT and DELETE /api/communities/{id}, GET /api/communities/{id}/members and PATCH /api/communities/{id}/settings.
- The operationIds didn't change, so the SDK method names stay the same; only the nine nested checkout operations are gone. Don't pass communityId in the SDK arguments anymore: it would go into the body.
- The full before-and-after table is in X-CommunityId.
Subscription management at /api/manage/subscriptions: list, export, view the detail, create and act on each subscription.
Pay now at POST /api/subscriptions/{id}/pay-now, and confirming an order at POST /api/checkout/purchases/{id}/refresh.
Installment interest in the calculate-price and checkout responses, with the installment options and the total.
Setting the invite password at POST /api/auth/set-password.
Search by title at GET /api/search: posts, events, courses, sections, spaces and calls for papers, ignoring accents and case, and only what the person can open.
Moving a post at PUT /api/content/{id}/move, moderator and up; the destination must be a Content or Feed space.
Modules and lessons at PUT and DELETE /api/courses/module/{moduleId} and PUT and DELETE /api/courses/lesson/{lessonId}: rename, reorder, move a lesson to another module and delete, keeping progress.
Community language with the optional language field in PUT /api/communities/{id}: only the 10 variants (pt-BR, es-MX…); any other value returns 400.
Monetization as drafts: POST /api/products no longer requires approved Business Information (the product starts as DRAFT, in the currency of its country or in BRL). Publishing (POST /api/products/{id}/publish, or PUT with status: ACTIVE) without approval returns 403 with the translated message, and with a currency different from the approved one, 400 (param: currency). Checkout, buying an add-on and accepting a downsell refuse with 403 any product from a community without approval.
Activity logs at GET /api/activity-logs (owner and admin): the timeline behind Members › Logs, with the sources team, assistant and members and the filters source, profileId, from, to, page and limit. Each item has actor, action, actionLabel in the request's language, target and details; the assistant's arguments come summarized, without tokens, images or secrets.
Diagnostics for an MCP connection at GET /api/oauth/connections/{id}/diagnostics (owner and admin): the last tool list the connection received, the current one, and whether it's up to date (listUpToDate).

See the API reference.

MCP: technical details

If the assistant can't find a new tool, it tells you to open a new conversation. Some assistants keep the tool list from the start of the conversation; when Memberfy is updated afterwards, the assistant now gets that message instead of an unexplained error. Under the hood: serverInfo.version is now <version>+<commit>; initialize and tools/list return _meta.memberfy with server_version, tools_fingerprint and tool_count; the audit gains the session.initialize, tools.list and tool.unknown events; and the connection diagnostics show whether the list is up to date. See Common problems and Server and tool list version.
Logs and diagnostics through the assistant: 184 tools. list_activity_logs (owner and admin, read-only) reads the activity logs with the same filters, and profile takes an id, an e-mail or an app link; get_connection_diagnostics (owner and admin, read-only) says whether the assistant's tool list is up to date (with listUpToDate false, reconnect). member_activity now also takes the profile link. The recipe Who did what puts them together. See Members.
Every module: 182 tools (up from 102) and 8 prompts. The whole call for papers (40 tools: the space's rules, opening and editing the call with tracks, days and banner, publishing and unpublishing, owners, reviewers per track, inviting speakers, submitting, editing and withdrawing a proposal, scores and progress, deciding, counter-offers, confirming in the program and voting) and the create_call_for_papers prompt. Structure: update_section, reorder_sections, reorder_spaces, delete_section, delete_space, update_space_access and update_space with section_id; create_space accepts call4papers. Content: move_post and create_short_post. Events: delete_event, start_live_stream, stop_live_stream, rsvp_event. Courses: editing and deleting modules and lessons, delete_course, enroll_in_course, complete_lesson. Gallery: list, edit, react and delete. Members: remove_member. Subscriptions: export_subscriptions_csv. Sales notices: get_notification_settings and update_notification_settings. Certificates: duplicating a template, who issues, resending the e-mail, retrying, list_my_certificates and set_certificate_indexing. Sales: editing and deleting downsell offers and coupons, delete_product, delete_plan, reorder_plans. A member's own side: list_my_subscriptions, list_my_purchases, manage_my_subscription and get_my_points. search_content now searches on the server and finds calls; update_community_settings accepts language. The 40 call-for-papers tools show up for every role, because a call's owner can be a member; Memberfy decides call by call. See Tools and Tools · Call for papers.
Publishing without approval doesn't undo the composite tool. In create_course, create_event and create_plan with publish, a refusal for lack of approved Business Information leaves everything as a draft, returns publish_blocked with the reason, and next_steps points to the Business Information and then publish_product. See Drafts before approval.
Server at https://api.memberfy.net/mcp, with OAuth authorization through the Memberfy account and the tools grouped by subject, each with a badge: read-only, changes data, or asks for confirmation. See Tools.
English names. Tools have English names, the same in every language (create_post, list_spaces, issue_certificate, sales_report); the title shown in Claude or ChatGPT comes in the language of whoever connected. The assistant picks up the new list in the next conversation.
Links and search. open_link understands a link copied from the app, and every id parameter accepts that link; search_content finds posts, events, courses and spaces by title. Posts (cover, pin), events (banner), courses (cover, status) and comments can be edited. See Tools · Content and engagement.
Two-step confirmation only for money and deletion. The money tools (create_coupon, update_coupon, update_coupon_status, delete_coupon, update_price, request_payout, cancel_payout, cancel_subscription, create_manual_subscription, update_subscription, create_downsell_offer, update_downsell_offer, delete_downsell_offer, manage_my_subscription, delete_product, delete_plan) and every tool whose name starts with delete_, remove_, revoke_, withdraw_ or cancel_ require confirmation_token: 36 in total. Everything else runs on the first call, including invite_member, invite_members, update_member_role, update_community_settings, update_space_access, issue_certificate, resend_certificate_email, retry_certificate, decide_proposal, negotiate_proposal and update_plan. issue_certificate gained dry_run: true, which returns who gets one and who is skipped without issuing. Money and deletion tools carry destructiveHint. See Money and confirmation.
Markdown both ways. Post text (create_post, update_post), event description (create_event, update_event), call text (create_call_for_papers, update_call_for_papers) and proposal description (submit_proposal, update_proposal) take Markdown (bold, italic, lists, links, subheadings from level 2, quote, code) and are stored as the app's formatted text. The short post (create_short_post, update_post with type: status) takes only bold, italic, links and line breaks. Titles, names, comments and the descriptions of courses, products, plans, groups, spaces and sections lose the marks. An image inside the text becomes a link, and a table becomes lines. When reading, the text comes back in Markdown, with text_format: "markdown". See Markdown text.
Images by URL or as the file itself (up to 5 MB; SVG becomes PNG), and space icons picked by topic. See Images.
Members, groups, tags and org chart: up to 100 invites per call, with a line-by-line result. See Tools · Members and the Invite a class recipe.
Community settings through update_community_settings: name, colors, logo, favicon, SEO and joining rules. See Tools · Community and structure.
Certificates: templates (platform design or your own artwork) with the preview as an image in the conversation, issuing with a dry run first, revoking, reissuing and deleting. See Tools · Certificates and the recipes Issue certificates to the class and Create a template with the brand's art.
Call for papers, ranking, store and moderation. See Tools · Call for papers.
Sales and subscriptions: editing plans and products, pausing coupons and seeing who used them, creating downsell offers, and complimentary, discount, extension, add-ons and payment link on each subscription. See Tools · Sales and plans and Tools · Subscriptions.
Reports (sales_report, subscriptions_report with MRR, members_report, engagement_report, events_report, courses_report, community_overview), with data ready for charts. The finance role sees sales and subscriptions; moderators see members, engagement, events and courses. See Reports and charts.
next_steps: after showing data or finishing an action, the response suggests up to three next steps to the assistant, based on the result and the role. See Next steps.
MCP prompts: the eight recipes in Claude's menu are server prompts, translated and filtered by role (owner and admin 8, moderator 6, finance 3, member 2). See Ready-made recipes in the menu.

Releases · Memberfy

2 novembre 2026

#Nouveautés

#Améliorations

#Corrections

#Pour les développeurs

#API

#MCP : détails techniques

1 novembre 2026

#What's new

#Configurable levels with weekly activity requirements

#What is left this week, on the profile

#Level and points triggers in workflows

#Revenue in Monetization

#Cookie notice in communities with Google Analytics

#Spaces and sections can open for whoever holds a badge

#Spaces and sections that open by level

#Badges awarded automatically

#Daily points cap per action

#Signed calls in Call webhook

#Campaign audience by custom field

#Display per space, with an Events calendar

#Turn off comments per post

#Feed by activity

#Welcome and First steps

#Scheduled posts

#Groups with an end date

#Reason when removing a member

#Member referrals

#Videos from Bunny Stream, Cloudflare Stream, Panda Video and HLS

#Points in the Store

#Sending through your Resend account

#Badges and points in the member import

#Dark mode

#Deleting your own account

#Download your data

#Data retention period

#Minimum age

#Circle alternatives guide on the website

#Improvements

#Fixes

#For developers

#API

#MCP: technical details

31 octobre 2026

#Improvements

#Fixes

30 octobre 2026

#What's new

#Improvements

#Fixes

#For developers

#API

#MCP: technical details

29 octobre 2026

#Networking

#Member page

#Side column in the Feed

#Recognition with types and art

#Chat on your photo, with status

#Browser and phone notifications

#Improvements

#Fixes

#For developers

#API

#MCP: technical details

28 octobre 2026

#What's new

#Improvements

#Fixes

#For developers

#API

#MCP: technical details

27 octobre 2026

#What's new

#Improvements

#Fixes

#For developers

#API

#MCP: technical details

Nouveautés

Améliorations

Corrections

Pour les développeurs

API

MCP : détails techniques

What's new

Configurable levels with weekly activity requirements

What is left this week, on the profile

Level and points triggers in workflows

Revenue in Monetization

Cookie notice in communities with Google Analytics

Spaces and sections can open for whoever holds a badge

Spaces and sections that open by level

Badges awarded automatically

Daily points cap per action

Signed calls in Call webhook

Campaign audience by custom field

Display per space, with an Events calendar

Turn off comments per post

Feed by activity

Welcome and First steps

Scheduled posts

Groups with an end date

Reason when removing a member

Member referrals

Videos from Bunny Stream, Cloudflare Stream, Panda Video and HLS

Points in the Store

Sending through your Resend account

Badges and points in the member import

Dark mode

Deleting your own account

Download your data

Data retention period

Minimum age

Circle alternatives guide on the website

Improvements

Fixes

For developers

API

MCP: technical details

Improvements

Fixes

What's new

Improvements

Fixes

For developers

API

MCP: technical details

Networking

Member page

Side column in the Feed

Recognition with types and art

Chat on your photo, with status

Browser and phone notifications

Improvements

Fixes

For developers

API

MCP: technical details

What's new

Improvements

Fixes

For developers

API

MCP: technical details

What's new

Improvements

Fixes

For developers

API

MCP: technical details

Workflows: new editor and results

Run now, Scheduled and Webhook received

Call webhook and Variables and keys

Run history from the inside

The assistant learns to automate

Platform actions and Call workflow

Custom domain

My tickets