What's new
What has changed
New capabilities and improvements, newest first. What isn't here hasn't shipped publicly yet.
- New
A meeting is never finished
Ending a meeting is no longer the end of it. Generate summary builds the record, and anything that changes what the record should say — a new participant, organisation or engagement, or resuming the recording — returns the meeting to "in progress" until a fresh summary has run. A finished meeting can be resumed at any time. And before summarising, the credit cost is shown from what this workspace's previous summaries actually cost rather than from an estimate.
- New
A meeting knows which engagements it is about
A meeting can attach to one or more engagements — at creation, from the engagement's own page, or later from the ⋯ menu, with the same badge organisations already have. It announces itself on each engagement's feed, and a meeting that has already ended can still be filed — which is when a forgotten one is usually noticed. Attaching grants nobody access: the meeting stays private at every stage.
- New
A comment is a record
Comments and decisions written on a feed now behave like every other record: their author can edit or delete them, and anyone who can read one can reply to it in the thread design. In every thread the newest reply sits on top and the original stays at the foot. Tasks are editable, deletable, tickable, re-assignable and repliable wherever they appear, and choosing an owner is a full-height sheet instead of a dropdown — it works on a phone and never shortens the list of names. Anything scheduled shows its real time on the agenda, meetings show their duration, today is marked by a date badge and a now line, and figures are written in the script of whichever language the app was opened in.
- New
Everything about a contact, on the contact's own page
Action items, records and notes now appear in one chronological list on a contact's, organisation's or engagement's own page. Before, an action item a colleague assigned you showed up only on Work, never on the page of the person it was about. An action item can also be owned by someone who has no login — a client's own finance lead, say — and can be written as the answer to a decision or a risk.
- New
Typed replies, and editing in the same box
A reply to a record can now carry its own kind — a decision, a risk, a blocker — instead of always being a comment; the server had always accepted it and the client never sent it. Editing a card opens in the page's own writing box rather than a separate window.
- New
One writer, one card language
Every contact, company and engagement page now has one writing box: a comment by default, switchable with one icon to a task, decision, blocker, idea, potential or risk — and while you write, the box itself takes on that kind's card design. Task cards and plain comments adopted the same card language, and every record takes replies right from its card.
- New
Work is yours — access control reaches the Work page and companies
The Work stream, agenda, task board and filter counts now show only what the signed-in user is allowed to see, and records join that same stream beside tasks and feed posts. Companies follow engagements: a company is visible to its creator, the members of its engagements, and admins. Rostering a private contact into a meeting shares them with that meeting's participants only — never the whole workspace — and every contact's owner is visible on its page and transferable.
- Improved
Assign a task's owner right where the task is made
A decision posted in the feed can name its owner in the same act, and the owner shown on every task card is now a control: one tap hands the task to a colleague or unassigns it.
- New
Records — write decisions, blockers, ideas and risks in place
Every contact, company and engagement page can now take a record: a decision, blocker, idea, potential, risk or comment — each with its own card, accountable person and date. Records take replies in a thread, can be edited by their author, and show up in the Work stream and agenda on their own date.
- New
The assistant sees with your eyes and acts on your approval
The assistant answers strictly from what the asker can see: engagements, contacts, meetings and records are now retrievable sources, each filtered with that user's own eyes — a filter that lives inside the query rather than after it. An engagement can be team-private, and a new contact belongs to its author until shared or visibly widened. The assistant also writes records: every step is previewed, executes only on human approval, and carries the assistant's mark permanently.
- New
The security envelope, health monitoring, and a backup that cannot pretend
Six parallel audits walked the whole platform and every critical finding is closed: each response wears the security headers and CSP, uploads stream against hard ceilings, account lockout works independently of IP, and markdown renders through a single sanitizer. One health endpoint reports the database, the job broker, the applied migration and the age of the last backup — probed at the origin, so a CDN outage cannot mask a dead box. And the backup design refuses the most dangerous state in operations — the backup everyone believes in and nobody has seen: a run marks itself complete only after every artifact of it exists, the health endpoint reports that mark's age, and a backup that has never run reads as stale, never as fine.
- New
Seven record kinds, one card, one thread
Task, comment, decision, blocker, idea, potential and risk are now one shape: one card, one table and one conversation. Any record can be replied to, and a reply is itself a record of any kind — a comment unless the writer says otherwise. Editing and deleting belong to the author; replying belongs to anyone who can read it.
- New
One bar, three things happening in the meeting
A recording meeting now carries one progress bar that says three things at once: how much has been captured, how much of that is safely transcribed — always a little behind — and which summary windows have actually run. The scale grows with the meeting: six marks to start, and always two ahead of where you are. When nothing is in flight the bar renders nothing at all.
- New
Correct the meeting record, then send it
The record Pulse builds from a meeting can now be corrected in place — the title, each participant's role, every topic heading, every entity's text and the executive summary. Then the same record goes out as a designed PDF or as markdown. The document states its own condition — provisional, corrected on a date, or as extracted — and carries no signature, because nothing recorded an approval.
- New
Work becomes a calendar agenda
The Work page was a list of what had been written; it is now a calendar of what is happening. Every row sits on the day it occurs — a task on the date it is scheduled for, a meeting on the meeting's own time, and an unscheduled task on the day it was written — so nothing is left undated and no date is invented. The page scrolls down into the days ahead and up into the past, and the days are there whether or not anything falls on them.
- New
The meeting's record, while the meeting is still going
A meeting's structured record — decisions, actions, blockers, topics — used to exist only once the meeting was over. It is now rebuilt every few minutes from what has been said so far, and every reader of the meeting sees it in the Pulse conversation as it grows. Each pass reconciles rather than rewrites: anything a person has edited or dismissed is left alone, and the record says it is provisional until the meeting ends.
- New
An engagement shows only the surfaces its kind of work needs
A service in the catalog declares what kind of work it is — General or Financial. Engagements of a general service no longer carry financial statements, analysis and findings: work that is not about a client's numbers stops offering financial tools. Each service also carries its own document-request checklist, written by the firm or installed from standard lists. The weekly summary is retired — meetings now write into every related feed themselves.
- New
A meeting is always private, and its transcript is not a document
A meeting is private at every stage, and there is no longer any way to open one to the whole firm — sharing happens only by granting a specific person access. The transcript is no longer a document: it is a file that no door serves, so it does not appear in the documents list, in search, or in the assistant's answers. Existing transcripts were migrated with their exact reader list preserved, so nobody's access changed.
- Improved
One card for an engagement, and one meaning for "client"
The engagements list said an engagement's name twice: once as the title, and once on the line beneath it. An engagement now renders as one shared card everywhere it is listed, and the part of the name the page header already states is no longer repeated. In the contacts directory, a "client" badge on some rows disagreed with the Client filter at the top of the same page — and it was wrong in both directions. The badge is gone; the question is answered once, by the filter.
- Improved
Dialogs move properly on a phone
Everything that covers the page — sheet, dialog, drawer, full-screen viewer — now comes from one shared layer. On a phone it slides in and out instead of appearing, you can put it away with a downward drag, and the device back button closes it rather than leaving the page. Escape closes the topmost one only, not everything that happens to be open. Separately, the app's initial download is 43% smaller.
- New
Talk to the meeting — the meeting page is a conversation
Every meeting page is now a private conversation with Pulse: ask mid-meeting or after, and answers come from the transcript as it stands, citing the passages used. Creating a meeting reads like an invitation: title, people, organisation and time in one frame — a date left at now means Start, any other date means Schedule. Recording survives navigating the app, and a live meeting floats within reach on every page.
- New
Meetings: live capture, a Persian transcript, restricted access
A meeting is now an entity: several people, one transcript. Audio arrives in chunks and is transcribed to Persian in the moment — with a glossary built from the meeting itself, so people's and companies' names come out right — and an already-recorded file is accepted too. The transcript is a document born restricted: only participants and the explicitly invited can read it, and for everyone else it appears in no list and no search. The audio expires after a while; the text stays.
- Improved
Every member is a contact — and one who has left says so
Anyone added to a workspace now appears in Contacts in the same moment. Only some of the doors did that before, and invitation — the main way people join — was not one of them. A colleague removed from the workspace keeps their contact, because their history and work are the firm's record, but the row now carries a "Former" mark and they are no longer offered in pickers. Deleting a contact is no longer half-guarded either.
- New
Restricted documents — access only for the people on the list
Any document can be made confidential: only the uploader, the people granted access, and workspace admins can see it — for everyone else it simply does not exist, in lists, in search, and in Pulse's answers alike. Sharing is a deliberate, recorded act: who granted, to whom, and when. A document can also be born restricted at upload.
- New
Work became the stream of the whole firm
Until now a feed was something you opened one at a time — a contact's, a company's, an engagement's — and Work was only the task board. Work now reads every feed in the workspace at once, chronologically, filtered on two axes: whose feed, and what kind of thing. Selecting tasks and nothing else gives back the old grouped board, so nothing was traded away for the stream.
- Improved
Where the product asks, it asks in Persian
The last English left in the product is gone: the "New engagement" button and the list/board view chips, the services page's badges and the engagement and client counts under every category, and all four forms that ask the user for something. An English label on a filter can be read past; one on a form you have to fill in cannot.
- Improved
Your account, where your workspaces already are
The workspace sheet now opens with you: avatar, name and email, a bell carrying the count of your own overdue tasks that taps straight through to them, and a gear to your account settings — a page that until now was reachable only from inside the chat sidebar. Below that, your workspaces and the way to make a new one; at the bottom, a sign-out that names the account it ends. Nothing overdue, no badge.
- New
One settings page, and colleagues in the directory
Five separate panels are now one page with five tabs: General, Users, Agent, Billing and Credits. The user list has search and invite, and each person carries their own role and seat type as far as the plan allows. More to the point, the firm's own people are no longer only a login: they are contacts, with a page, a feed and a seat.
- Improved
Settings, made one thing
Every settings surface — the workspace's five tabs and the personal account page — was rebuilt on one design language: a centred identity, borderless cards separated by space, thumb-sized rows, and choices made in a bottom sheet that says what each option means. Three tabs had been rendering 32px narrower than their siblings on every phone; they no longer do. The assistant's capability page is fully Persian for the first time, with a test that stops a new capability shipping untranslated.
- New
Indicators, simplified: two axes instead of four labels
You no longer have to pick one of four kinds of indicator before you can measure anything. You say what you are measuring — a result, or a performance measure — and then promote the ones that matter this chapter. KRI, RI, PI and KPI are derived from those two facts rather than chosen ahead of them. Promotion is a management decision and it is recorded, so you can still ask what mattered last quarter.
- New
A Persian interface, with its own typeface
Contacts, engagements, services, work, Pulse and chat are now Persian, set in PeydaWeb — self-hosted — with right-to-left leading. Persian is no longer a translation of the interface; it is its first language.
- Improved
Engagements and services, Persian to the last word
The engagement page and the service page — and everything they render, from the FDD workbench to the feed and the weekly milestone — are fully Persian. Most visibly, the pipeline's stage and outcome vocabulary follows the reader's language; a name a firm gave one of its own stages stays exactly as they wrote it, in either language.
- Improved
Indicators moved into the service catalog
The indicator library and the scoreboard moved out of the daily-work nav into the service catalog's tab strip. Nothing about what an indicator is changed — the model, thresholds and breach path are untouched, and there is no migration.
- New
Indicators: the platform measures itself
You define the indicators and their thresholds are versioned. When one breaches, it surfaces through Pulse rather than in a dashboard nobody opens. A KPI must name one owner and a KRI must have none — a rule that is enforced, not advised.
- New
One address: samanegaar.ir
The site and the product share one domain. Signed out you get the marketing site; press Sign in, enter your email and password, and the platform opens. If you are already signed in you go straight through, with no flash of marketing on the way. There is no separate subdomain, and sessions that were already open were left alone.
- New
Run it on your own servers
Self-hosting became a complete channel: four containers, one volume, and a licence that verifies offline. The software makes no outbound connection to run.
- New
Sign up directly
Accounts are no longer invitation-only. A signup path exists, and you can start without talking to sales first.
- Improved
Control what the assistant may do
The assistant's capability map became a real admin page: each capability can be switched on, off or locked. The boundary between proposing and doing is set by the workspace administrator, not by us.