Changelog

What's new in Blocks

New features, improvements and fixes, shipped as they land.

2026.10.12

Versioned Schemas, Versioned Plans, and Faster Functions

DataLogicUtilitiesIAMOSMonitorReleaseLocalization

Versioned Data Gateway schemas with rollback, subscription plans you can edit with live subscribers, faster and safer Workflow functions, plus CLI 0.9 schema indexes and safer previews.

Data

Data Gateway schemas become versioned, auditable, and safe to roll back.

  • Schema version history and rollback: Every published schema change is now kept as a version you can review and roll back to, so a bad edit is a one-click revert instead of a manual rebuild.

  • Only published, validated snapshots go live: The gateway now serves only schema snapshots that have been published and validated, so a work-in-progress edit can no longer reach live traffic.

  • Every pod stays on the latest schema: A schema publish is now announced across all Data Gateway pods over Redis, so a multi-pod deployment can't keep serving a stale schema after you change it.

  • Reworked schema editor: The schema structure editor was rebuilt, with nested rule groups in the rule-set editor, enum editors that auto-focus, a unified style for field flags, and a principal selector with inline chips.

  • Analytics date range and bucket size: The graph analytics page gains a date-range picker and a bucket-size control, so you can scope the window and resolution of your charts.

  • Mobile layout: The schema header and playground now lay out correctly on small screens.

Workflow

Functions get faster, safer, and able to act as the caller.

  • Caller token on demand: A function can now request a caller-scoped access token at run time with await ctx.blocks.getAccessToken(), so it calls Blocks services as whoever invoked it instead of holding a static credential.

  • Faster functions: Warm calls are quicker, cold starts get a start-up CPU boost, and a function re-warms automatically after a restart. Deployment and invocation add artifact support and sandbox reuse.

  • Credentials stay out of functions and logs: Functions refuse literal credentials, revoke their run grants when they finish, clean up leftover envelopes, and support force-delete. Secrets are never written to notifier, notification, scheduler, or workflow logs.

  • Clearer editing: Workflow details show the workflow name in the breadcrumb with an actions menu, the output panel shows mock data with an indicator you can remove, and the HTTP node gains a None authentication option.

  • More predictable runs: A step with any failed item now fails, so the run ends Failed rather than reporting a success it didn't earn.

Utilities

Subscriptions gain versioned plans and a full billing-email story.

  • Versioned plans: A plan can now be versioned so it stays editable while subscribers are live on it, and existing subscribers keep the version they bought.

  • One trial per plan: Each plan's trial is limited to one per subscriber, closing repeated-trial sign-ups.

  • Emails in the recipient's language: Subscription notification emails are now sent in the recipient's language. Members are emailed when they are given or lose a seat, and billing contacts are notified on seat, plan, and cancellation changes.

  • Edit capture delay in the portal: A payment provider's capture delay is now editable from the portal, so Adyen auto-capture settles on your schedule.

  • Payment reliability: Stored-card charges now send the provider store, settlement reservations no longer block a cancellation, webhooks for references Blocks did not issue are acknowledged rather than erroring, and a recurring charge fails cleanly on a configuration error instead of hanging.

  • Leaner reconciliation: The subscription sweep now runs only for tenants that have subscribed and skips tenants with no database, so background work scales with real usage.

  • In-process PDF rendering: Template-engine PDFs now render in-process.

Identity

  • One password prompt, not two: An existing active user who redeems a signup link now confirms their password and arrives already signed in, instead of being sent to the sign-in page to type it again.

  • Email preferences: Admins can opt out of activation and organization-membership emails.

  • Safer redirects: Redirect targets are validated before a full-page navigation, so a crafted target cannot send a user off-site.

  • Console consolidated into OS: The admin and console pages that moved to Blocks OS have been removed from Identity, leaving one place to administer them.

Platform hardening

  • Configurable Content-Security-Policy: Data Gateway and Observability now build their CSP from configuration instead of hard-coded values, and the OS app uses a per-browser style nonce in place of unsafe-inline, tightening the browser security posture without hand-editing headers per service.

Deployment & Observability

  • Repo details: Deployment hides the Tracing and Logs buttons on the repo-details page, and Observability refines the SCA severity tiles and repo-detail styling.

Localization

  • Import migration fix: An issue in the localization import migration has been fixed, so bringing localization data across lands correctly.

CLI

@seliseblocks/cli-os 0.9.0 is on npm, with 0.9.1 rolling out.

  • GeoJson schema indexes (0.9.0): blocks data schema indexes list|create|delete manages Data Gateway indexes. A non-array GeoJson field gets a MongoDB 2dsphere index automatically and is reported separately as a read-only system index, and create builds custom indexes with --fields, --name, and --unique.

  • Case-sensitive field types caught locally (0.9.0): data validate, data schema push, and data schema fields now reject a miscased scalar such as string or geojson and name the right spelling (String, GeoJson) before the server does.

  • Safer previews and project targeting (0.9.1): new web --dry-run is now read-only and writes nothing, project selection is pinned per workspace so two terminals in different directories can't retarget each other, and a project token issued for the wrong tenant is detected and discarded instead of silently answering from the wrong tenant's data.

In 0.9.1 the CLI stops granting Public (anonymous) access to new data schemas. They now default to User (signed-in) access. Pass --access public to keep the old behaviour.

2026.10.4

Signup Links, Custom Domains, and Per-Person Plans

IAMOSDataLogicUtilitiesStudio

Release Notes

Identity gains signup links: invite someone with a link that already carries their roles, and they join in one click, through Blocks OIDC or from inside your own app. Custom domains now come with a guided setup that shows each step as it runs. Data Gateway adds an Enum field type. Subscriptions can be sold per person, with each person getting their own allowance. The CLI now covers proxies, schedules, custom domains, and GitHub connection.

Identity

  • Signup links — Under Identity & Access → One-Click Signup, you create a configuration that holds the defaults for one kind of invitation: roles, permissions, how long a link lasts, where the person lands afterwards, and whether they set a password (PasswordRequired) or join without one (Passwordless). Each link you then generate is tied to one email address, and its grant is fixed when it's made. A link is stored only as a hash and can be revoked one at a time or for a whole configuration. Generating a link checks that you're allowed to assign the roles it grants, so a link can't hand out more access than you have.

  • Two modes — Blocks OIDC mode sends the person through your registered OIDC client and back to its registered redirect URI. IAM checks that redirect when the link is generated and again when it's used. Embedded mode is for apps that run with OIDC off. Your app shows its own join screen, calls signup-links/context and signup-links/redeem, and gets the tokens back directly. IAM never redirects in this mode, because there's no registered client to check a redirect against. The configuration form shows only the fields that apply to the mode you choose, and the client is picked from a list instead of typed in.

  • Signed in on arrival — Previously, someone who accepted a PasswordRequired invitation set a password and was then asked to type it again on the sign-in page. Turn on Sign in after activation and they arrive already signed in. This works in both modes. The setting is on by default for new PasswordRequired configurations. Existing configurations are unchanged.

  • Multi-use links — A link can now be used more than once. Set maxRedemptions to a number, or to 0 for unlimited uses until the link expires. Leave it out and the link stays single-use, as before.

  • Link activity — POST iam/signup-links/summary returns, for each configuration, how many links were generated, used, never used, and rejected. It returns counts only, no link ids or email addresses.

  • Account state on the users list — Previously an invited, deactivated, or suspended user all showed as "Inactive". Each user now has one accountState (Active, PendingVerification, Suspended, or Deactivated), and the portal's users list has a Status column and filter. In the API, the accountStates filter also accepts LockedOut. Bulk role changes use the same filter. The existing active and status fields are unchanged.

  • Rotate client secrets — POST client-credentials/{id}/rotate-secret issues a new secret for a client credential and returns it once. Saving a client credential returns the secret only when the credential is first created. An update keeps the existing secret.

  • Client status in the list — The OIDC client list now shows an Active/Inactive badge and lets you enable or disable a client from the row, as the client credentials list already does.

  • Revoke default-organization access — In multi-organization tenants, you can now remove a user's access to the default organization from their Access tab. You still can't remove your own access.

  • Delegated access for services — A delegated-access grant can now name an OAuth client instead of a user. When it's redeemed, IAM issues a client_credentials token (with no refresh token) and checks that the client is still active. This is the server side of the Genesis (.NET) v4.2.3 change in the September 27 notes.

  • No more repeat activation emails — Revoking access, reinstating a user, or activating a social-login account used to send the user a new activation email, which looked like being invited again. Activation emails now go out only when a user is created.

  • Security fixes — If an OIDC redirect_uri doesn't match a registered client, IAM now shows its own login error page instead of redirecting to the supplied URL. The user-exists check (users/exists) now takes the email in a POST body instead of the query string. A GET on email/available returns 405. This keeps email addresses out of URLs and logs. If you call users/exists directly, switch to POST.

