Auto Arrange: One-Click Clean Layout for Workflows

Workflow design in Nimbus just got easier. With the new Auto arrange button, Nimbus users can now instantly arrange the layout for their entire workflow: Blocks are neatly positioned and connector lines stay easy to follow, no matter how large or complex the workflow gets. One click is all it takes to keep a flow looking sharp, any time structural changes are made.

🆕What will be added to Nimbus?

• Workflow editor and workflow template editor: a new Auto arrange button in the toolbar, alongside Expand all, Collapse all, and Fit to screen.
• One click arranges the entire flow into a clean top-down layout: blocks are positioned automatically, and existing connectors redraw over the new layout.
• Available any time, so Nimbus users can re-arrange a flow whenever they like, including right after adding or restructuring blocks.
• Disconnected blocks (with no path from START) are placed predictably; wider blocks automatically get the spacing they need.
• In the template editor, all blocks are arranged, including locked ones. Lock state only guards block configuration, not canvas position.
• The new layout is applied immediately and persists on the next Save; discarding or cancelling the edit restores the previous layout.

UI Profiles: Tailor the Portal Menu per User Role

Administrators can now shape the Nimbus User Portal menu to match each user's role. With the new UI Profiles, admins can define exactly which pages appear in the navigation menu and which page opens by default after login. Agents, supervisors, and other roles each get a Nimbus Portal experience tailored to what they actually need.

🆕What will be added to Nimbus?

• A new UI Profiles configuration page under Admin Portal > Configuration > UI Profiles.
• Administrators can define visible menu pages per profile, set custom icons and tooltips per page, and configure a default landing page.
• UI Profiles can be assigned to individual users or in bulk via Extensions User Settings.
• Pages not included in a profile are hidden from the menu but remain fully reachable via direct links, such as deep links or contextual actions elsewhere in Nimbus Portal.

Export Workflows and Templates via API

Building on the existing Workflow Export/Import feature, the new Export Workflows and Templates via API allows Tenant Administrators to gain full control over how and when their workflows and workflow templates are backed up. Exports can be scheduled and automated, integrating workflow protection directly into existing IT processes on top of the export options already available in the portal.

🆕What will be added to Nimbus?

• A new export API endpoint for workflows and workflow templates, usable alongside the existing portal-based export.
• Export scope can be set at tenant or OU level, so administrators can pull an entire tenant's workflows or just those belonging to a specific organizational unit.
• An overwrite parameter controls whether existing local files are refreshed or preserved, making it easy to keep a local archive current without duplicating or overwriting unchanged definitions.
• Enables fully automated, scheduled backups (e.g. a monthly export job) without manual intervention.

Bulk Export for User and Service Configuration

With Bulk Export, all users in Administrator roles can export all user and service configurations within an Organization Unit, or across the whole tenant, in a single operation, giving them a fast, reliable way to capture configuration snapshots at scale, without giving up the precision of selecting specific entities when that's all that's needed.

🆕What will be added to Nimbus?

• OU-scoped export: select an OU in the grid filter and export all users/services* within it in one file — useful for backups, reviews, or migrations.
• Whole-tenant export: clear the OU filter to export the entire tenant's user/service configuration in a single operation.*
• Hand-picked export remains available as before, for exporting only specific, manually selected entities.
• Choose the output format — JSON (combined) or CSV — depending on how the export will be used downstream.

💡*Note that exports are automatically bounded by the administrator's authorized OU scope — an admin with access to only a subset of OUs will only ever receive the entities they're permitted to see, even when running a whole-tenant export.

Virtual User Configuration: Simplified Setup with Clearer Structure

Configuring a Virtual User is now faster and more intuitive. The configuration page has been reorganized into three clear tabs — General, Behavior, and Tools and Outcomes — guiding Nimbus users step by step through setting up behavior, conversation flow, and tools, without needing to consult detailed documentation. Terminology has also been standardized throughout, making it clearer what each field actually controls.

🆕What will be added to Nimbus?

• A new tab-based layout for Virtual User configuration: General (name, description, bot/profile assignment, modalities, license), Behavior (instructions, messages, timeouts, voice & persona settings), and Tools and Outcomes (conversation flow instructions, outcomes, and extensions like Web Requests or MCP Server).
• Standardized terminology: fields that shape the Virtual User's behavior are consistently labeled as Instructions (i.e. prompts used to steer how the Virtual User behaves) — clearly distinguished from descriptive fields, like Description or the Initial/Final Message to Customer, which are not prompts.
• The previous Role field is now marked (Deprecated) to reflect that its purpose is now covered by the General Instructions field.
• Overall, a simpler, more guided configuration experience with better control over how your Virtual User works.