What to expect
Heads-up, not a commitment. The information below explains how we treat beta features and why delivery and availability can change.
- Currently being tested. These features are in active development and testing. Behavior and scope may change.
- No guaranteed delivery date. We do not commit to a specific release date for any feature listed here.
- No guarantee of delivery. Priorities shift based on resources and customer needs. A feature in beta may be delayed, changed, or not released to General Availability.
- Limited availability. Some features may be tested by select customers before being released to General Availability. Broader access is not guaranteed until a feature is generally available.
- Labs badge. Experimental features available in the platform but still being validated are marked with an orange Labs badge in the Elementum UI. Treat these the same way—behavior, scope, and availability may change before General Availability.
Features in beta
This list is updated as new beta features become available to give you an idea of upcoming improvements likely to occur in Elementum. The colored badges indicate the area of Elementum where you will see the update.User Field Filtering Apps
App Admins can add a filter to a user-type field that limits which users can be selected, accepting any mix of specific users, groups, and up to one group field on the record. The field displays only the combined set of eligible users—every selected user, every member of each selected group, and every member of the group currently stored in the selected group field—so form and record editors never see anyone outside the configured set.Configurable Voice Authentication Agent Intelligence
A reusable Auth Agent can be configured once and attached across phone services to authenticate callers—using flows such as PIN or Identifier + OTP—before they reach a Voice Agent. Administrators can tailor greetings, terminology, password-reset or service-desk guidance, OTP resend behavior, and whether failed authentication ends the call or transfers to an approved destination with a custom message.Automation Description Field Automations
Automation authors can write a description for an automation to document its purpose and behavior for teammates working in the same app. A new info icon on the automation details page opens a panel that shows the automation’s information and lets authorized users edit the description inline.Automation Activity Log Automations
Each automation includes an activity log that records what was added or changed in every publication and what is currently in the draft. The log shows who made each change and when, giving administrators visibility and audit-ability for how an automation evolves over time.Custom Managed Views: My Items Blocks Apps
App Admins can configure a My items block on a Custom managed view that locks the list to records created by the current user, so one view shows each person only the records they submitted. Admins can add a heading, a paragraph, and quick-filter pills above the list, and any filter, quick filter, or search the user applies is combined with the locked filter.Custom Managed Views V1 Apps
App Admins can create a Custom managed view in any app by describing it in a chat panel, and the builder composes a dashboard from the existing block catalog with each block bound to the app’s records and fields. The layout renders on the builder canvas before it is saved, and published views appear in the app’s view list with the same access policies as other managed views.OpenAI Realtime for Voice Agents Intelligence
Voice agents can be configured with an OpenAI Realtime setup that connects to your own OpenAI account and lets you choose the provider and model, while keeping existing authentication, prompt, and tool settings unchanged. The Realtime setup supports multi-lingual conversations, more natural interactions, and a larger context window than the existing voice pipeline.Customizable Voice Agent Authentication Emails Org Settings
Authentication emails sent when users request a PIN or one-time password from a voice agent can be customized with your organization’s branding and messaging. This gives users a consistent, recognizable experience when authenticating with your voice agents.Context & configuration
Context & configuration
Who can configure it: Organization Administrators.Where to find it: Admin → Settings → Communication → Email Templates.Configuration steps:
- Open Admin → Settings → Communication and select the Email Templates tab.
- Open the Voice PIN template. This email is sent when a caller requests an authentication PIN using a phone number already saved in the system.
- Edit the template content and colors so the message and branding match your organization, then save your changes.
- Open the One-Time Passcode template. This email is sent when a caller provides their employee ID and receives a code to use on the call.
- Edit that template’s content and colors the same way, including any instructions callers need, then save.
- These templates are in addition to the existing transactional email templates on the same Email Templates tab.
- Customizing the Voice PIN and One-Time Passcode templates changes what callers receive during voice authentication without changing the authentication flow itself.
Org-Scoped Deployment Org Settings
Deployment configuration in the target environment is shared across org admins rather than tied to whoever clicked Deploy, so any admin can pick up a deployment that is waiting on configuration and finish it. The Deployments page shows each environment’s most recent deployment state at a glance—Needs Configuration, Deploying, Deployed, or Failed—and configuration progress persists across sessions and handoffs.Portals v1 Org Settings
Org admins can create and manage portals from a new Portals page in Org Settings under Gateways, each with a name, description, icon, and shareable URL slug. Portals are built from managed views—set one as the homepage and add views from any app as menu items—so users signed in with their Elementum credentials see only the portal’s branded top bar and menu, with items filtered by each view’s access policy.Snowflake Postgres CloudLink Org Settings
Org admins can add Snowflake Postgres as a CloudLink provider under Admin > CloudLinks, connecting Elementum directly to a Snowflake Postgres database with password or key pair authentication over SSL. Builders can then select the connection when creating an Element or App, so records live in the Postgres database instead of a separate warehouse copy.Custom Transactional Email Templates Org Settings
Org admins can customize the four transactional emails Elementum sends on their behalf—welcome, password reset, email verification, and access link—from a new Email Templates tab under Admin > Settings > Communication. Each template’s title, body, safety note, call-to-action label, and per-template colors are editable, with dynamic variables like organization name and expiration, a live preview, and a per-template reset to the Elementum default.Dynamic Approvals: Delegation Apps
Approval delegation can read approver availability from Microsoft Outlook, fall back to an approver’s manager when no delegate is set, and honor a per-process delegation depth limit from 0 to 2. Approval routing adjusts to who is actually available without requiring every approver to configure a delegate in Elementum.Post-Deployment Unconfigured Elements Handling Apps
Deployed elements with incomplete configuration are automatically placed in maintenance mode, so end users see an Under Maintenance page in the list view instead of a partially configured element. Admins see a banner on the element details page until setup is finished, and both the banner and maintenance mode clear on their own once configuration is complete.Automations: Search Table Records Action Automations
A new Search Table Records action in the Automations action picker lets an automation look up data directly from a table instead of an app. Automation builders can source records from tables to drive downstream steps, expanding beyond app-only lookups.Automations: Run In Parallel Operator Automations
A Run In Parallel operator in the Automation Builder lets admins define multiple branches of tasks that execute simultaneously. Running branches at the same time reduces end-to-end runtime for automation steps that do not need to happen in sequence.Roll-Up Widget Apps
App administrators can configure a Roll-Up widget with a top-level filter and a custom hierarchy of tables or aspects, choosing which measures roll up and how they sum at each level. Reviewers see the summed total at the top and can drill down one level at a time to the underlying detail records driving that total.Context & configuration
Context & configuration
Who can configure it: App Administrators.Where to find it: App → a Dashboard view → 
- Open or create a Dashboard view in your app.
- Open the dashboard’s
- Enter a name for the widget and choose the aspect or records to aggregate. Apply a top-level filter only if you want to limit which records are included.
- Choose a number format: Standard shows full values, and Compact rounds with K, M, or B suffixes.
- Build the hierarchy by adding one or more group-by fields (with an optional label override for each level), then add the numeric measures to sum at each level.
- On Record fields, choose which fields appear when reviewers drill down to individual records. Include an identifier and title at minimum, and add any measure fields you want visible at that detail level.
- Review the configuration and click Create Rollup. Refresh the dashboard if the new widget does not appear immediately.
- Reviewers can drill from each hierarchy level down to the underlying detail records that drive the totals.
- Hierarchies can include more than one level when you need to organize the same measures in nested groups.
- A measure that appears in the roll-up totals is not shown on detail rows unless you also add that field under Record fields.
Data Entry View Apps
App administrators can configure a no-code Data Entry view that turns any app into an editable grid, choosing which fields are editable and how rows are filtered, sorted, and grouped. Users type or paste values directly into cells, save all edits at once, and see per-line and roll-up totals recalculate live as they work.Context & configuration
Context & configuration
Who can configure it: App Administrators.Where to find it: App → Manage Views → Create new view → Data Entry.Configuration steps:
- Open Manage Views, click Create new view, and select Data Entry.
- Choose a source aspect (the app whose records you want to edit in bulk).
- Select the field values users should edit. Leave other options at their defaults unless you need to change filters, sort, or grouping.
- Mark which of those fields are editable. For example, leave Title read-only and allow edits to budget or division fields.
- Under Display, set a Record label template so each row shows a clear label (for example, handle and title) using the available template references.
- Review the live preview of the editable grid, enter a name for the view, and click Save.
- Open the saved Data Entry view to confirm end users can edit cells and save changes in bulk.
- Editable cells currently support text and number fields. Other field types may appear in the view but are not editable.
- Users can copy and paste cell values with Ctrl+C / Ctrl+V (or Cmd+C / Cmd+V on Mac) to update many rows at once.
- Edits stay unsaved until the user clicks Save. Changed cells are highlighted so reviewers can see what will be written.
- The common use case is bulk-editing records in one app. Joining records across sources is a separate, more advanced configuration path.
Dynamic Approvals: SLAs Apps
Dynamic Approvals can be configured with an SLA policy that sets targets for each step in the process and sends alert emails to approvers at a configurable time before the deadline. When an SLA breaches, the approval workflow can branch on expiration to determine what happens next.Dynamic Approvals: Segregation of Duties Apps
Built-in compliance rules for Dynamic Approvals prevent the person who requested an approval from approving it, and prevent any single user from appearing more than once in the same approval chain. These rules help enforce segregation-of-duties requirements across approval workflows without additional configuration.Dynamic Approvals: Workflow Inspector Apps
Clicking an inflight approval opens a side panel with the full details of the approval process, including the current step, the assigned approvers, and progress so far. The panel is available from the Record Details page, the My Approvals page, and the approvals list on a record.Dynamic Approvals: Expiration Outcomes Apps
A new approval-process-level setting decides what happens when a step in a Dynamic Approval process fails to complete: reject, cancel, approve, or hold open. Approval processes conclude in a predetermined way instead of stalling in a pending state when a step expires.Dynamic Approvals Apps
A new Dynamic Approvals approval type lets app administrators route each request to the right user or group based on rules and record data, rather than hard-coding approver IDs. Chains can span multiple sequential steps with concurrent approvers at each step, and per-rule filters decide which approvers apply so approval processes adapt to the record instead of getting stuck.Context & configuration
Context & configuration
Who can configure it: App Administrators.Where to find it: App → Workflows & Processes → Approval Processes.Configuration steps:
- Open your App and go to Workflows & Processes → Approval Processes in the left navigation menu.
- Click Create New and choose the Dynamic Approval option.
- Enter a name for the approval process and click Save.
- Use the Table filter columns dropdown to select the fields the approvals will be filtered on.
- Click Add Step to build the approval as it progresses. For each step, configure the approver type, the users, and the preconditions that must be met, then save your changes for that step.
- Repeat the previous step for each step the approval should follow.
- Select Settings in the top-right corner to configure the approval name, expiration outcome, delegation depth, whether the approval can be started manually, locked fields, and SLAs.
- Steps run in the order you add them, and each step can have concurrent approvers who act at the same time.
- Save your changes for each step individually before moving on to the next one.
- Per-step preconditions decide whether a step applies, so the approval process adapts to the record instead of stalling on approvers who aren’t relevant.
- The Settings panel controls process-level options, including the expiration outcome that determines what happens when a step fails to complete, delegation depth, manual start, locked fields, and SLAs.
cXML Webhook Trigger Automations
You can now create a cXML Webhook Integration in Company Settings with the credentials required for cXML invoice event types, then use it as a trigger in automations. The trigger supports the synchronous responses that cXML requests require.Closed beta
These features are available to a limited set of customers by invitation and are not broadly available yet.- Elementum Development Kit (EDK) — A code-first toolkit for building Elementum in TypeScript as an alternative to building in the platform. Represent Apps, Elements, Automations, Agents, Skills, Flows, Search Tables, and Approval Chains as typed source, then follow a Terraform-like lifecycle: pull existing entities into a local workspace, author changes with typed
@catalogreferences, preview a structural diff withplan, and apply approved changes. Packaged coding-agent playbooks teach AI coding agents the EDK’s conventions, so you can describe an outcome in plain language and delegate the authoring from your editor or CLI. Get started with the EDK documentation to install the toolchain, authenticate, and bootstrap an organization workspace.