What shipped, and when it was verified

Agents connected over MCP can read a project’s classification label and security checklist with the new get_project_security tool, using the person’s own project access. The record link tools now also understand assets, suppliers, Governance controls and register entries and approved policy versions, each only within the modules the person connected and with their own permissions in Governance, never an administrator’s. Linking still asks for approval.

Risks of the register are not reached by an agent’s own session; a link to a risk is drawn after approval on a screen or on the web. The companion in the app has no project security tool.

Suppliers from the Contracts register and approved policy versions can now be linked to Governance controls, risks and register entries like any other record: paste the supplier’s address, or the new “Link to this version” address on an approved policy, into the record links of a control, risk or entry. A control can so show the exact version of a policy that was in force as its evidence, not whatever the page says today. Each person sees only the links whose other end they may read, and a supplier’s risk notes never appear on a link. Supplier links that register entries kept as text are moved to record links, and the text field is gone from the entry form.

Links are drawn on the web and through the API and MCP; the phone apps show none of them. Text links to a supplier of another organisation are dropped during the move.

When you start an access review in the console you can now have it repeat every 90, 180 or 365 days. On the day, the same campaign opens again with the same reviewers and the same time to decide, and the reviewers are notified as before. It opens in the name of the administrator who set it up, and only while they may still open campaigns. The console shows when the next one opens and lets you stop the repetition.

Only one recurring campaign per organisation. If the administrator who set it loses the right to open campaigns, or a named reviewer leaves, nothing opens until somebody sets it again. Campaigns are still closed by hand.

An asset now has a next review date beside its licence expiry. Once a board is chosen in Governance settings, each owned asset’s licence expiry and review, and each owned policy’s review date, become a recurring board item assigned to the owner that cannot be marked done without evidence, and come round again every year. The item names neither the asset nor the policy, so the board’s readers learn nothing they could not read before. A policy reviewed on the board no longer sends the separate reminder two weeks ahead.

Items come round yearly from the date they were made; changing the date later does not move an item that already exists. Retired and disposed assets and policies without an owner get no item.

Security responders can connect a dedicated mailbox that people outside the organisation write to with security reports. Each message lands in a triage queue on the security incidents page, marked as authenticated when your own mail server confirmed the sender passed DMARC for their domain, and unverified otherwise. Nothing in the queue is an incident yet and no deadline runs: a responder accepts a message, which opens a security incident with the sender, subject and text and starts the organisation's awareness, or discards it, after which it is deleted within two weeks. Attachments are virus-scanned and become evidence only once clean. Daily limits per sender and per organisation are counted, not stored, and senders never receive an automatic reply. The mailbox is not listed among mailboxes, cannot be shared, and is never read by assistants; agents see only the waiting senders and subjects over MCP, after asking.

Mail already in the folder when the intake is set up is not read. Unverified messages nobody decides on are deleted after 30 days. Responders are not notified of new messages. Configured on the web and desktop only.

Governance gains registers for continuity plans and exercises, backup-restore tests, threat intelligence, vulnerabilities and legal and contractual requirements. A plan, a backup test, a threat note or a requirement can be scheduled as a recurring board item that cannot be marked done without evidence. A change is now approved by a second person who neither proposed nor edited it, and any later edit withdraws the approval; every entry keeps who proposed, edited and approved it. Evidence collectors check your own Enclessa settings — a second factor for administrators, single sign-on, audit anchoring and retention — and, with a read-only GitHub token of their own, the organisation's 2FA requirement, branch protection, open Dependabot alerts and open secret-scanning alerts. Each run is kept redacted, hashed and signed, and a failed check opens a vulnerability. Agents read the registers and the evidence over MCP with the same permissions.

GitHub is connected with a fine-grained token, not a GitHub App, and up to 100 repositories are checked per run. On the web and desktop only.

People now records the people side of an information security management system. Screening results are kept as type, date, result, legal basis and who checked — never the report itself — and a criminal-record or credit result is deleted three months after the check. Disciplinary cases have their own history and are deleted two years after they close. Both are seen only by people given the screening or disciplinary role, never by an administrator for being one and never about themselves. Every onboarding asks for the confidentiality agreement to be acknowledged, and a transfer asks the new manager to review the person's access. Training courses have an audience by department or position and a repeat interval; a completion is filed as a training document that expires when the course is due again. HR sees who is overdue on a course, who has not acknowledged a policy and which position requirements nobody holds. Offboarding now ends the membership the way removing a member does — devices, sessions and API, OAuth and agent tokens — removes GitHub access when the step says so, lists the webhooks, endpoints, mailboxes, contract reviews and security incidents left behind, and keeps what it revoked as evidence. An announcement can ask every member to confirm they read it, and a communication plan records what is told to whom and when.

With single sign-on, the account at the identity provider is not disabled from here: the offboarding records that it has to be. Offboarding an administrator takes a second administrator unless single-person offboarding is turned on. Recurring awareness campaigns, course quizzes and issued equipment follow later; the phone apps do not show screening or disciplinary records.

