Skip to main content

11–29 October 2026

Applies to: SimpleTwo 0.9.325–1.0.19 · directory up to 1.3.16 · agent up to 1.0.8 · apps: iOS 1.0.7, macOS 1.0.8, Android 1.0.6, Windows 1.0.6 · Checked: 29.10.2026

The headline of the period is release 1.0. The directory became the one source of people, groups, roles and sign-in; the coordinator no longer keeps users of its own and signs nobody in itself. Changes are grouped by functional area; in each, new features come first, then fixed defects.

Release 1.0: the directory is the source of people and sign-in​

New features

  • Sign-in through the directory only. The apps on every platform and the console sign in through the directory; the coordinator has no sign-in and no passwords of its own any more. Sign-in starts with the address: the domain decides the organisation, an address without one is a local account.
  • Permanent identifiers. Every account, group and role now has a permanent identifier issued by the directory. The login became an attribute: renaming an account keeps its files, messages, mail and rights, and the former login stays reserved for it for a while. Every service — messaging, mail, the drive, the MCU, support — keeps people by that identifier.
  • Roles and assignments live in the directory only. What a person may do in the console and in the services is the directory's decision; the services read it from one projection. The built-in groups Simple Users, Simple Guests, Simple Partners and the others are bound to the built-in roles.
  • Guests after the move. A guest signs in with an invitation card: its life is a policy setting, its link opens the directory's page, and the inviter is notified. A guest can redeem the card, remind the inviter, and recover access with a code from them.
  • The emergency local administrator and the administrator's personal access tokens live in the directory; administrative operations that outlive a request run under a grant issued for them, and the log names the person.
  • The organisation's tree, address books and address lists. Organisations and departments, address lists and the Global Address List are directory objects; who sees whom is decided by the address book policies. The organisation's address book is available over CardDAV.
  • An account's addresses. A person has work phones, mail addresses and SIP addresses, one primary of each kind; the SIP address defaults to the primary mail address, the internal number is the work phone's extension.
  • The installation's objects. Servers, services, sites, policies and address lists are directory objects modelled on Active Directory, with their own attribute schema and SCIM 2.0; policies resolve into a resultant set across "root → organisation → department → group → account → device".
  • Directory profiles base, simpletwo, calendar; the schema extensions of the line's platforms are registered when a platform is switched on.
  • Directory replication. A directory instance in another metaspace becomes a replica of the installation: a change feed over SCIM, attribute versions, a schema master; deleted rows are kept for 14 days.
  • Meeting rooms and devices. A room's devices (SIP, panels) are "legs" of the room account in the directory; the MCU decides by their replica. A Poly Trio gets the room's calendar over EWS.
  • Quotas in the directory. Quota templates are the directory's policies: given to the organisation, a department, a group or a person, the smaller order winning among several, as a Group Policy's. A shared mailbox gets a template by its address. See Quotas.
  • The migration tool upgrade1 moves a 0.x installation to 1.0: accounts, guests, bots, rooms, roles, policies, address books and the Secure Access objects.

Fixed defects

  • AD FS refusing a known account is no longer reported as "wrong password".
  • Sign-in through an upstream provider links the account by the provider's subject before the login.
  • A guest's second invitation card reaches the inviter.

Console​