OS

  • Guided custom domains — Previously, adding a custom domain didn't tell you which DNS records to create or which API address to use afterwards. Setup now lists the exact records: a CNAME for a subdomain, or an A record with the target's IP for a root domain. It then shows verification, server configuration, and certificate issuance as they happen. Setup keeps running if you close the tab, and only one setup can run per domain at a time. The domains table shows each domain's API base URL. The connect step's Test now link opens your domain's IAM Swagger page, which loads only when the domain, its certificate, and the gateway route all work.

  • Archived and purged secrets — Secrets now have an Archived view with its own count. An archived secret stops working until you Restore it, or you can Purge it to delete it permanently, including from Azure Key Vault.

  • Connect with Blocks OS — An external site, such as a CMS, can send you to Blocks OS to connect it to a project. You sign in and pick a project and environment, or create a project on the spot, then approve the connection. The page waits until the environment is ready. If you have to sign in partway through, the request picks up where it left off. Connections are managed under Integrations (previously Connect).

  • Links survive sign-in — If you open a portal link while signed out, you're taken back to that page after signing in.

  • Project limit — You can own up to 10 projects. The server now enforces this limit, not only the console. A project's environments (dev, stg, prod) count once, and projects shared with you don't count. Adding an environment to an existing project is never blocked.

Data

  • Enum fields — Schemas get an Enum property type. You list the allowed values in the schema editor: up to 100, each 1–100 characters of letters, numbers, and underscores, not starting with a number, and no duplicates. Each Enum field becomes its own GraphQL enum type, so a value outside the list is rejected and clients can discover the allowed values from the schema. Enum fields can be filtered with eq, neq, in, and nin.

  • No more blank Data Gateway screen — Data Gateway could open to an empty main area when the project configuration loaded before the session. It now waits and shows a loading or error state instead.

Workflow

  • Reliable branching — When an If node splits items, only the branches that actually received items continue. A node that joins several branches now waits until every parent has either finished or can no longer run, so it runs once with all its inputs instead of early or twice.

  • Correct webhook responses — A webhook-triggered workflow now responds with the result of the last node that actually ran, following only the branches that received items. Previously it could pick a node on a branch that never ran.

  • Steadier parallel runs — When parallel nodes finish, each completion and the nodes it starts are recorded as one step, so a run can't skip a node or run one twice.

  • Execution history — The executions list and execution view were reworked, and the Transform Code node guide now has sections and worked examples.

Utilities

  • Per-person plans — A plan can now be sold to each person in an organization, not only to the organization as a whole. The organization buys places, and an administrator assigns each place to one person. Each place has its own allowance (for example, 100,000 AI tokens per month), and only the person holding it can use it. Overage is calculated place by place. When a person uses something, their place pays first, and anything it doesn't cover falls back to the organization's plan, so an organization can have both kinds of plan at once. A place keeps its usage when it's reassigned. People can see their own subscription with GET /subscriptions/mine. A service calling with client credentials can name the user whose place should be charged. See the per-person plans guide in the Subscription API documentation.

  • Flexible rate limits — A rate limit on a meter (for example, "at most 1,000 an hour") can now span several windows and be measured as a rolling window, and one meter can have several limits at once. The plan builder names the window each limit applies to, and warns you when a limit can never be reached because the plan's included amount is lower.

  • Better invoices — Invoices list discounts as their own lines, show a customer number and the masked card, and follow the standard financial-document layout. Financial-document PDFs are stored with organization-level access. Adyen subscription checkout now always saves the card.

  • PDF signature validation — A new asynchronous API checks the digital signatures of PDFs already in Blocks storage using the European Commission's DSS library. Send file ids to POST /pdf-signature-validations (202 Accepted), then read results with POST /pdf-signature-validations/status. You get a verdict per file and per signature, including the PAdES level reached. Trust comes from the EU List of Trusted Lists plus any extra trust anchors you configure. Only the revocation data embedded in the document is used. Files are never modified. A completion notification can be sent for each file.

  • Templates with nested data — The template engine now renders nested JSON objects and lists in template data.

Studio

  • A better model picker — The chat model picker is a fixed-height popover with Blocks provided and Your models tabs, search by model or provider, and grouping by provider. It now lists every chat model in the catalogue. Embedding models are left out because they can't chat.

  • Requests go to the right place — Studio now decides by what you mean, not by keywords, whether a message describes a new requirement (which becomes a feature) or asks for a build.

  • Fixes — Features can be edited again. Telegram file paths resolve correctly. The PRD document structure has been reworked.

Extension

The UILM Assistant browser extension (v1.2.0) can now create keys and publish from the side panel:

  • Add new keys — Create a localization key and its translations directly from the page you're working on.

  • Publish changes — Publish your localization changes from the side panel instead of switching to the portal.

  • Smoother sign-in — Fixed tokens expiring too early and the screen flickering during the Blocks sign-in flow, plus smaller UI fixes.

2026.09.30

Text Messaging Arrives, Workflows Get Secrets & a CLI

IAMLogicDataOS

Release Notes

Identity picked up account-security hardening with MFA, lockout, and captcha; Workflow gained a full versioning and publishing model; and the console shipped a guided wizard for moving a project into the new per-environment architecture.

Identity

  • Multi-Factor Authentication — A new MFA controller and services support TOTP setup and verification at login, giving users a second factor beyond their password.

  • Account lockout — Repeated failed sign-in attempts now trip an account lockout, and a captcha (HCaptcha or ReCaptcha, configurable per tenant) is required after failed attempts on both the embedded and OIDC login flows.

  • My Organization — Users get a self-service "My Organization" page, and the role/permission model now supports multiple organizations per user, including creating and switching between them from the console.

  • Unified auth settings — OIDC configuration is now exposed through a dedicated UI-config endpoint, and Identity's settings moved to unified tabs, retiring the older general auth configuration screen.

Workflow

  • Versioning and publishing — Workflows can now be versioned: authors create a new version, publish or unpublish it, and browse version history, with executions distinguishing draft from published runs.

  • Editor productivity — Nodes can be multi-selected, duplicated, copied, and pasted; a new "set variable" node was added; and the send-mail node gained dynamic key-value field mapping with template key extraction.

Data

  • AI-assisted validation regex — A new "generate validation regex" action in the schema editor turns a plain-language description of a validation rule into a working regular expression, so schema authors no longer need to hand-write one.

Blocks OS Platform

  • Guided environment migration — A step-by-step wizard walks a project through moving its data into the new per-environment architecture, with progress tracked so a user can see whether a migration is in flight or recently completed.

Extension