Contracts now keeps the suppliers you rely on, not only your customers: what each one does for you, how critical it is, what data it handles and how that data is classified, where it is processed and on what basis outside the EEA, whether it is a cloud service, its contract and data processing agreement, its certifications with their expiry, the next review and an exit plan. The owner is reminded before a review or a certificate falls due. Suppliers that process customer data are the sub-processor list every new AVV starts from, so the two can no longer drift apart. Send a supplier a security questionnaire through the Customer Center and record the completed answers as an assessment, kept unchanged with a SHA-256 of the answers and the uploaded files. Risk notes and assessments are seen only by people given the supplier risk role — an administrator is not let in by being one. Information-transfer agreements are a template kind of their own.

On the web, and readable by agents over MCP. Reviews are a date with a reminder, not yet a recurring task.

When a management review ends the segregation-of-duties exception for single-person closure, Incidents' setting that lets one person close a security incident is switched off at the same time and the change is recorded in the audit log — the exception and the setting can no longer drift apart.

Each project now shows a Security card on its overview: a classification label from your organisation's levels and a checklist of seven security steps — classification, risk assessment, access, data protection, secure development, suppliers and a clean handover — ticked by the project's managers, with who ticked each step. People with the risk role can copy a project risk into Governance's organisation register straight from the project's risk list.

The checklist is the same for every project and cannot be edited yet. It is not available to agents.

Choose a board in Governance's settings and every control test and risk review comes round there as a recurring item, assigned to its owner, that cannot be moved to done without a file or a record link as evidence — so the work shows up in Agenda and Calendar like any other. Risks, controls, register entries and assets can now be linked to the pages, files, board items and incidents that implement, evidence, treat or affect them, from a panel on each record; a link shows only to people who may read both ends, and a risk only to holders of the risk role.

Without a board the test reminders stay notifications. A risk's board item does not name the risk. Agents link these records through an approval rather than directly.

Governance can now let an external auditor in without letting them into anything else. Invite the auditor as a guest, then grant them one internal audit until an end date at most 90 days ahead; granting needs the risk register permission of your own. They read only the snapshots you freeze for that audit — the statement of applicability, the audit report, a management review or the risk treatment plan — never the live registers and no other module. Every snapshot carries its SHA-256, every time the auditor opens one is recorded in the audit log, and on the end date (or when you revoke the access) the auditor is signed out.

Agents cannot act for an auditor. A snapshot shows what was frozen, not today's state; freeze a new one after a correction.

A new module keeps the parts of an ISO/IEC 27001 management system that belong to no other module. Record the scope, the context including climate change, interested parties and who holds which ISMS role. Set a risk matrix, an appetite and who may accept which risk; keep the organisation risk register with treatment and residual risk, where a risk is accepted only by somebody who never owned it and only within their authority. Set up the 93 Annex A controls in your own words as a statement of applicability with owners, evidence, a test procedure and the next test date; a failed test opens a nonconformity whose corrective action a second person checks. Plan internal audits and record findings, measure objectives per period, keep change records, records of processing and DPIAs, and hold management reviews from a frozen pack of inputs with recorded decisions. The SoA, the risk treatment plan, a review and an audit export as Markdown with your classification label. The risk register is visible only to people given the risk role — an administrator is not let in by being one. Agents read it over MCP with the same permissions.

On the web and desktop only. External auditor access, project security checklists and PDF reports are not there yet. A team without a second person records a dated exception, which a management review has to renew.

A new Assets module keeps the register of information, software, hardware, services and sites, with owner, custodian, location, lifecycle, licence expiry and the acceptable-use rule; sites list their physical controls, equipment can be issued to a member, and a disposal is recorded with its method and a witness, counts once the witness confirms it, can be withdrawn until then, and cannot be changed afterwards. Administrators define classification levels; Spaces pages, files and assets carry them, they show wherever the record is and travel with a Spaces export, and sharing a file with a customer above a chosen level asks for confirmation and is recorded in the audit log. Bookings gains a visitor log that deletes entries after 90 days unless set otherwise; reception sees every visitor, everybody else the visitors they host or signed in. In the console, access reviews freeze who holds what, send each grant to a reviewer who never reviews their own, revoke on submit, escalate at the deadline and keep the closed review as a hashed record; a report lists privileged access and who signs in with a second factor or single sign-on.

Reviews and asset checks are started by hand for now; recurring schedules follow. Agents read the asset register over MCP; the companion has no Assets toolset yet.

A page in Spaces can be kept as a policy with an owner, a document number, a classification, a next review date and the people asked to read it — everyone, or departments and positions from People. Somebody who did not write it approves it: the approved version is frozen with its SHA-256 and stays in force while later edits wait as a draft. Everyone asked acknowledges each approved version, the owner sees who has not, and the owner is reminded two weeks before the review date. Twelve policy templates in German and English — from the information security policy to retention — are offered when you write a new page, and replaced versions and acknowledgements can be kept for a set number of days before they are removed.

