October 22, 2026

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

1. Open Chat, People tab, and tap someone online (or Send message on their profile card).
2. Write and send; the person gets it instantly.
3. 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.

1. Tap Drops and allow the camera and microphone (the browser only asks now).
2. Tap Record and, when you're done, Stop; at 3:00 the recording stops on its own.
3. 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.

1. Write the text and click Improve with AI.
2. If you like, write an Instruction (optional), such as shorter or more formal, and click Improve.
3. 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.

1. 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).
2. Ask each person to build their PDI and, in study actions, pick the course.
3. 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.

1. Set the Workplace by address search or with Use my location.
2. Choose the Radius and the mode, Block or Flag.
3. 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.

1. On the wall, open Filter by value and pick a value; See all goes back to the whole wall.
2. In the Dashboard, choose the period and look at the By value block.
3. 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.

1. Open Numbers and choose the period and, if you like, a group.
2. Click Download CSV or Download Excel.
3. 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.