Back to release notes
2026.11.03

Push Notifications, Error Workflows, and Secrets in the Vault

Mobile and web push, error and event workflow triggers, per-app sign-in methods, secrets moved to Blocks Secrets, and zip download in Storage.

OSIAMDataLogicLocalizationUtilitiesReleaseMonitorStudio
OS

Notifications now reach phones and browsers through mobile and web push, and each notification chooses who gets it and on which channels. Workflows get an Error Trigger, a Blocks Event trigger and Filter and Limit nodes, and schedules can run in your own time zone. Projects control which sign-in methods each app may use. Client, OIDC, identity provider, mail and authenticator secrets now live only in Blocks Secrets. Storage adds zip download and bulk sharing.

Some changes refuse calls that used to work, and authenticator-app MFA must be set up again. Read Upgrade notes at the end before you update.

Notifications

Previously, a notification went to the in-app inbox and live channel only, and the recipient choices were hard to read. Now each notification says who receives it and how, and it can go to phones and browsers.

  • Mobile and web push: The new Push settings page (/notification/push) turns on push for Android, iOS and Web. Upload your Firebase service account key, or choose Enter manually and type the project ID, client email and private key. The project ID is read from the key, and you get a warning when a new key is for a different Firebase project. After setup, a switch pauses or resumes push, and each platform can be turned off on its own. A Test sends to your own devices and shows the result per device, and Registered devices lists the project's devices with a remove action.

  • Push per notification: The notification form picks the push platforms and the push title and message. Type a key from the Localization notifications module, or type the text itself. Each user gets the text in their own language.

  • Recipients in two choices: All users, or Targeted. Targeted combines an Owner tick (the user the event is about, on by default), a Done by tick (the user who did the action, off by default), and picked users, roles and permissions. A Targeted notification that would reach nobody is refused, and a built-in set to All users shows a warning. Match offers two clear choices next to the lists it combines.

  • Audiences and channels renamed: Audiences are now Consumer users and OS users. The channels are In-app, Push and Offline (previously "Save to inbox"), shown together in one Delivery channels column.

  • Turn off any notification: A project can turn off any event it doesn't need, including built-in job and progress events. Turning off one that a page waits for shows a warning.

  • Built-ins keep your settings: When the platform changes a built-in notification, a project keeps its own recipients, channels, push message, rate limit and on/off state.

  • Addresses: Notification pages now have their own paths (/notification, /notification/new, /notification/<id>). Old ?notificationEdit= links redirect.

Identity

  • Choose how people sign in: IAM settings → Sign-in methods turns the app's own login form, the IAM login page, password sign-in and social sign-in on or off for the project. Each OIDC application can narrow that further: Sign-in method Default, Password or Social, and social providers Default (all enabled) or Selected. The login page shows only the allowed methods, and the application list shows each app's sign-in summary. A refused sign-in returns 403 login_method_not_allowed. Saving a policy that would let nobody sign in is refused. API: GET and POST /iam/login-policy.

  • Admin password reset without a captcha: Previously, Reset Password in the OS console used the public forgot-password flow, so admins got "Captcha verification is required" on projects with a captcha. Now it uses POST /iam/users/reset-password with its own permission, blocks-iam::iam::reset-user-password. A user gets at most one reset mail per minute, and the link goes only to the user's mailbox.

  • Secrets kept in Blocks Secrets: Client credential secrets, OIDC client secrets, identity provider secrets and authenticator-app (TOTP) secrets are now stored in Blocks Secrets, and the records keep only a reference. Existing client and provider secrets move over on their next edit or rotate, so applications that hold them keep working. When the store can't be read, token calls answer 503 temporarily_unavailable, never "wrong secret".

  • Stronger MFA and password checks: Each MFA code and change-password attempt is counted before it runs, so guesses can't be sent in parallel. Email MFA codes and Blocks CAPTCHA codes work only once, and reset codes are stored hashed. Authenticator setup no longer keeps a QR image file, and turning MFA off needs a fresh code.

  • MFA page: The MFA step has a way back to sign in, a resent email code goes to the right project, and the profile no longer shows a "None" MFA row.

  • Signup links: A signup link must use a client that is registered as a Blocks OIDC identity provider. The console greys out other clients and says what to fix. Invitees set their password on the invitation page and land in the app.

  • Social providers: The identity provider form shows the IAM redirect URI to register with the provider, and IAM checks it against the provider's configuration. Inactive OIDC clients are refused.

  • Sign-in fixes: A signed-out device is refused on its next request instead of when its access token expires. A refresh stays in the project of the token it presents. A member of the default organization can switch into it on a multi-organization project. Signed-out users return to the device page after login. The OIDC error page uses the project's theme, and "Back to Sign In" works without a client.

  • Access attributes on user details are hidden in the console for now. Rules that use Auth.Attributes.<name> keep working.

  • If an invitation mail fails, the inviter is notified.