Approving and acknowledging are on the web. The approver needs a confirmed second factor; small teams can let the author approve, and each such version says so. The classification is free text for now.

An invitation mailed to somebody without an account now has Yes, Maybe and No and an Add to calendar link. They open the guest's own invitation page, where the answer is sent with one more press, the meeting can be joined, and the event goes into Google Calendar, Outlook or any calendar as a file. The answer shows up in Who is coming and the organiser is notified when it changes. Whoever may change the event can copy each guest's link from the guest list, on the web and on the phone; taking the guest off ends it.

The answer is recorded in Enclessa, not in the guest's own calendar app, and an answer sent from their mail program still only reaches the organiser's mailbox. Not on calendars synced from Google, Microsoft or iCloud.

A board item can repeat every day, week, month, quarter or year — or on any rule over the API — counted from its target date. When it is done, or when its date arrives, the next one appears once in the board's first open column, with the same text, tags and the people still in the team. An item can also require evidence: it cannot move to a done column until a file is attached or a record is linked to it. A repeating item that is overdue stays in its assignee's Agenda and Calendar until it is closed.

Custom field values are not copied to the next item, repeats are set on the web and desktop only, and an item closed by a GitHub or GitLab sync skips the evidence check.

Link any two records you can open with a meaning and a reason: a page implements a control, a file evidences a board item, a board item treats a risk, an incident caused or affects something. Every link is shown with who drew it and why — but only to somebody who can open both records; a link to something you cannot open is left out rather than shown blank. Links are drawn and removed over the API and by a connected agent, with your approval.

There is no screen for drawing these links yet. A connected agent links board items, projects, customers, knowledge-base pages and Studio posts and shoots; other records are linked over the API.

Every mail Enclessa sends — mentions, digests, sign-in and password links, invitations, bookings, signatures and calendar invitations — has a new, calmer layout: your brand on top, one clean card with a clear headline and a single full-width button in your accent colour, and a mention shows the message the way the app does — who wrote it and what they wrote. The details you check before clicking — which account, how long a link lasts — sit in a short list, a change to your sign-in is marked in amber and an unpaid subscription in red, with a plain note on what to do if it was not you, and every sign-in link also prints the address to paste if the button does not work. The small print sits quietly under the card. Your organisation’s logo, accent colour, tagline and website carry over unchanged.

Outlook on Windows draws the button with square corners.

Every member can report a security event — a suspicious mail, a lost laptop, data in the wrong place — and follow their own report. Security responders classify it, record the impact on confidentiality, integrity and availability and whether personal data is involved, keep evidence files with their SHA-256, record notifications to the supervisory authority, customers and affected people, and close it with a root cause and lessons learned. A personal-data breach shows its 72-hour deadline and reminds the responders until the authority decision is recorded. Closing takes a second person who did not handle the incident, and only people given the security responder role see these incidents — an administrator is not let in by being one. An alert incident can be escalated into a security incident.

Handling an incident is on the web and desktop; the phone apps report and follow your own reports. Small teams without a second responder can allow one person to close, and each such closure is marked.

A calendar event and an appointment you write down yourself can now be held by video. Guests without an account are mailed a meeting link with their invitation or confirmation, and wait in a lobby until somebody lets them in. The link opens 15 minutes before the meeting starts and closes an hour after it ends, so a forwarded link cannot ring anybody at the wrong time; taking a guest off renews it; whoever may change the event can copy the link, start the meeting at any time, or renew the link to stop the old one working. On the web, on the phone and from an agent.

A meeting with guests is not end-to-end encrypted, it cannot be planned on a calendar synced from Google, Microsoft or iCloud, and a repeating one needs a last date no more than two years ahead.

A reply now quotes the message it answers below your signature, so the recipient sees what you are replying to. Sender names with a comma or quotes reach the recipient as one address, replies go to the address the sender asked replies to go to, and reply and forward subjects get exactly one AW: or WG:. Arriving mail no longer loses its attachments behind an unusual character set, old Latin-1 mail reads correctly, and logos and pictures sent inside a message appear in it instead of in the attachment list. Text colours that would vanish in light or dark mode are dropped, and a link whose text names one website but leads to another shows where it really goes. On the phone, pictures keep their shape, web and mail addresses can be tapped, and quoted history is folded. Giving a ticket to somebody notifies them in their language, as a card on the conversation and by push, and the ticket panel has "Assign to me" and a note field that grows with the note.

Show original still opens no links, by design. Mail that arrived before this change replies to its sender, not to a Reply-To it named.

The website is rebuilt in English and German: a page per feature, sector, use case and integration, comparisons and migration guides, a pricing calculator, a glossary, the roadmap, this changelog with an RSS feed in both languages, and the newsletter.

Appointments are no longer booked on the site; write to us to arrange a call.

