October 25, 2026

• 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.