Workflow

  • Error Trigger: In Workflow Settings → Alert, a workflow can name an error workflow. When a production run fails, that workflow starts at its Error Trigger node with the failed run's details. The panel shows the output structure. Turn on Run on test mode to also start the error workflow's draft when a full test run fails. Step tests never send an alert.

  • Blocks Event trigger: A new trigger starts a workflow when a Blocks service sends a platform event, such as a user change in IAM or a payment status in Utilities. The new Event Triggers page lists the project's events and turns each one on for workflows. Every published workflow that uses an event runs once per event. Publishing fails while the chosen event is off, and turning an event off stops its published workflows. New projects get the event catalog. There is no editor test run for this trigger yet.

  • Filter node: Keeps only the items that match all (And) or any (Or) of its conditions, and passes them on unchanged.

  • Limit node: Keeps the first or the last N items.

  • Node panel by category: The node library has All, Triggers, Logic, Transform and Actions tabs, and nodes are grouped under those headings.

  • Schedules in your time zone: An application schedule can use any IANA time zone, with daylight saving handled. The form has a searchable time zone picker with Use my timezone and a Next runs preview of the next three runs. Existing schedules stay on UTC.

  • Schedule history: A new Executions tab lists every run of an application schedule with its HTTP status and response body (up to 16 KB). Signing secrets and header values are hidden.

  • Faster function runs: Deployed functions now run in warm, reused sandboxes by default.

  • Fixes: Test step saves the trigger's pinned or sample data before it runs. A deploy that is still building shows again after a page reload. A lost function event stream recovers without a restart. The code editor grows with its content.

Data

  • New validation rules: A rule can apply only when a condition is met (only when). New types are In and Not in a list, Min items, Max items and Unique items for lists (also lists of objects), and Must not exist in another schema. Date rules can compare with today, for example {{Now-30d}}. A Reference rule can filter its target, and can point at a system entity such as users. The editor groups targets as project and system entities.

  • Schema description: A schema can have a description of up to 500 characters. It is shown in lists, carried by export and import, and used as the GraphQL type description.

  • Rule editor: A rule's fixed value is entered by the property's type. Secret fields of system entities are never offered.

  • Fixes: Data-triggered changes carry the caller's delegated access.

Storage

  • Download as zip: Select several files and folders, or a whole folder, and download them as one zip. A Drive-style panel shows the download's progress. The API is two calls: POST /objects/download-zip/prepare with fileIds and directoryIds (up to 1,000), which checks access and returns a single-use ticket, then GET /objects/download-zip?ticket=…, which streams the zip. The prepare call needs blocks-data::object::download-zip.

  • Share many at once: The selection bar has a Share button that shares up to 50 files and folders with up to 50 users, roles or organizations in one step. API: POST /objects/share-objects.

  • Storage requests are now checked by their validators.