The UILM Assistant browser extension (v1.1.0) lets you manage localization setup from the side panel, not just translate keys:

  • Manage languages — Add a language from a built-in language catalog, make one the default, or remove one (the default can't be removed), from a new language manager menu.

  • Manage modules — Create, edit, and remove localization modules without switching to the portal.

  • Auto-translate everything — A single Auto-translate all action fills in missing translations across your keys.

  • Delete keys and smoother loading — Keys can be deleted from the key detail view, and new loading placeholders keep the panel steady while data arrives.

2026.09.13

Utilities, Identity Hardening & the Blocks CLI

IAMDataLogicReleaseUtilitiesLocalization

This release brings tenant-aware branding to Identity, richer schema and analytics controls to Data, a PDF ingestion engine and a redesigned plan catalogue to Utilities, and a major maturation of the Blocks CLI: / now at 0.5.0 with project source control built in.

Identity

  • Tenant-branded OIDC — The OIDC sign-in experience is now rendered from template data and branded per tenant across every flow. Branding is served from the database with the logo delivered over a CDN, supports light and dark themes, and the old per-client branding fields have been migrated out behind a protected management API.

  • Flexible activation — The activation password step is now configurable; when no password is collected, accounts activate on arrival. The signup page is served directly from the initiate endpoint with a flow=signup parameter.

  • Clearer SSO failures — A refused SSO sign-in is now surfaced in a blocking modal instead of failing silently.

  • Scoped tokens & filtering — Organization-scoped tokens can be minted with client credentials, and the users list can be filtered by role and organization.

Data

  • Schema index management — A new Indexes tab lets you manage schema indexes directly, with the default ItemId index shown correctly and an accordion UI for index display.

  • Graph Log analytics — Graph Log history and analytics can now optionally include Blocks Console operations, and impersonated tokens store their context in the activity record for a clearer audit trail.

Workflow

  • Export & import — Workflows can now be exported and imported, making it easy to move automation between projects and environments.

  • Mail configuration — Workflows can retrieve mail-server configuration and present a summary, and both the HTTP Request and data-action nodes can authenticate with client credentials or Blocks authentication.

Deployment

  • Project source control backend — Deployment now exposes GitHub push-credential and create-repo endpoints, the backend that powers the CLI's new blocks git source-control commands.

Utilities

  • PDF ingestion — A new PDF ingestion engine performs managed, in-process inspection of uploaded PDFs — readability, geometry, digital signature, and PDF/A conformance — through a per-file ingestion pipeline that reports a status verdict per file.

  • Protected billing endpoints — Subscription and payment endpoints are now guarded with [ProtectedEndPoint], machine callers are identified by their client id, and subscription reads carry quantity bounds.

  • Redesigned plan catalogue — The plan catalogue has a modern, animated visual design with improved presentation and accessibility.

Localization

  • WordPress integration guide — A new guide page documents configuring the Localization WordPress plugin.

CLI

The CLI matured rapidly from its August debut, moving from 0.2.12 to 0.5.0.

  • Project source control (blocks git) — New in 0.5.0: source control for the project's own code through the GitHub account connected in the Blocks portal — status, init, clone, connect, pull, push, and disconnect. Push credentials are fetched per command and never written to disk.

  • New command families — captcha and secrets families were added, along with 18 release commands covering the full deployment surface.

  • Safer edits — Save and update commands now read the current record and merge changes over it, so omitting a flag no longer wipes stored fields; an endpoint-verification tool checks every CLI route against the live service controllers.

  • Reliability & help — A generated blocks help reference, a passive update check that asks before upgrading, and fail-closed native credential storage round out the release.

Developer SDKs

  • genesis-os (React) v4.3.7 — Continued refinement of the shared OS app-shell and components across service applications.

  • Blocks Genesis (.NET) v4.1.7 — Ongoing v4.1 line updates to the .NET bootstrap SDK.

2026.08.26

Blocks OS Consolidation & Platform Hardening

IAMDataLogicReleaseOSUtilitiesLocalizationMonitor

The month after the Blocks OS launch focused on consolidating the new architecture and hardening it for production. Identity gained account-lockout and archive workflows, Storage matured its document model with soft-delete and sharing, Utilities introduced a full subscription-and-billing engine, and the Blocks CLI made its debut as a terminal control plane for the platform.

Identity

  • Account lockout, phase 1 — Repeated failed sign-ins now trip an account lockout, and the lockout state is exposed on the Users API — a backend phase ahead of console surfacing for administrators.

  • Archive roles & permissions — Roles and permissions can now be archived through dedicated endpoints, retiring them without deleting history. A console UI for archive actions is not yet wired up.

  • Role-change impact API — A new endpoint reports the impact of a role-permission change ahead of time — add/remove counts, affected organizations, and users holding the role — for a future console preview experience.

  • Organization improvements — Users can create an organization during signup, log out of all applications at once, and the my organizations view now reports the default organization and omits disabled ones. User email search also matches on a partial address.

  • Device flow, wired end to end — OIDC authentication completes the Device Authorization Grant with organization-scoped tokens and improved error handling.

Storage & Data

  • Soft delete & restore — Directories and files can now be soft-deleted and restored, so accidental removals are recoverable.

  • Shared content — A new shared-content capability exposes files and directories that have been shared, with permission checks enforced across every file and directory operation.

  • Schema validation — Schemas support required-field validation with a requiredOn property, and data policy rules now handle multiple right-hand operands against array fields for richer conditions.

  • Public GraphQL endpoint — A dedicated public GraphQL URL is now part of the runtime environment configuration.

Workflow

  • Blocks authorization on nodes — The HTTP Request node gained a Use Blocks Authorization option, so workflow calls carry proper credentials without manual token handling.

  • Raw query mode — The data-action node adds a raw query mode and new GraphQL field support.

  • Targeted notifications — User-specific notifications can be filtered by role and organization.

Deployment

  • Environment variables — Deployment secrets have been reframed as environment variables, with runtime variables enabled per release for clearer configuration management.

  • Monitoring in Deployment — Deployment now proxies the monitor list from the observability backend, bringing service health into the release surface.

  • Deployment lifecycle — Deployments can be deleted, project deletion triggers a queued teardown of its deployments, and pipeline definitions and cluster credentials are now sourced from Key Vault.

Observability

  • Pause awareness — Monitors can be paused, and paused state is shown across the monitor table and detail pages.

  • Self-served inventory — The repository list is now served from the observability service's own API, and new monitors default their timeouts to 30 seconds.

Utilities

  • Subscriptions & billing — Utilities introduces a subscription and billing engine: it issues its own invoices and credit notes, supports calendar-aligned monthly billing with a prorated first period, automatic per-price discounts, and configurable inclusive or exclusive tax per price. A resilient scheduler drives renewals and usage charges, publishes metrics, audits abandoned work, and lets operators requeue or abandon dead-lettered jobs.

Localization

  • Faster key editing — Keys support inline editing and bulk editing, language tables offer copyable snippets for language, key-name and module-name values, and module tables are paginated.

CLI

  • Introducing the Blocks CLI — @seliseblocks/cli-os debuts as the terminal and automation control plane for Blocks OS. It signs in through OIDC device login with OS-native credential storage, scaffolds new projects, and exposes command families for Identity, Data, Mail, Notification, Localization, Storage, MFA, and Deployment — so the platform can be operated from a terminal or an agent instead of ad-hoc API calls. A set of AI workflow skills ships alongside to guide agents through supported Blocks workflows.

Developer SDKs

  • genesis-os (React) v4.2.x — The shared app-shell continued to refine the OS console experience across service applications.

  • Blocks Genesis (.NET) v4.0.x → v4.1.x — The .NET bootstrap SDK moved through the v4.1 line with configuration and security updates.

2026.07.30

Blocks OS Platform

OSIAMDataLocalizationLogicUtilitiesReleaseAgentsMonitorStudio

Blocks Cloud is now Blocks OS. This release re-architects the platform around a unified operating console where every service runs on its own dedicated domain, migrates all applications to the new genesis-os frontend foundation on React 19, and ships a wave of new capabilities across Identity, Storage, Payments, and Workflow. It is the largest platform update since the 3.x line and the starting point for everything that follows.

Blocks OS Platform

The platform rename is more than branding — it reflects a re-architecture into independent, individually addressable services behind one console.

  • A unified OS console — All services are now reached through a single shell at os.seliseblocks.com, with consolidated sidebar navigation and a service switcher that filters available applications by environment.

  • A domain per service — Each capability now has its own dedicated subdomain instead of sharing one Cloud origin. Identity, Data, Workflow, Deployment, Observability, Localization, Utilities, Studio, and AI each run and scale on their own host.

  • Identity & Access, in the console — User and Organization management has moved out of the standalone IAM frontend and now lives natively inside the OS console under Identity & Access, unifying administration with the rest of the platform.

  • Environment data migration — A new migration engine moves each project's data into the per-environment architecture. Migrations are authorized, OTP-verified, and emit completion events so dependent services can react when a project finishes moving.

Identity

Identity gains a major set of authentication and access-management capabilities alongside the console move.

  • Device Authorization flow (OAuth 2.0 / RFC 8628) — Blocks OS now supports the OAuth 2.0 Device Authorization Grant, enabling sign-in on input-constrained and headless clients (CLIs, terminals, TV apps) using a short user code.

  • Social identity linking at signup — Users can link a social identity provider to their account during signup, streamlining onboarding across providers.

  • User activation flow — A dedicated activation experience captures first and last name on the activation form, and administrators can resend activation to users who remain inactive.

  • OIDC client management — Client secrets can now be rotated for OIDC clients, identity providers can be deleted, and credential saving supports an external discovery endpoint.

  • Permission management overhaul — Dependent-permission selection is clearer and easier to reason about, built-in permissions are surfaced as read-only, permissions carry a severity, and permission groups can be created directly from the UI.

  • Stronger session control — Logging out can now revoke multiple active sessions at once.

Storage & Data

Storage is now a full document management system, and the data layer gains query and metadata improvements.

  • Document Management System (DMS) — A new content platform with fine-grained access control: content-access administration backed by an audit trail, file version history, move and zero-copy copy, cached folder ancestry with a cycle-guarded rebuild, and access-resolved children listing with cursor pagination. An effective-policy resolver evaluates access-control entries per request.

  • Richer GraphQL queries — Queries now support logical AND / OR operators for more expressive filtering.

  • Better resource metadata & docs — Permissions and resources carry names and descriptions, and the Data service ships published API documentation.

Workflow

  • Rename workflows — Workflows can be renamed in place, and the workflow editor gains improved state management and input-panel handling.

Payments

Utilities introduces a complete Stripe-based payments experience.

  • Stripe payments — Hosted checkout, saved cards (save and remove), and refunds are now supported end to end. Payments record the authenticated user, and the platform reuses a shopper's existing Stripe customer at checkout.

  • Multiple providers — Payment providers can be registered and configured through the API and administered from dedicated provider pages, with provider credentials stored encrypted on the provider document and incoming events verified through Stripe webhook validation.

Localization

  • genesis-os client — The Localization application has migrated to React 19 on the genesis-os foundation, and a new extension guide page documents the localization extension workflow.

Observability

  • Driver updates & API exploration — The observability driver was updated across services, and Swagger is enabled for exploring the monitoring API.

Developer SDKs

The SDK line moved to v4.0 in lockstep with the platform, unified under the genesis-os name.

  • genesis-os (React) v4.0 — @seliseblocks/blocks-kit is renamed to @seliseblocks/genesis-os@4.0.0 and now requires React 19.2.8 and react-router 8. It is the shared app-shell and component foundation consumed by every service application (IAM, OS, Data, Logic, Monitor, Release, Studio, Utilities, Localization), with an environment-aware app switcher. A React 19 / react-router 8 migration guide is published. (Breaking change.)

  • Blocks Genesis (.NET) v4.0 — The .NET bootstrap SDK bumped to v4.0 alongside, adding formal versioning and analysis rulesets and picking up security updates.

  • genesis-py v0.3.1 — The Python Genesis SDK received a maintenance update.

2026.06.29

Workflow Versioning, MFA & Guided Environment Migration

IAMLogicDataOS

Identity picked up account-security hardening with MFA, lockout, and captcha; Workflow gained a full versioning and publishing model; and the console shipped a guided wizard for moving a project into the new per-environment architecture.

Identity

  • Multi-Factor Authentication — A new MFA controller and services support TOTP setup and verification at login, giving users a second factor beyond their password.

  • Account lockout — Repeated failed sign-in attempts now trip an account lockout, and a captcha (HCaptcha or ReCaptcha, configurable per tenant) is required after failed attempts on both the embedded and OIDC login flows.

  • My Organization — Users get a self-service "My Organization" page, and the role/permission model now supports multiple organizations per user, including creating and switching between them from the console.

  • Unified auth settings — OIDC configuration is now exposed through a dedicated UI-config endpoint, and Identity's settings moved to unified tabs, retiring the older general auth configuration screen.

Workflow

  • Versioning and publishing — Workflows can now be versioned: authors create a new version, publish or unpublish it, and browse version history, with executions distinguishing draft from published runs.

  • Editor productivity — Nodes can be multi-selected, duplicated, copied, and pasted; a new "set variable" node was added; and the send-mail node gained dynamic key-value field mapping with template key extraction.

Data

  • AI-assisted validation regex — A new "generate validation regex" action in the schema editor turns a plain-language description of a validation rule into a working regular expression, so schema authors no longer need to hand-write one.

Blocks OS Platform

  • Guided environment migration — A step-by-step wizard walks a project through moving its data into the new per-environment architecture, with progress tracked so a user can see whether a migration is in flight or recently completed.

v3.7.15

Workflow Data Integration, Localization Control & Identity Enhancements

LogicDataLocalizationIAMStudio

Data trigger and action nodes for workflows, localization glossary, configurable sign-up flows, and Blazor scaffolding in the CLI.

Release Notes

v3.7.15 introduces deeper integration between Workflows and Data Gateway, enhanced localization control through glossary management, improved identity onboarding flexibility, and expanded developer tooling via CLI updates.

This release strengthens Blocks Cloud’s position as a unified platform by enabling event-driven data workflows, improving translation accuracy, and providing greater control over authentication and application scaffolding.

Workflow – Data Nodes

Workflows now integrate directly with Data Gateway through the introduction of data-aware nodes, enabling event-driven automation and seamless interaction with persistent storage.

This enhancement allows workflows to react to data changes in real time and perform operations directly on stored data—eliminating the need for intermediary services or custom backend logic.

New Nodes

Data Trigger Node

The Data Trigger Node enables workflows to be triggered automatically based on changes in Data Gateway collections.

  • Listens to insert, update, and delete operations
  • Configurable per specific collection
  • Enables real-time, event-driven workflows based on data activity

This allows teams to build reactive systems such as audit pipelines, notifications, synchronization processes, and downstream data workflows triggered by changes in persistent storage.

Data Action Node

The Data Action Node allows workflows to directly perform operations on Data Gateway collections.

  • Supports operations:
    • Get
    • Insert
    • Update
    • Delete
  • Configurable per target collection

For schemas protected by access modifiers, the node can:

  • Use client credentials configured in Blocks Cloud IAM
  • Automatically authenticate using those credentials
  • Execute operations securely without manual token handling

This enables secure, automated data manipulation within workflows while respecting existing access control policies.

Localization – Glossary

The Localization module now includes a Glossary system, providing precise control over how specific terms are handled during auto-translation.

Blocks Cloud’s auto-translation engine detects untranslated values and generates translations across enabled languages. However, certain terms—such as technical keywords, brand names, or domain-specific terminology—should not be translated or should follow specific rules.

The Glossary feature allows users to define and control these terms explicitly.

Glossary Scopes

  • Global Glossary
    Applies to all localization keys across the application

  • Module-Level Glossary
    Applies to all keys within a specific module

  • Key-Level Glossary
    Applied manually to individual keys for fine-grained control

Users can define whether glossary terms:

  • Should be excluded from translation
  • Should be translated in a specific way

This ensures higher translation accuracy, consistency, and control across multilingual applications.

IDP – Configurable Sign-Up Flow

Blocks Cloud now provides greater flexibility in how users register and access applications through configurable sign-up flows.

Administrators can now:

  • Enable or disable self-service user registration
  • Define the allowed authentication methods for sign-up

Supported Sign-Up Methods

  • Email and Password
  • Single Sign-On (SSO) (requires prior configuration in Blocks Cloud)

When self-sign-up is enabled, users can register directly into the associated Construct application using the configured methods.

This enhancement allows organizations to align user onboarding with their security policies and identity strategies.

CLI

The Blocks CLI has been enhanced to support multiple frontend scaffolding options, improving flexibility for developers.

Previously, the CLI supported only the React-based Construct. With this update:

  • Support for Blazor-based Construct has been added
  • Users can now choose their preferred framework during project setup

This allows developers to align application scaffolding with their preferred technology stack, supporting both JavaScript and .NET ecosystems.

v3.7.11

Security, Identity & Automation Enhancements Across Blocks Cloud

UtilitiesIAMLocalizationAgentsDataOS

Magic Links, OIDC single sign-on via Blocks IDP, Selise AI agent integration, S3-compatible storage, and redesigned environment management.

Release Notes

This release strengthens Blocks Cloud with secure Magic Links, OIDC-based SSO via Blocks IDP, enhanced Selise AI agent integration, improved localization change detection, AWS S3–compatible storage support, and a redesigned environment and user management experience.

Together, these updates improve automation, governance, flexibility, and AI-driven workflows across the SELISE Blocks ecosystem.

Utilities - Secure Redirects & Backend Action Triggers

Blocks Cloud now introduces Magic Links, enabling teams to generate secure, time-limited URLs for streamlined user flows and automated backend actions.

Magic Links are designed for flexibility and control, supporting configurable usage limits, expiration dates, authentication scopes, and environment-specific base URLs.

Two Types of Magic Links

Redirect Magic Links Generate shortened URLs that securely redirect users to a configured destination while maintaining authentication context. Ideal for passwordless login, invitations, and guided user journeys.

Action Magic Links Trigger predefined backend HTTP requests (GET or POST) when accessed. These links execute actions such as email verification, workflow triggers, or system events—without requiring user redirection.

Key Capabilities

  • Configurable usage limits
  • Optional automatic expiration
  • Scoped access via client credentials
  • Support for custom headers, payloads, and query parameters (Action type)
  • Customizable short URL base configuration
  • Centralized dashboard for viewing, filtering, and managing links

Magic Links provide a secure and extensible mechanism for handling authentication flows, event-driven automation, and controlled access patterns across environments.

Identity - OIDC

OpenID Connect (OIDC) Support for Blocks IDP

This release adds OpenID Connect (OIDC) support, enabling applications to use Blocks Identity Provider (IDP) as a standards-compliant Single Sign-On (SSO) solution.

Applications can now integrate with Blocks IDP using the Authorization Code flow, enabling secure, standards-compliant user authentication while delegating identity management to the Blocks platform. This allows any third-party application to use Blocks IDP as its SSO provider.

Blocks Construct also supports this capability—by enabling Bring Your Own SSO and implementing Blocks OIDC—allowing Construct-based deployments to participate in the same unified single sign-on experience across environments.

Key benefits include:

  • Centralized authentication through Blocks IDP
  • Secure, industry-standard OIDC authorization flow
  • Seamless SSO availability across Blocks-based deployments
  • Reduced need for custom authentication logic in applications

This enhancement strengthens identity integration within the SELISE Blocks ecosystem and provides a scalable foundation for SSO-enabled applications.

Localization

A new endpoint is now available to help determine whether localization content has changed, without requiring a full language file download. This allows applications to efficiently detect when an update is necessary by checking the publication history of language resources.

New endpoint: /Key/GetLanguageFileGenerationHistory Detailed specifications are available in the API documentation Swagger.

The endpoint returns versioned metadata for published language files, including creation time and project context, enabling lightweight change detection.

Newly Supported Languages

  • Bengali (Sylheti)
  • Bengali (Chittagonian)

This update improves localization efficiency while expanding language coverage for regional variants.

Selise AI – Blocks Cloud Agent Integration

Selise AI continues to evolve as a unified conversational interface.

Previously, users could interact with multiple large language models (LLMs) within a single GPT-style experience. With this release, Selise AI now supports direct interaction with agents configured on Blocks Cloud.

This enhancement allows users to connect to agents powered by the Blocks RAG architecture, leveraging:

  • Dedicated knowledge bases
  • Custom tunings and configurations
  • Context-aware retrieval
  • Enterprise-ready deployment controls

By integrating Blocks Cloud agents into Selise AI, organizations can move beyond general-purpose LLM conversations and interact with domain-specific, retrieval-augmented assistants tailored to their own data and business logic.

This update strengthens the bridge between conversational AI and the broader **SELISE Blocks ecosystem, enabling more intelligent, contextual, and controlled AI experiences.

UDS – AWS-Compatible Object Storage Support

UDS (formerly Data Gateway) now supports AWS S3–compatible object storage, enabling integration with alternatives such as MinIO.

This enhancement allows organizations to use self-hosted or third-party S3-compatible storage solutions while maintaining compatibility with existing AWS-style APIs. It provides greater flexibility in storage architecture, supports hybrid and on-prem deployments, and reduces dependency on a single cloud provider.

Blocks Cloud

A new dedicated section has been introduced for navigating Environments, Project Settings, and People Management, creating a more structured and intuitive user experience.

This update streamlines navigation across environments and improves visibility and control over user access. Teams can now:

  • Invite users to multiple environments
  • Clearly see who has access to each environment
  • View and manage user profiles
  • Manage project-level settings from a centralized location
v3.7.9

Workflow Automation, Access Control & AI Visibility

LogicIAMAgentsDataLocalizationUtilities

Visual workflows, roles and permissions across data, endpoints and UI, AI conversation transparency, and consolidated platform endpoints.

Release Notes

v3.7.9 continues to evolve Blocks Cloud into a modern, extensible platform for building, securing, and operating intelligent systems. This release introduces visual Workflows for automation, Roles and Permissions for fine-grained access control, and meaningful upgrades across AI, localization, and platform APIs.

Together, these enhancements bring greater control, transparency, and composability—allowing teams to automate processes, govern access across data and applications, and gain deeper insight into AI behavior, all while staying aligned with current industry standards for platform engineering and AI operations.

Roles and Permissions

Blocks Cloud introduces Roles and Permissions to give teams fine-grained control over access across data, APIs, and user interfaces. This capability aligns with modern security and governance standards, ensuring the right users have the right access—no more, no less.

Access Control Areas

Roles and permissions can be applied across three key aspects of the platform:

  1. Data Connect
    • Control access to data using row-level and schema level permissions.
    • Ensure sensitive data is visible only to authorized roles.
  2. Endpoints
    • Define who can access and invoke specific API endpoints.
    • Enforce consistent authorization rules across services.
  3. Front-End
    • Control access to front-end pages and resources.
    • Tailor UI visibility based on user roles.

Benefits

  • Stronger security through least-privilege access control.
  • Centralized governance across data, APIs, and UI.
  • Cleaner separation of responsibilities for teams and collaborators.
  • Scalable access management as applications and organizations grow.

Workflows

Blocks Cloud now introduces Workflows, enabling teams to orchestrate automation and integrations through a visual, node-based experience—similar to modern workflow tools used across the industry.

Nodes Available

Workflows are built by connecting reusable nodes that can be arranged in any configuration:

  • HTTP — Send HTTP requests to external services or APIs.
  • Webhook — Receive incoming HTTP calls with user-defined input and output schemas.
  • Email — Send emails as part of automated flows.
  • AI — Invoke any agent configured in Blocks Cloud directly within a workflow.

Key Capabilities

  • Flexible, visual node-based composition for building automation flows.
  • Support for custom input and output definitions, enabling predictable integrations.
  • Combine AI, external APIs, and notifications in a single workflow.

Benefits

  • Faster automation without writing glue code.
  • Seamless AI integration—use agent as first-class workflow components.
  • Greater flexibility to connect services, react to events, and automate processes.
  • Extensible foundation for future workflow nodes and integrations.

AI

The assistant now provides live feedback after a prompt is submitted, indicating the current stage of processing so users know the request is actively being handled.

  • The assistant now provides live feedback after a prompt is submitted, indicating the current stage of processing so users know the request is actively being handled.
  • Ask AI in Tracing and Logs also has real-time responses
  • Improvements in AI conversation history
    • See workflow steps
    • See duration in each step
    • See the tools that were used, if any, along with the input and output parameters
    • See the used retrieval calls, if any, along with the chunks
  • The Tools sections input and output parameters has been improved and supports nested objects
  • The output parameters can be reduced based on output parameter limits. This helps reduce token calls
  • Tools dashboard tab is now active. See useful information like:
    • Total Requests
    • Success Rate
    • Success Requests
    • Failed Requests
  • Configuration improvements

Microservices endpoint changes

Some microservice endpoints have been updated in this release. The previous endpoints will remain supported for a limited period to ensure backward compatibility.

We recommend updating your integrations to use the new endpoints as soon as possible, as the legacy endpoints will be deprecated and removed after the announced deprecation window.

SubmodulesOld microservice EndpointNew microservice endpoint
Authentication submodule/authentication/v1/Client/GetOIDCClients/idp/v1/Authentication/GetOIDCClient
/authentication/v1/OIDCClient/Save/idp/v1/Authentication/SaveOIDCClient
/authentication/v1/Client/DeleteOIDCClient/idp/v1/Authentication/DeleteOIDCClient
/authentication/v1/OIDCClient/Get/idp/v1/Authentication/GetClientCredentials
/authentication/v1/Client/SaveClientCredential/idp/v1/Authentication/SaveClientCredential
/authentication/v1/Client/DeleteClientCredential/idp/v1/Authentication/DeleteClientCredential
/authentication/v1/Configuration/Get/cloudconfiguration/v1/Authentication/Get
/authentication/v1/Configuration/Update/cloudconfiguration/v1/Authentication/Update
/authentication/v1/OAuth/Token/idp/v1/Authentication/Token
/authentication/v1/Authentication/Logout/idp/v1/Authentication/Logout
/authentication/v1/OAuth/GetSocialLogInEndPoint/idp/v1/Authentication/GetSocialLogInEndPoint
/authentication/v1/Social/GetSsoCredentials/idp/v1/Authentication/GetSsoCredentials
/authentication/v1/Social/SaveSsoCredential/idp/v1/Authentication/SaveSsoCredential
/authentication/v1/Social/DeleteSsoCredential/idp/v1/Authentication/DeleteSsoCredential
/authentication/v1/Social/UpdateStatus/idp/v1/Authentication/UpdateStatus
/authentication/v1/Social/GetLoginOptions/idp/v1/Authentication/GetLoginOptions
Captcha submodule/captcha/v1/Configuration/Gets/cloudconfiguration/v1/Captcha/Gets
/captcha/v1/Configuration/Save/cloudconfiguration/v1/Captcha/Save
/captcha/v1/Configuration/UpdateStatus/cloudconfiguration/v1/Captcha/UpdateStatus
Communication submodule/mailservice/v1/Configuration/Get/cloudconfiguration/v1/Mail/Get
/mailservice/v1/Configuration/Gets/cloudconfiguration/v1/Mail/Gets
/mailservice/v1/Template/Gets/communication/v1/Template/Gets
/mailservice/v1/Template/Get/communication/v1/Template/Get
/mailservice/v1/Configuration/Save/cloudconfiguration/v1/Mail/Save
/mailservice/v1/Mail/SendToAny/communication/v1/Mail/SendToAny
/mailservice/v1/Template/Save/communication/v1/Template/Save
/mailservice/v1/Template/Clone/communication/v1/Template/Clone
/mailservice/v1/Template/Delete/communication/v1/Template/Delete
/mailservice/v1/Configuration/Delete/cloudconfiguration/v1/Mail/Delete
Data-gateway submodule/data/v1/data-sources/add/uds/v1/data-sources/add
/data/v1/data-sources/update/uds/v1/data-sources/update
/data/v1/data-sources/${payload.projectKey}/get/uds/v1/data-sources/${payload.projectKey}/get
/data/v1/${payload.projectShortKey}/configurations/${payload.projectKey}/reload/uds/v1/${payload.projectShortKey}/configurations/${payload.projectKey}/reload
/data/v1/configurations/${payload.projectKey}/reload/uds/v1/configurations/${payload.projectKey}/reload
/data/v1/schemas?Keyword=${payload.keyword}&PageSize=${payload.pageSize}&PageNo=${payload.pageNo}&SortDescending=${payload.sortDescending}&SortBy=${payload.sortBy}&ProjectKey=${payload.projectKey}&SchemaType=${payload.schemaType}/uds/v1/schemas?Keyword=${payload.keyword}&PageSize=${payload.pageSize}&PageNo=${payload.pageNo}&SortDescending=${payload.sortDescending}&SortBy=${payload.sortBy}&ProjectKey=${payload.projectKey}&SchemaType=${payload.schemaType}
/data/v1/schemas/${id}?projectkey=${projectKey}/uds/v1/schemas/${id}?projectkey=${projectKey}
/data/v1/schemas/info/uds/v1/schemas/info
/data/v1/schemas/fields/uds/v1/schemas/fields
/data/v1/schemas/${payload.id}?projectKey=${payload.projectKey}/uds/v1/schemas/${payload.id}?projectKey=${payload.projectKey}
/data/v1/data-access/manage/uds/v1/data-access/manage
/data/v1/data-access/security/change/uds/v1/data-access/security/change
/data/v1/${projectShortKey}/gateway/uds/v1/${projectShortKey}/gateway
/data/v1/data-manage/${projectKey}/mock-data/uds/v1/data-manage/${projectKey}/mock-data
/data/v1/data-manage/mock-data/uds/v1/data-manage/mock-data
Iam submodule/iam/v1/Account/Activate/idp/v1/Iam/Activate
/iam/v1/Account/ResendActivation/idp/v1/Iam/ResendActivation
/iam/v1/Account/Recover/idp/v1/Iam/Recover
/iam/v1/Account/ResetPassword/idp/v1/Iam/ResetPassword
/iam/v1/Account/ValidateActivationCode/idp/v1/Iam/ValidateActivationCode
/iam/v1/Configuration/Get/cloudconfiguration/v1/IAM/Get
/iam/v1/Configuration/Save/cloudconfiguration/v1/IAM/Save
/iam/v1/Resource/GetPermissions/idp/v1/Iam/GetPermissions
/iam/v1/Resource/GetPermission/idp/v1/Iam/GetPermission
/iam/v1/Resource/CreatePermission/idp/v1/Iam/CreatePermission
/iam/v1/Resource/UpdatePermission/idp/v1/Iam/UpdatePermission
/iam/v1/Resource/GetResourceGroups/idp/v1/Iam/GetResourceGroups
/iam/v1/Resource/GetRoles/idp/v1/Iam/GetRoles
/iam/v1/Resource/GetRole/idp/v1/Iam/GetRole
/iam/v1/Resource/CreateRole/idp/v1/Iam/CreateRole
/iam/v1/Resource/UpdateRole/idp/v1/Iam/UpdateRole
/iam/v1/Resource/SetRoles/idp/v1/Iam/SetRoles
/iam/v1/User/GetUsers/idp/v1/Iam/GetUsers
/iam/v1/User/GetUser/idp/v1/Iam/GetUser
/iam/v1/User/GetUser?id=${payload.id}&ProjectKey=${payload.projectKey}/idp/v1/Iam/GetUser?id=${payload.id}&ProjectKey=${payload.projectKey}
/iam/v1/User/Create/idp/v1/Iam/Create
/iam/v1/User/Update/idp/v1/Iam/Update
/iam/v1/User/SaveRolesAndPermissions/idp/v1/Iam/SaveRolesAndPermissions
/iam/v1/Activity/GetSessions/idp/v1/Iam/GetSessions
/iam/v1/Activity/GetHistories/idp/v1/Iam/GetHistories
/authentication/v1/Client/GetUserCodes/idp/v1/Authentication/GetUserCodes
/authentication/v1/Client/GenerateUserCode/idp/v1/Authentication/GenerateUserCode
/iam/v1/user/getUserRoles?Id=${payload.userId}&ProjectKey=${payload.projectKey}/idp/v1/Iam/GetUserRoles?Id=${payload.userId}&ProjectKey=${payload.projectKey}
/iam/v1/user/GetUserPermissions?Id=${payload.userId}&ProjectKey=${payload.projectKey}/idp/v1/Iam/GetUserPermissions?Id=${payload.userId}&ProjectKey=${payload.projectKey}
/iam/v1/Account/ResendActivation/idp/v1/Iam/ResendActivation
MFA submodule/mfa/v1/Configuration/Get?ProjectKey=${paylaod.projectKey}/cloudconfiguration/v1/MFA/Get?ProjectKey=${paylaod.projectKey}
/mfa/v1/Configuration/Save/cloudconfiguration/v1/MFA/Save
/mfa/v1/Management/GenerateOTP/idp/v1/Mfa/GenerateOTP
/mfa/v1/Management/SetUpTotp?UserId=${paylaod.id}&ProjectKey=${paylaod.projectKey}/idp/v1/Mfa/SetUpTotp?UserId=${paylaod.id}&ProjectKey=${paylaod.projectKey}
/mfa/v1/Management/VerifyOTP/idp/v1/Mfa/VerifyOTP
/mfa/v1/Management/ResendOtp/idp/v1/Mfa/ResendOtp
/mfa/v1/Management/DisableUserMfa/idp/v1/Mfa/DisableUserMfa
Nofitication submodule/notification/v1/NotificationHub/communication/v1/NotificationHub
/notification/v1/Notifier/GetNotifications/communication/v1/Notification/GetNotifications
/notification/v1/Notifier/MarkNotificationAsRead/communication/v1/Notification/MarkNotificationAsRead
/notification/v1/MarkAllNotificationAsRead/communication/v1/Notification/MarkAllNotificationAsRead
/notification/v1//Configuration/Gets?page=${page}&pageSize=${pageSize}&projectKey=${projectKey}/cloudconfiguration/v1/Notification/Gets?page=${page}&pageSize=${pageSize}&projectKey=${projectKey}
/notification/v1/Configuration/Save/cloudconfiguration/v1/Notification/Save
/notification/v1/Configuration/Delete?itemId=${payload.itemId}&projectKey=${payload.projectKey}/cloudconfiguration/v1/Notification/Delete?itemId=${payload.itemId}&projectKey=${payload.projectKey}
Storage submodule/storage/v1/Configuration/Gets?ProjectKey=${projectKey}/cloudconfiguration/v1/Storage/Gets?ProjectKey=${projectKey}
/storage/v1/Configuration/Save/cloudconfiguration/v1/Storage/Save
/storage/v1/Configuration/Delete?ProjectKey=${payload.projectKey}&ConfigurationName=${payload.configurationName}/cloudconfiguration/v1/Storage/Delete?ProjectKey=${payload.projectKey}&ConfigurationName=${payload.configurationName}
/storage/v1/Files/GetFile?FileId=${payload.itemId}&ProjectKey=${payload.projectKey}/uds/v1/Files/GetFile?FileId=${payload.itemId}&ProjectKey=${payload.projectKey}
/storage/v1/Files/DeleteFile/uds/v1/Files/DeleteFile
/storage/v1/Files/GetPreSignedUrlForUpload/uds/v1/Files/GetPreSignedUrlForUpload
/storage/v1/Files/GetFilesInfo/uds/v1/Files/GetFilesInfo
/storage/v1/Files/updateFileAdditionalInfo/uds/v1/Files/updateFileAdditionalInfo
/storage/v1/Files/GetFile?FileId=${meta.fileId}&ProjectKey=${meta.projectKey}/uds/v1/Files/GetFile?FileId=${meta.fileId}&ProjectKey=${meta.projectKey}
/storage/v1/Files/UploadFileToLocalStorage/uds/v1/Files/UploadFileToLocalStorage
/storage/v1/Certificate/UploadCertificate?TenantId=${payload.TenantId}&IsThirdParty=true/uds/v1/Certificate/UploadCertificate?TenantId=${payload.TenantId}&IsThirdParty=true

Localization Service Webhook

Get notified every time the auto-translation is complete. Use the following endpoint to set up your webhooks.

curl --location 'https://api.seliseblocks.com/uilm/v1/Config/SaveWebHook' \
--header 'Authorization: Bearer <your-token>' \
--header 'Content-Type: application/json' \
--data '{
  "itemId": "<uuid>",
  "createDate": "<iso_8601_timestamp>",
  "lastUpdateDate": "<iso_8601_timestamp>",
  "url": "<webhook_url>",
  "contentType": "application/json",
  "blocksWebhookSecret": {
    "secret": "<webhook_secret>",
    "headerKey": "<signature_header_name>"
  },
  "isDisabled": false,
  "projectKey": "<project-key>"
}'