New features

  • A new menu. The first level is Overview, the platform's products, Users, Security, Settings, Logs & audit; each item has a row of its parts. The organisation's logo and name sit in the top strip with the platform switcher, the person on the right.
  • The directory is parts of the console, not an embedded page. Users holds the directory's people, guests, groups and bots, the organisation's structure, rooms and devices, roles and the address book. A new Security item gathers the sign-in requirements, the sign-in page, applications, synchronisation (LDAP, HRMS, SCIM, webhooks), access reviews and emergency access. The directory's sign-in log and audit are under Logs & audit, the schema under Settings → Directory, what needs attention on the Overview. The directory has no console of its own any more.
  • The platform switcher (SimpleTwo, SimpleThree and the line's other platforms): host lists, the role picker and administrators' rights narrow to the chosen platform.
  • The "Add a role to this host" wizard and the multi-role agent: several roles on one host.
  • People are shown by name and login everywhere, never by identifier; rule lists have a short name and a separate description.
  • The console's long lists page and filter on the server; settings sit beside what they affect.
  • The "Current tasks" dock can be resized.
  • Every console field is checked by one rule contract shared by the console and the service.

Fixed defects

  • CLIENT SESSIONS and the rule lists no longer show opaque identifiers.
  • The Settings row of parts no longer wraps.

Secure Access​

New features

  • Everything in the directory. Gateway groups, GEOs, third-party gateways, rulesets and rule lists are directory objects. Which ruleset and gateway groups a person gets is decided by a routing policy linked to everyone or to a directory group, with a link order; the tunnel profile works the same way, with a personal layer and a device layer. See Access network.
  • Large rule lists. A small list is kept in its object, a large one as a file beside it (up to 64 MiB).
  • Nodes in the directory. A node joins the directory as a computer joins a domain; a gateway has its own service account. The gateway takes its configuration and its admitted clients from the directory itself, while still reporting liveness and load to the coordinator. The directory keeps the tunnel sessions.
  • Third-party gateways over IPsec (FortiGate and other IKEv2): the server proves itself by a PSK or a certificate; the apps on every platform bring up a tunnel to it and show its state; the corporate gateway's login is remembered and asked again when refused.
  • Secure Access counters by route — the GEO tunnel, the corporate tunnel, direct.
  • An IP/CIDR or domain field with a wrong value is refused at save and never reaches the tunnel.

Fixed defects

  • The IPsec handshake waits for each answer and repeats a request.
  • A refused tunnel plan is shown and not retried until the plan changes.
  • A gateway whose directory is briefly unavailable keeps its admitted clients.

Calls, MCU and telephony​

New features

  • Internal calls by SIP address, device digits by the dial plan and reverse lookup; only a telephone number is presented to the carrier; the From to a room's device carries no account identifier.
  • Several PSTN gateways without a shared bus: one gateway per trunk.
  • A call room's life in one service: a chat on every call, the room history with types, live rooms; the apps learn from the core which service runs a room.
  • MCU: names and indicators on the room's picture, the recording announced, a room calls a person and a person calls the room, a device behind NAT, SRTP keyed in the SDP, recent calls, an SRV domain per country and site, a site certificate, a device's video cut to the meeting's limit instead of dropped.
  • A room's device is bound by the certificate the MCU verified; device enrolment is a window that shuts itself.
  • A meeting room's extension on the main number; a retry with its own prompt and a free-room prompt.

Fixed defects

  • A device no longer hangs after the SDK's callbacks.
  • Poly VideoOS calls: SRTP-only streams are refused by name, keyframes are requested over SIP INFO.

Messaging, mail, drive and calendar​

New features

  • People for messaging and mail come from the directory only; who may start a conversation is decided by the directory's address book.
  • Unsent messages are drawn in place with the person's actions; a repeated send answers about the past instead of sending a duplicate.
  • Meeting reminders are made by the app itself; a meeting opens with one tap.
  • Calendar: each participant's own copy of a meeting, cancelled meetings and cut series, tasks and attachments.
  • Drive: ranged downloads, picture view, visible uploads, a note on what will vanish from a device.
  • The manager and contacts break through Do Not Disturb again.

Apps​

New features

  • Windows 1.0 — a full client: messaging, calls (raised hand, reactions, host rights, DTMF keypad), mail, files, calendar, contacts, VPN with automatic reconnection and third-party gateways, sign-in through the browser and approval by number, updates on its own, a Group Policy template (ADMX) for the organisation's server address.
  • iOS, macOS, Android 1.0: sign-in through the directory only, invitation links, "My guests".
  • Forwarding a message with a picture works; the recipient list shows the login or the status, not an identifier. A picture can be copied, pasted, saved (on iOS — to Photos) and zoomed.
  • Android: calls on the lock screen, markup and links in messages, forwarding several messages, files and calendar as on the Mac, a tunnel watchdog, the invitation QR scanner.
  • The apps measure their own resource use and send it to support with a problem report.

Fixed defects

  • Mac 1.0.0 crashed on sign-in through the browser.
  • A conversation no longer opens as an empty pane under its messages.
  • No app shows an identifier in place of a login.

Support and monitoring​

  • The support role asks the directory with its own key and reads diagnostics through a read token.
  • Client telemetry retention is a console setting; resource windows are kept 7 days, daily rows 90.