People without an account can join a call from a guest link, including a call in a direct chat, and pick their microphone, camera and speaker. Guests now see shared screens and hear their sound, and every camera and screen is shown whole instead of cropped — on the web, on the guest page and on the phone. A microphone or camera that will not turn on says why: blocked for the site, not found, or in use elsewhere. Unmuting works on the first press after a host muted you, and people who leave a call disappear from it reliably.

An end-to-end encrypted call can only be joined from its invite link, because the key travels in the link and nowhere else.

A picture pasted into a board item is attached to it and written into the description as Markdown, the way GitHub issues do it, so it stays where it was placed. Pictures appear as thumbnails once the upload has been scanned, on the web and on the phone, and several items can be added in a row without reopening the dialog.

In an end-to-end encrypted room you can now delete a message you sent, on the web and on the phone. The deletion travels through the encrypted group like any other message, and every device removes the message from its local history.

Deletion removes the message on devices that are members of the room; it cannot reach a copy somebody has already exported or photographed.

The iOS app is available in the App Store for iPhone and iPad running iOS 18 or later. It holds several accounts and organisations at once, opens a tapped notification in the account and organisation it was sent to, lets you invite people from the members list, and follows the system’s light or dark appearance or the one you choose.

There is no Android app.

A signed-in person can change their password under Security, on the web and on the phone. The command palette now jumps to any page of any module, any settings pane and any account setting, finds contract drafts, approvals and signatures, and opens Reminders’ lists directly. Lists filtered down to nothing offer to clear the filters, empty lists suggest the next step, and people can be invited straight from the members list.

A mailbox refreshes from the mail server every 30 seconds and on demand. Mail sent from an organisation’s own domain is signed with that organisation’s own DKIM key, so receiving servers can check it really came from you.

A quotation can be started from a customer’s finance tab, Lexware Office’s response is shown on each quotation row, and an accepted quotation offers its follow-ups on the quotation page. Every billing proposal names its customer, time can be booked from a project’s overview, and the tax reserve is marked transferred per voucher.

The web app now has one flat sidebar instead of a rail with floating panes, and every module page shares the same header and layout. Chat shows each message in its own bubble with your own on the right and a thread’s replies under its first message; mail is organised around the sidebar; boards, projects, customers and spaces have flat headers with tabs. Call reactions and raised hands stand out, and every organisation’s icon appears in the switcher.

An administrator can check any person’s access to a room and gets the answer in plain language, including what keeps somebody out. The person is told when their access changes, and permission settings describe what they allow in words rather than codes.

A shared mailbox can ask the assistant for a proposed reply whenever somebody writes in. The mailbox names the people who review proposals; they are notified when one is ready and accept, revise or discard it beside the conversation, on the web or on the phone.

Nothing is sent without a person accepting it.

An export of everything the organisation holds can now be requested, listed and downloaded from the organisation settings, instead of by asking us. The web, desktop and iOS apps now also carry the licence notices of the open-source software they include.

Rooms now count what you have not read, mark an unread room with a dot, and let you mark a message unread to come back to it. A half-written message is kept as a draft, a message can be scheduled to send later and cancelled from above the composer, and older history loads as you scroll up. Your own messages sit on the right, fenced code is highlighted, and a mention opens the person’s profile card. Direct messages can show read receipts, off by default and visible only when both people share them. An account-wide notification level now applies to every room left on “default”, people choose which notification mails they receive, and a message notification can be answered with a thumbs-up or marked read without opening the app.

Drafts and send later work only in rooms that are not end-to-end encrypted, because both would mean storing unsent text on the server.

The event editor can book a meeting room and shows which rooms are free before the event is even saved. People outside the organisation can be invited by email and receive a calendar file their own calendar understands. Alongside Google, iCloud and other CalDAV calendars, a Microsoft 365 or Outlook.com calendar can now be connected from the calendar settings.

The finance dashboard downloads a period as a DATEV booking batch for the tax adviser, optionally with the documents as PDFs. Sales are booked per VAT rate, credit notes are booked as credits, purchases and cash discounts are included, and reverse-charge and third-country services land on their own accounts. The accounts follow SKR03 or SKR04 by default and can be changed in the Finance settings, and VAT deadlines move past public holidays of the organisation’s state.

Enclessa runs as a desktop app on macOS and Windows, downloadable from this site. It keeps several accounts signed in at once, rings for calls even when the window is closed, shows the unread count on the dock or taskbar, answers a message or a call straight from the notification, and on macOS locks itself behind Touch ID after a while away. The macOS app is signed and notarised. Since version 0.1.25 both apps check for updates in the background and offer to install and restart.

The Windows installer is not yet code-signed, so Windows may warn before running it. Screen sharing from the macOS app is not switched on yet.

A team can now have voice rooms that people simply walk into: entering the room joins its call, which stays docked and can be dragged anywhere in the window while you keep working. In a call you choose your microphone, camera and speaker, join from a second device beside the first, turn somebody’s volume up to 200 percent, mute or remove people as host, and send reactions that float up with your name. A screen share interrupted by a reload can be resumed, and somebody who never answered a call is told they missed it. A soundboard module, in beta, plays short sounds into a call.