Bug Fixes

  • Fixed key duplication when migrating language keys form one environment to another
  • Fixed only keys are IDs were being exported when exporting to Excel format
v3.7.7

Advanced Health Monitoring

IAMMonitor

Health overview dashboards, service monitors and alerting in Deploy & Observe, plus new social logins and JWT claims mapping.

This release introduces powerful new authentication options, deeper health monitoring for deployed and managed services, and improved visibility into system uptime. v0.0.8 expands Deploy & Observe into a full monitoring suite while delivering more flexibility in identity mapping across external providers.

Release Notes

v3.7.7 enhances platform observability with a new Health view, configurable service monitors, and alerting options. On the Identity side, expanded social logins and JWT claim mapping streamline authentication and integration for both Blocks Cloud and Construct apps.

Authentication

New Social Logins

Users can now authenticate using GitHub, X (Twitter), and LinkedIn.
These new social login providers are supported across:

  • Blocks Cloud
  • Construct projects

This simplifies onboarding, enables broader identity federation, and reduces friction for end users.

JWT Claims Mapping

Different identity providers expose different fields inside their issued JWT tokens.
With JWT Claims Mapping, administrators can now:

  • Map external token fields to Blocks Cloud–expected fields
  • Align custom claims from third-party identity providers
  • Ensure seamless authentication flows across Construct and Cloud