OS

  • Mail templates: Template HTML is checked on save and clone. It may not contain active content, must use https, and may link only to the project's own domains or {{placeholders}}.

  • Domains: An application domain that another project already uses is refused.

  • Mail and service bus secrets: Mail passwords and service bus connection strings are stored in Blocks Secrets. Existing configurations move on their next save, and a duplicated configuration gets its own secret. New projects get their own copies of the mail secrets instead of a plain-text password.

  • Default mail configuration: The default mail configuration can't be duplicated.

  • Fixes: The user-exists check refreshes after an invite, grant, revoke or user update.

Deployment

  • Custom domain only: Once a repository has a custom domain, Deployment Settings offers Default and custom domain or Custom domain only. It applies from the next deployment, and the repository and build pages show the default domain as not deployed.

  • Saved code analysis per build: Each build keeps its own SonarQube (SAST) and Dependency-Track (SCA) results, so an old build shows the results it had, not today's. A scan step that failed or didn't run says so.

Observability

  • Alert recipients page: Monitor → Alert recipients manages who gets alert emails in one place. Add a person to All monitors or to Selected monitors, with member suggestions, and remove with Undo. New monitors and heartbeats start with the All monitors people. Each monitor takes up to 10 emails. Monitor details show recipients read-only with a link to the page.

Localization

  • Glossary-aware AI suggestions: Single-key AI suggestions can follow the project glossary. Suggestions are checked against the glossary and retried once, and any remaining problems are listed under the field with Fix or Retry. Saving is never blocked. Glossary entries gain Variants and a Case-sensitive switch. This is off by default and turned on per deployment.

  • Glossary pages: Adding a glossary entry, the glossary details page and glossary selection in the key editor are redesigned.

  • Large key lists: The key list pages through keys faster and the All view scrolls smoothly with many keys.

  • Fixes: Auto translate all uses the right default language, and badges have readable contrast.

Utilities

  • OneDrive and SharePoint: A new API connects a user's OneDrive or SharePoint to a project. Browse, search and create folders, import files into Blocks Storage, and upload Blocks Storage files back to the drive.

  • Subscriptions:

    • One trial per plan (on by default) ties a trial to the organization, so a colleague buying after the trial goes to paid checkout. Turn it off for plans that may be trialled again.

    • Subscribers can Change card, and the billing contact gets a mail before the card expires.

    • Credits can have a fixed lifetime in hours, days, weeks, months or years, and the credit price currency is picked from a list. New credit terms are offered to existing subscribers.

    • Invoices show the organization name, the card's last four digits, expiry and holder, and line periods that end on the last day of service.

    • New weekly revenue and recurring revenue trend reports.

    • Fixes: seats added during a trial are no longer charged.

  • PDF: Caller HTML renders with scripts off and a 30-second limit, and template values are HTML-encoded. The wkhtmltopdf engine (engine 4) is removed.

Studio

Studio now starts from the project, not a single app, and checks what it draws before it builds.

  • Project setup: Set up a project in a short conversation before its first app. The project profile reads as a brand sheet, keeps the logo and pictures in project storage, and every new app starts from it. Setup ends with the apps the project needs, planned and ready to start. Apps in a project know their siblings and the records they share.

  • Plans you can trust: Every feature says which parts of Blocks it uses, why, what you must supply, and who may see and change each record. A new request gets its own plan and a change to a built feature gets its own change request. The planner asks before it takes anything out, and the plan page shows what a change removes and why.

  • Designs checked in a browser: Drawn designs are opened in a browser, graded as blocker, medium or minor, repaired once, and shown with real thumbnails. A progress bar shows each screen's check. Select on a design lets you swap alternatives, edit words in place, move, remove or add a note. Redraw is one menu: this screen, all screens, or remove from the plan.

  • Designs become screens: Studio turns a build's designs into React screens itself and checks each one before the builder wires them. After a build, Studio looks at the screens it changed as each role, using sample records. A built screen that differs from its design is shown beside it with Match or Keep.

  • Sign-up from Studio: Studio can change who may sign up to the project, previewed with a dry run and saved only after you confirm. The way in is one Sign in button, labelled Sign in or create an account while sign-up is on.

  • Chat: Attach files and pictures to a message. Snap on Preview takes a picture of the current view or an area in your own browser, and you can draw on it. The assistant asks fewer, sharper questions, and the closing card leads to the next step.

  • Websites: A website's first version offers its pages and links sign-up to the project's app. Its content is edited in an editors-only area, not the Blocks console.