An organisation can now allow end-to-end encrypted channels in its teams, not only encrypted direct messages. A member added to an encrypted room can be given earlier messages by somebody who already holds them, unread counts and read positions work in encrypted rooms and follow you between your devices, and encrypted rooms look like every other room. A lost or stolen device can be revoked permanently from the web or the phone, and device certificates now expire on their own. A room whose encryption got stuck can be started again, with a clear notice where that happened, and the recovery phrase can be saved as a file.

Encrypted team channels are off until an organisation switches them on. Earlier messages can only be shared from a device that holds them, covering the last 30 days.

An owner or administrator can export the messages, memberships and file details of the organisation’s rooms for a chosen period of up to a year, as a signed file whose integrity can be checked independently. The audit log can be exported for a date range together with the daily anchors that make tampering detectable. A team or a single room can now keep its history for a shorter time than the organisation as a whole, and every such change is recorded.

The compliance export covers rooms that are not end-to-end encrypted; Enclessa cannot read encrypted messages and so cannot export them.

A set of team roles can be defined once as a permission scheme and bound to many teams, so a change reaches all of them at once. Ready-made delegated administrator roles — system manager, user manager and read-only — can be handed out without giving away more than the person granting them holds. A team manager can time a member out for up to 28 days, during which they can read but not write, and room owners can change a member’s role in the room. Anyone can delete their own account after confirming their password.

Cards, business cards and badges print as PDFs, a share link comes with a QR code, and issuing or withdrawing a card can be a step in onboarding and offboarding. Offboarding can also review and remove a person’s GitHub access. Cards take on the organisation’s own design, and permission templates show what they will change before they are applied.

Apple Wallet and Google Wallet passes are built and not yet switched on for the hosted service.

A working-time policy can follow the German Working Hours Act: missing breaks, too little rest, too long a day, night and Sunday or holiday work are flagged on the day, and so is a day that pushes the 24-week average past eight hours. Public holidays are generated for a chosen state. At year close, overtime beyond the carry-over cap or past its expiry is settled. Approvers can delegate to somebody else and revoke that again, a pending correction shows on the booking it concerns, entries can be suggested from GitHub activity, and timesheet and other scheduled reminders go out. Sick notes and custom fields marked as health data sit behind their own permission.

Breaches are flagged for a person to act on; none of them stops a booking from being recorded.

The part of the API that an access token may call is now published as its own reference, together with a dependency-free TypeScript client. Administrative and internal routes are deliberately not part of it.

An organisation can sign its members in through its own identity provider over OpenID Connect or SAML, and require it. Members and teams can be provisioned and removed from a directory over SCIM 2.0. Anybody can sign in with a passkey, offered by the browser’s autofill, and manage their passkeys in the account settings; the desktop and phone apps hand the passkey step to the system browser. An organisation can serve Enclessa on a domain of its own, which is verified in DNS and over a secure connection and rechecked continuously.

Passkeys work on the Enclessa sign-in address, not on an organisation’s own domain.

The marketplace offers industry bundles — law firm, medical practice, public sector and engineering — that install a matching set of modules in one step. An administrator decides whether a module is open to everyone, to selected people or on request, and members can request one from where they meet it and see where their request stands. Before a module is removed, the marketplace says what becomes of its data and offers an export of just that module. Signed outgoing webhooks report events such as bookings, contracts, tickets and incidents to other systems, and reviewed partner apps can be installed by consent and connected over OAuth.

A conversation in a shared mailbox can become a ticket with a status, a priority, an assignee, internal notes and a linked customer, and arriving mail can open tickets on its own. A mailbox can set first-response and resolution targets and shows which tickets are due or overdue, and the queue can be searched, sorted and paged. A pasted link to a conversation shows as a card in a room.

Next to GitHub, repositories on GitLab, Forgejo and Gitea can now be mirrored onto a board. Board columns map to open or closed, the mirrored issue shows on its item, and issues and merge requests can be mentioned in a room like any other reference.

An administrator can upload a Slack workspace export or a Mattermost bulk export, check a preview of channels and people matched to members by email address, and import the history into new rooms. Timestamps, threads, reactions and Mattermost attachments are kept, every message is marked as imported, authors who are not members appear under their original name, and running the import again adds nothing twice.

Direct and group conversations are not imported, because direct messages in Enclessa are end-to-end encrypted.

The Incidents module, in beta, opens an incident from a monitoring alert, posts it into a room and pages whoever is on call according to a daily or weekly rotation, skipping people who are absent, until somebody acknowledges. Incidents can also be opened by hand, reassigned, annotated and followed on a timeline, acknowledged or resolved with /incident in the room, and leave a follow-up item on a board when they are resolved.