All mapping is done directly through the Cloud portal for consistency and ease of configuration.

Deploy & Observe

Modern cloud platforms rely on real-time visibility, automated health checks, and proactive alerting — and Deploy & Observe continues to evolve to meet these industry standards. With v0.0.8, Blocks Cloud introduces a comprehensive health monitoring experience that brings deeper transparency, better uptime awareness, and stronger operational control across all services.

New Features

  • Health Overview Dashboard — view uptime summaries and a 24-hour health timeline, where each bar represents one hour of service health.

  • Hover & Click Insights — hover to see uptime percentage and time ranges; click to open detailed monitoring options.

  • Service Details View

    • Incident history
    • Notification configuration (email recipients, triggers, etc.)
    • Callback monitoring support (your service pings Blocks Cloud to confirm it’s alive)
    • Request-based monitoring (Blocks Cloud pings your service to verify availability)
    • Support for JSON payloads and custom headers
    • Options to pause or delete monitors

  • Core, Managed & Deployed Services Monitoring — health checks now support all service types across the platform.

  • Monitoring Setup in Deploy & Observe — configure callback or request monitors directly from the dashboard with an improved setup flow.

Benefits

  • Unified visibility — see the state of your entire ecosystem (core services, deployed workloads, and managed services) from a single view.
  • Proactive issue detection — understand uptime patterns hour-by-hour and catch incidents before they scale.
  • Fewer surprises in production — automated health checks ensure that degraded services are flagged quickly.
  • Flexible monitoring — choose callback or request-based checks depending on how your service reports health.
  • More control — pause, delete, or reconfigure monitors without redeploying anything.