Developer SDKs

  • genesis-net 4.4.7 to 4.6.0 (26 October to 3 November):

    • Notifications (4.6.0): A notification publisher and worker send through In-app, Push and Offline channels, with a push template and the All users and Targeted audience rules, including Done by.

    • Blocks Event Trigger: Enabled catalog events are forwarded to the Workflow event trigger queue.

    • Signed-out sessions: An access token whose session was signed out is refused with session_revoked.

    • Origins: Outside Development, only https origins pass CORS and the project origin check, and localhost passes only in Development (4.5.0, 4.5.1). The Referer header is no longer used.

    • Validation rules: Conditional, list and relative-date rules, reference filters and Must not exist in.

    • Entities for sign-in policy, Blocks Secrets references, schedule time zones and history, error-workflow settings and custom-domain-only deployments.

    • Aborted and malformed requests return 4xx or 499 instead of 500.

  • genesis-react 4.4.4 to 4.4.7 (26 October to 2 November): The console UI is translatable. Its language list comes from the project's languages, the selector hides when there is only one, and a user's choice is kept. The session lock is released when a call never answers.

  • genesis-py 4.0.0 (28 October): The Python package is renamed seliseblocks-genesis-os and restarts at 4.0.0, in line with the other SDKs. It is now published to PyPI from CI.

CLI

No new CLI release this week; @seliseblocks/cli-os stays at 0.11.0. The agent skills moved out of the CLI repository into their own blocks-skills repository, with their history.

Upgrade notes

Authenticator-app MFA must be set up again. Authenticator (TOTP) secrets are now kept only in Blocks Secrets, and the old stored secrets were removed. Users who signed in with an authenticator app must set it up again. Email MFA is not affected.

New permissions. Add these to the roles that use these features, then sign in again so the token carries them.

Service

Endpoint or action

Permission

Identity

POST /iam/users/reset-password (new)

blocks-iam::iam::reset-user-password

Identity

GET and POST /iam/login-policy (new)

blocks-iam::iam::mutate-tenant-configs

OS

Mail template save, clone, get and delete

blocks-os::mail-template::save, gets, delete

Workflow

Mail SendToAny

blocks-logic::mail::send-any

Workflow

BlocksEventTrigger/* (new)

blocks-logic::workflow::read, manage

Storage

POST /objects/download-zip/prepare (new)

blocks-data::object::download-zip

Storage

POST /objects/share-objects (new)

blocks-data::object::share-object

Calls that are now refused or behave differently.

  • http and localhost origins: Outside Development, browser calls from an http:// page or from localhost are refused. Serve your app over https, or use a Development environment for local work.

  • Sign-in methods: When a project or OIDC application turns a method off, sign-ins that use it get 403 login_method_not_allowed.

  • Test mail goes only to the caller's own address, and a send with SendPhoneNumberAsEmail keeps only addresses that match a user's stored phone.

  • Mail templates with scripts, http links or links to other domains are refused on save.

  • Application domains already used by another project are refused.

  • Monitor alert emails: emails is no longer read on monitor and heartbeat create or update. Use the Alert recipients page or its API (Monitor/SaveAlertRecipient).

  • Push devices: a user can register at most 10 devices. Devices not seen for 60 days stop getting push.

  • Removed notifications: lmt-restore-status, os-lmt-restore-progress, os-certificate-changed, os-project-disabled-or-deleted and os-secret-changed are no longer sent.

  • PDF: Scripts in caller HTML no longer run, a render stops after 30 seconds, and engine 4 (wkhtmltopdf) is removed.

  • Python SDK: install seliseblocks-genesis-os instead of the old package name.

Related entries