Each appointment type has a booking link of its own that opens a short step-by-step page. The person who booked receives a confirmation and a reminder by email, set per appointment type, and can move the appointment from their manage page. Appointments can also be written down by hand, and booking requests can be searched by name or email.

Two new modules, both in beta. Polls asks a room a question from the composer; when it closes, its creator can turn the winning option into an event. Reminders keeps personal and shared lists with smart lists, repeats, photos and an early alert, hands a reminder to a colleague, and shows what is due on Today and in the calendar. Board items can also carry a private reminder of their own.

A billing run now picks up a contract’s one-off positions and charges each exactly once, and for contracts that include a volume of hours it bills only the overage, once per period. Projects and contracts gained a Finance tab, documents can be bound to a project, and a billing profile can prepare its month on a schedule. Customers see their own invoices and can accept an offer in the Customer Center, and an issued contract offers to set itself up in Lexware Office. Finance also calculates how much should be set aside for tax and reminds the chosen people when the reserve falls behind or a VAT return is due.

Nothing is sent, finalised or paid automatically: prepared invoices stay drafts until a person pushes them, and the tax reserve only records transfers made by hand.

Studio, in beta, plans an organisation’s social media content on a week and a calendar: posts with a creative brief, a script per frame, alt text and wording per network, grouped into campaigns and content pillars, with posting slots and public holidays shown. It warns where a format or length does not fit, plans shoots for chosen posts with a call sheet the crew receives by email, takes a post through review with comments, keeps its history and records how it performed.

A room can invite guests, who see only the rooms they were invited to. An invitation can be accepted with an account somebody already has, the invited email address is filled in on registration, and an existing account can start another organisation straight from sign-up.

The console can now say why a person may or may not do a particular thing, list what they hold and through which role, team or group, compare the roles of a tier against its permissions and preview what a role change would do. Teams, groups and roles are administered together, a team can hold a role and be linked to a channel, and groups can be assigned work and given access to channels and projects. Navigation a person has no right to use is hidden rather than refused.

Board items can be linked to a project milestone, and the milestone shows its progress from the cards linked to it. Project deadlines and project board items appear on the calendar, a card can be due at a specific hour, and the item dialog was redesigned.

A connected AI agent can now administer the organisation — organisation units, positions, locations, cost centres, rooms, team roles, boards and projects — for people who may administer it. Its changes are grouped into a run that a person reviews and approves or rejects as one decision, every change is recorded in the audit log as coming from the agent, and the audit log can be filtered by agent. Text inside a record is treated as data, never as an instruction to the agent.

An organisation sets its logo, icon, colour and tagline in a branding pane with a live preview, and every email it sends uses that brand. Members can hide areas they do not use from their navigation.

Members can protect their sign-in with an authenticator app, enrolled by scanning a QR code, and an organisation can require a second factor of its administrators, its finance staff or its HR staff. An administrator can create accounts from first and last names alone and print a sheet with usernames and temporary passwords, for staff without a work email address; each person finishes their account at first sign-in.

Members can download their own data, and administrators can export or erase the personal data of one member or one customer contact person. Contracts that the law requires in written form can no longer be signed electronically, and a policy in such a category cannot be acknowledged with a signature.

A new module gives each customer a portal of their own, signed into by emailed link. There they read and sign the documents shared with them, work through a guided onboarding on their phone, book an hour and send files. An organisation builds its onboarding journeys itself, including a website-intake starter that produces the legal notice from the answers, and assigns them from the customer’s record.

An organisation chooses a plan at sign-up and its owner manages it on a billing screen: billing address, payment and every invoice to download. Invoices are German e-invoices in the EN 16931 format (ZUGFeRD PDF and CII XML), a cancelled invoice is corrected only by a numbered credit note, and a reminder is sent before an unpaid subscription is suspended.

Spaces is a knowledge base for handbooks, runbooks, policies and notes, in which every page can carry its own permissions. Pages link to each other and to records elsewhere in Enclessa, and a map draws how pages, people, projects and customers connect.

The Calendar module brings events with recurring series and exceptions, attendees and their answers, free-time search and a slot finder, shared and delegated calendars, bookable rooms, five views and an event typed in one line. Dates from other modules appear beside your own, calendar files can be imported and exported, and a subscription link keeps Outlook up to date. Google calendars connect two ways and iCloud calendars are mirrored, and when both sides changed the same event the losing version is kept for you to decide.

Changes are written back to a connected calendar only where somebody switched that on for it.

The Finance module connects an organisation’s Lexware Office account: contacts in both directions, invoices and other documents mirrored onto the customer, a dashboard of receivables and revenue, and offers written in Enclessa and sent once. Booked hours become an invoice draft, and an hour can never be billed twice. Recurring invoices are linked to the customer, and every push to Lexware Office shows what became of it.

Nothing reaches Lexware Office without a person deciding it; drafts are never finalised automatically.

An organisation can connect AI assistants that speak the Model Context Protocol. A person signs in and consents to the areas the agent may use, and an administrator decides per tool what is allowed. The agent sees only what that person may see, and every change it proposes waits for a person to approve it before it runs.