Bug Fixes

  • Fixed issue where all client credential grant types were being set as inactive.
  • Resolved issue where already filled-in values were being translated when using auto-translate.
v3.7.6

Managed Services, Smarter IAM & User Docs

OSIAMDataAgentsLocalizationMonitor

Dedicated Data Gateway instances per project, external IdP and client credentials support, context-aware AI translation, and managed services.

This release focuses on isolation, identity, and intelligent communication. Each project and environment now has its own schema, ensuring complete data separation. The IAM module gains new authentication options, while the AI, Communication, and Managed Services sections see meaningful functional and usability updates.

Release Notes

v3.7.6 introduces dedicated Data Gateway instances, smarter identity management with client credential support, and context-aware AI translations. These enhancements improve security, flexibility, and collaboration across SELISE Blocks Cloud.

Projects & Environments

Every project and environment now has its own schema, replacing the previously shared model.
This provides complete isolation between environments, ensuring that project-specific data, rules, and configurations remain independent.

IAM (Identity & Access Management)

New Features

  • External IdP JWKS Support — Administrators can now integrate third-party authentication providers such as Auth0, Keycloak, or any custom OpenID Connect (OIDC)–compliant service through JWKS (JSON Web Key Set) configuration. By sharing the provider’s JWKS endpoint within IAM settings, Blocks Cloud can directly verify tokens issued by these external systems. This enhancement allows organizations to bring their existing user base into Blocks Cloud without requiring re-registration or manual synchronization. Users authenticated through their existing IdP can seamlessly access Blocks Cloud resources while benefiting from native identity, authorization, and LMT (Logs, Metrics & Tracing) capabilities. In essence, teams can now unify their external authentication ecosystem with Blocks Cloud — maintaining centralized identity management externally while still gaining full observability and policy control within the platform.
  • Client Credentials Grant — Added support for the Client Credentials OAuth 2.0 flow, enabling secure, machine-to-machine authentication. This allows backend services or applications to access APIs using client ID and secret without requiring user interaction.
  • SSO Renaming — The “Social” tab has been renamed to SSO (Single Sign-On) for clarity and alignment with industry standards.

Improvements

  • Tab Sequence Updated — The sequence of authentication tabs has been restructured for a more logical setup flow.

Data Gateway

New Features

  • Preview Section — Added a powerful preview interface allowing users to view endpoints for GraphQL databases, auto-generate Create/Read/Update/Delete (CRUD) queries, and inspect schema structure in JSON format.
  • Dedicated Instances per Project/Environment — Each project or environment now comes with its own Data Gateway instance, ensuring dedicated GraphQL resources and complete data separation.

AI

New Features

  • Custom Agent Banner — Organizations can now add branded banners to their agents. The banner appears at the top of the agent interface and supports image formats, allowing teams to display announcements, promotions, or visual identity elements.

Communication

New Features

  • Sinhala Language Added — Sinhala is now supported as part of the translation system, expanding accessibility.
  • Key-Specific Context Provision — AI translation models often produce linguistically correct results but can miss contextual nuances — especially when the same phrase or label carries different meanings depending on where it appears in the interface. With key-specific context provision, developers can now attach contextual metadata to each translation key. This additional layer of information helps the AI understand where and how the text is used — whether it’s part of a button, tooltip, message, or title — allowing translations to stay accurate not just in language, but also in intent and placement. As a result, automatic translations across the platform become more reliable, natural, and domain-aware, minimizing errors that come from one-size-fits-all translations.