The Mail module connects an organisation’s mailboxes and grants them to people, teams or everyone. It has an inbox with folders, rules, search and bulk actions, a composer with templates, attachments, appointments and contracts, sender identities with their own HTML signature, and a conversation can be filed onto the customer it is from. Outgoing mail is signed so receiving servers can verify it.

The Contracts module drafts agreements from a clause library and starter templates, including a data processing agreement whose annexes are structured data rather than prose. A readiness report says what is still missing, a draft goes to somebody who may sign it, approving it issues and signs it with a signature recorded once, and an issued document is frozen and numbered. Notice dates appear in the calendar and warn before they pass, and documents can be filed with the customer they concern.

The Companion, in beta, is an assistant inside Enclessa that answers from customers, projects, time, contracts and, where an administrator allows it, mail. It can draft a contract, a customer note or a time entry, but every change it suggests is a proposal a person accepts. It can also run a question on a schedule and leave the results in a review inbox, says clearly that it is an AI system, and marks what it drafted as AI-generated.

The whole web app is available in German as well as English and renders in the reader’s language from the first page load. Tables can be shaped — columns chosen, ordered and sized — and keep that shape.

An organisation can now keep the companies it works with — contacts, addresses, an activity log and a follow-up date — without installing time tracking or anything else. Opening one customer shows the projects being run for them, the hours those cost, the appointments they booked and the last thing anybody said to them, assembled from whichever modules are installed. A customer can be a company or a person, and the financial fields are absent rather than blank when nobody may see them.

Projects no longer belong to the Time module. An organisation can say what it is working on, who owns it and what it owes by when, with milestones, status updates, risks, decisions and files on one screen alongside the project’s room and its boards. An organisation that also runs Time decides per project whether it appears there at all, and switching a project off stops it accepting new hours without losing any hour already booked. Links pasted into a room months ago still resolve after a project is renamed.

A new agenda view collects what is actually on somebody’s day from six sources at once — appointments, milestones, absences and the rest — instead of asking them to check four screens. Appointments gained an owner and a project to book against, a completed appointment offers the hour it took, and a board can carry a project so a timer started from an item knows what to book against.

The day strip on the week board was planned for this step and was not built; it is recorded as deferred rather than done.

Dropping a link to a board item, a project, a person or a time entry into a room now shows a card describing it rather than a bare URL, resolved for the reader according to what that reader is allowed to see. Typing # in the composer searches across sixteen kinds of object and mentions one in a sentence. Boards learned what they cost — hours appear on the item and a timer starts from it — and notifications from every module arrive in one clickable inbox.

Every employee gets a card derived from the employment in force on the date being asked about, which they can fill in themselves and send to a customer who saves the contact without signing in to anything. Each card carries a per-organisation signature, so somebody at reception can check that this person works here and in what position — and on the day the employment ends, the same check says so without anybody having revoked anything. A manager sees their report’s card and not their pay.

Wallet passes, the email-signature generator and batch printing were deferred and are not available.

Registration no longer asks anybody to choose an organisation first: the account, the organisation and the first membership are created together and the organisation is named from the username, then renamed in settings. Each organisation lives at its own address, and somebody who belongs to more than one switches between them from the rail without signing in again, seeing in each exactly what that membership allows. Sessions moved to a host-only cookie the browser will not hand to another organisation.

The organisation is now asserted at one choke point rather than remembered at each call site, and a request for another organisation’s object is answered with a not-found rather than a forbidden — because a forbidden confirms that the object exists. A probe suite generated from the API description drives every operation across the boundary and asserts that all of them refuse: 203 driven, 203 refused. It runs on every build, so a regression fails continuous integration instead of reaching anybody.

Each organisation now has exactly one owner, enforced by the database and transferable, above an administrator and member ladder. On top of that, an organisation defines roles of its own over an organisation-level permission set, and a role can never carry a permission its author does not hold. The member roster, invitations, role changes and removal all moved into the organisation’s own settings.

The surface Enclessa operators use became a separate identity with its own sign-in, mandatory second factor, sessions and audit log. It can list organisations, see counts and states, suspend one and schedule a deletion — and it cannot read a message, a file or a personnel record. That is enforced by a check in continuous integration that forbids the control-plane package from importing anything capable of reading content, so it fails the build rather than a policy review.

The controls that matter after signature rather than at it. Rate limits apply per organisation and scale with seat count, with each member capped at a share, so one runaway integration cannot exhaust everybody else’s budget. Storage is accounted per organisation, retention is configurable per organisation with a default that keeps data, every metric and log line carries the organisation it belongs to, and an organisation can export everything the platform holds for it at any time.

Finer-grained retention per team and per channel, and export of the audit log to an external sink, are planned work and are not available.