Managed Services

New Features

  • Managed Services — The Managed Services capability allows users to connect their own backend services with the core features of SELISE Blocks Cloud — effectively extending the platform’s observability, identity, and data capabilities into their own systems. In this release, users can integrate Blocks’ native Logs, Metrics & Tracing (LMT) features directly into their managed services. This enables unified monitoring, debugging, and performance analysis across both internal and Blocks-hosted components. Looking ahead, this integration layer will expand beyond LMT to include additional platform services — allowing teams to view their service usage, operational health, and even vulnerability scans (via SCA, SAST, and DAST) within the same dashboard.
  • Future Enhancements — In upcoming releases, users will also be able to view service health and scan for vulnerabilities using SCA (Software Composition Analysis), SAST (Static Application Security Testing), and DAST (Dynamic Application Security Testing) integrations — bringing proactive observability and security into one place.

Documentation

  • User Docs Site Launched — The official documentation for SELISE Blocks Cloud is now live at docs.seliseblocks.com/cloud. Explore detailed guides, configuration steps, and API references.

Bug Fixes

  • Fixed UI responsiveness issues in the “Export Keys” section.
  • Updated “Reload Schema” API to dynamically load projects. (#1680)
  • Fixed agent scrolling issues on mobile devices. (#1497)
  • General responsiveness improvements across modules.
  • Fixed language data migration bug where duplicate keys were being created.
  • Resolved issue where Test Construct users were unable to log in due to a cache problem. (#1645)

Summary

SELISE Blocks Cloud v3.7.6 continues the journey toward isolation, intelligence, and integration — offering developers more control, businesses stronger identity options, and teams smarter tools for communication and observability.

v3.7.5

Smarter Recommendations, Security & Integrations

AgentsDataIAMRelease

Data-driven AI suggestions, schema-level permissions, personal access tokens, and OIDC integration.

This release strengthens SELISE Blocks Cloud with smarter recommendations, enhanced security controls, and deeper integrations. Users gain contextual suggestions, schema-level permission management, and flexible authentication options across the platform. Together, these improvements make the environment more adaptive, secure, and developer-friendly.

Release Notes

This release introduces data-driven suggestions, identity enhancements, and schema-level permissions while refining deployment and observability. Teams benefit from stronger security, streamlined workflows, and intelligent automation across SELISE Blocks Cloud.

AI

New Features

  • Data-Based Suggestions — recommendation system powered by user data and behavioral signals to surface relevant actions and configurations.
  • Input-Based Suggestions — real-time suggestions derived from current user input, improving task accuracy and reducing setup time.
  • Knowledge Base Notifications — in-app notifications when documentation updates or relevant knowledge base articles are published.
  • Word Count — live word count within Markdown fields to assist with documentation and content management.

Improvements

  • Enhanced suggestion logic for better contextual relevance across multiple workflows.
  • Introduced visual distinction for suggestions derived from data versus input.
  • Optimized notification frequency and relevance to match project type and workspace activity.

Data Gateway

New Features

  • Schema-Level Permission Controls — adds support for Row Level Security (RLS) and Column Level Security (CLS) to manage data visibility with precision.
  • Administrators can now define role-based filters and masking policies directly from Data Gateway settings.

Improvements

  • Improved schema management UI for quicker configuration of RLS and CLS rules.
  • Policy changes are now logged for audit tracking.

Deploy & Observe

New Features

  • SCA Redirection — users can now be redirected directly to Software Composition Analysis findings and vulnerability reports for faster issue resolution.

Improvements

  • Updated integration flow to align with dependency management services.

Identity

New Features

  • Personal Access Tokens (PATs) — create and manage scoped tokens for secure programmatic access.
  • Third-Party Token Validation — validate tokens issued by external systems for broader interoperability.
  • Revoke Access — revoke issued tokens, sessions, or connected app access directly from profile settings.
  • OIDC Integration — introduces OpenID Connect (OIDC) support for seamless authentication between Dependency Track and SELISE Blocks Cloud.

Improvements

  • Improved token management interface with clearer expiration indicators.
  • Enhanced identity synchronization and access token handling.

Fixes

  • MFA Issue Fix — resolved inconsistencies in multi-factor authentication prompts that affected certain user accounts.

User Interface

Improvements

  • Terms and Conditions Placement — moved Terms and Conditions section to the bottom of relevant flows for improved readability and layout.

Git Integration

Fixes

  • Git Command Reliability — fixed issues affecting specific Git commands during repository synchronization. Operations like fetch, commit, and push now perform as expected.

Summary

SELISE Blocks Cloud v3.7.5 continues the platform’s focus on adaptability, control, and security — empowering teams to build, manage, and integrate confidently within a unified cloud environment.

v3.7.0

IAM, Security & Communication Enhancements

IAMUtilities

Major upgrades in identity management, user handling, security features, and email configuration.

This release includes major upgrades in identity management, user handling, security features, and email configuration. Below is a summary of what's new:

Security Enhancements

  • MFA (Multi-Factor Authentication) configuration enabled for projects and users via IAM (login, profile).
  • reCAPTCHA integrated for Signup, Forgot Password, and Activation pages (cloud frontend).

User Management

  • Advanced user filtering for quicker access.
  • Enhanced user details view with:
    • Basic info display
    • Password reset
    • MFA enable/disable
    • Assign roles and permissions directly from the user profile
  • Device-wise access log per user.
  • User activity history for audit and tracking.

Roles & Permissions

  • Add and manage roles.
  • Assign permissions to roles.
  • View role details and filter the permission list.

Email Management

  • Add and list mail server configurations.
  • Manage email templates: add, edit, filter, clone, and view.
  • Send test emails.
  • Simplified configuration management.

People Management

  • Invite users to the platform.
  • View and manage the list of invited users.