Somebody can now be hired before they have an account. The People module holds employee records with effective-dated employment and compensation, organisational units, positions, locations and cost centres with a chart drawn from them, documents with versions and acknowledgements, self-service change requests, and onboarding and offboarding workflows that drive the other modules. Field visibility resolves across seven roles, so a manager sees what a manager may see and no more.

Somebody clocks in, takes a break, clocks out and sees the right balance — computed from a ledger rather than stored in a column, so it can be shown line by line. Hours book against a customer’s project, an activity, a board item or a pull request; a week is submitted and a manager returns it; corrections supersede rather than overwrite; and holiday is requested against an entitlement that can be explained. An organisation that has not installed Time sees no navigation for it and answers not-found to every one of its routes.

Time tracking gained the four views it could already compute and not show: a week board where a timesheet is drawn and dragged instead of typed into a table, an hours account showing a year month by month and day by day, an absence planner covering everybody the viewer is allowed to see, and a personal list of what was requested and what came of it.

The absence planner is read-only by decision, not by omission.

Optional surfaces stopped being feature flags and became installable modules. An administrator installs, suspends, resumes or uninstalls from a single catalogue page; each module gets a settings screen generated from what it declares; changes are stored as revisions so an earlier one can be rolled forward as a new revision rather than edited over; and an uninstalled module keeps its history for thirty days before it is purged. A module that is not installed answers not-found to every one of its routes.

A decision made in a room turns into an item on a board, moves through columns the team defined, and appears as a table, a board with drag-and-drop, or a roadmap — the same items, three ways. Items carry fields, assignees, tags, dates, comments and a link back to the room they came from, and saved views keep whatever arrangement somebody works in.

An administrator connects GitHub once and a board mirrors a project: cards arrive in the columns the team named, each showing whether its pull request is merged and whether its checks are green. Credentials are sealed rather than stored, webhooks are verified and logged, redelivery is idempotent, and an organisation can stop every outbound write with one setting without unlinking a board or revoking anything.

A sync against a live GitHub organisation has not been run — the credential for it does not exist on the build machine — so the connector is verified against a GitHub that actively refuses rather than one that accepts.

A script holding a token can post as a bot into a room it was added to, a build system can post to a webhook URL with no account at all, and the built-in slash commands work in the composer alongside custom ones an organisation registers against its own HTTP endpoint. Tokens are scoped to named operations, and none of the three reaches the administration console.

Status with an expiry, do-not-disturb, quiet hours and out-of-office now hold in email and in push rather than only in the interface. Keyword notifications reach somebody about a word they care about without their name being used, custom groups can be mentioned as one, a message written at midnight can be scheduled to arrive at nine, and a missed-message digest arrives by email.

A pasted link explains itself without being clicked — fetched by the server behind protection against being pointed at internal addresses, never from the reader’s browser. Voice messages record, show a waveform and play back inline, mathematical notation renders, and a file somebody sent last month is findable by a word inside it rather than only by its name.

Calls run in any room and ad hoc: a stage with tiles, device pickers, screen sharing, in-call chat, reactions, raised hands, a lobby, host controls and an incoming-call ring. An ad-hoc call’s link works for somebody who was not rung. Media in encrypted rooms carries a key bound to the room’s own group rather than one the media server holds, and that handover was demonstrated between two browsers.

No call has been run at fifty people. The load harness exists and the test has not been executed, so Enclessa publishes no measured figure for call size. Recording exists for managed rooms and produces no downloadable file.

Direct messages and group direct messages are end-to-end encrypted with MLS, the IETF standard published as RFC 9420, implemented with OpenMLS and compiled once in Rust so every client runs identical cryptographic code. Each device is a separate member of the group: adding one is visible, and revoking one re-keys the conversation so it can decrypt nothing sent afterwards. Attachments are encrypted with the message, devices are cross-signed, both sides compute the same safety number, and search in encrypted rooms runs on the reader’s own device against a local index because the server has nothing to index.

A second device of the same user does not yet sign itself: the identity key stays on the device that minted it until the encrypted key backup has an interface. The backup itself is built.

A team can express that a shelf is for these people, that a room is read-only, and that these three may notify everybody — without an administrator touching a database. Permissions are a bitmask evaluated in the data layer rather than hidden in the interface, teams name roles of their own over it, and allow-or-deny overwrites apply per category and per channel. Who is in a public room is derived from the permission rather than maintained by hand.

Sign-up, invitation, email confirmation, password reset and changing your own password all work, with single-use tokens that are stored only as hashes, so somebody who has forgotten their password does not need an administrator to get back in.

The first usable Enclessa: teams, channels and threads with reactions, edits, deletes and mentions; messages arriving live over a WebSocket rather than on a refresh; uploads with thumbnails and malware scanning before anybody can open them; full-text search across messages; an activity feed with notification settings; an email pipeline; and an audit log of administrative action.

The first working system: the database schema and its migrations, the API with a generated OpenAPI description, authentication with a device registry, telemetry, the design tokens the product is built from, and continuous integration — including the licence gate that fails the build if any runtime dependency stops being open source under an OSI-approved licence.