Introduction to IO

Identity Orchestrator (IO) is a drag-and-drop framework for mapping user journeys during all phases of the identity lifecycle, including provisioning, authentication, and authorization. It helps you build user journeys with a codeless approach, drastically reducing integration complexity and time.

What is IO?

IO provides a visual interface for designing and managing complex user workflows without writing code. Using a node-based architecture, you can create sophisticated identity orchestration scenarios by connecting pre-built components that handle everything from user authentication to API integrations.

IO core concepts

Flows

A flow is a structured workflow pipeline composed of ordered processing steps. Each step executes a specific operation such as:

• Data transformation and validation
• User authentication and authorization
• Routing and conditional logic
• Integration with external systems
• Custom business logic execution

The flow defines the execution logic, data propagation rules, and conditional branching, enabling automated and consistent processing across the entire pipeline.

Nodes

A node represents a single, self-contained step within a flow. Each node performs a specific function and passes the result to the next node in the flow. Nodes are the fundamental building blocks used to create, customize, and manage flows.

Node types:

• Frontend (FE) nodes: Render user interfaces and collect user input.
• Backend (BE) nodes: Execute server-side logic and API calls.
• Decision nodes: Implement conditional logic and branching.
• Integration nodes: Connect to external services and APIs.

Flow execution

Flows are executed in response to user actions or system events:

1. User initiates flow: A user or system triggers the flow start.
2. Session created: IO creates a session to track the flow state.
3. Nodes execute: Each node processes sequentially.
4. Data stored: Variables and data persist in the session context.
5. Flow completes: The flow reaches an end state (success or failure).

How IO works

IO uses a graph-based workflow model where each operation is represented as a node. Nodes perform specific tasks and are connected through directional links that define both the execution path and the data flow.

The visual node-based model allows you to design even complex pipelines in an intuitive way, while maintaining full control over input and output structures, conditional branching, triggers, and execution logic across the entire process.

Visual designer

The IO designer provides an intuitive interface with:

• Drag-and-drop: Drag from the palette to add nodes.
• Visual connections: Connect outputs to inputs to link nodes.
• Node configuration: Configure each node's behavior and parameters.
• Variable management: View and manage flow variables.
• Flow settings: Control flow-level configuration.
• Version control: Track and manage flow versions.

Session management

Each flow execution creates a unique session that:

• Stores flow state and variables
• Manages user context and authentication
• Persists data across node executions
• Expires based on configured Time To Live (TTL)
• Provides isolation between concurrent executions

Data flow

Data flows through the workflow via variables:

• Input variables: Data passed into nodes
• Output variables: Results produced by nodes
• Flow variables: Shared across all nodes in the flow
• Session variables: Persist throughout the flow execution

Flow categories

IO supports multiple flow categories for different use cases:

Authentication flows

Manage user login and logout processes:

• Username and password authentication
• Multi-factor authentication (MFA)
• Social login integration
• Passwordless authentication
• Session management

Self-service flows

Enable users to manage their own accounts:

• User registration
• Password reset
• Profile updates
• Account recovery
• Preference management

Admin flows

Administrative operations for user management:

• User provisioning
• Account lifecycle management
• Bulk operations
• Administrative approvals

API flows

Backend integrations and web hooks:

• API orchestration
• Data synchronization
• Event-driven workflows
• Integration with external systems

Consent flows

Manage user consent and preferences:

• Cookie consent
• Data processing consent
• Communication preferences
• GDPR compliance

Custom flows

Build any custom workflow specific to your needs:

• Business-specific processes
• Complex integrations
• Specialized user journeys

Library flows

Reusable sub-flows that can be called from other flows:

• Shared logic components
• Common validation routines
• Modular workflow building blocks

Key features of IO

Multi-tenant architecture

IO supports multiple tenants with complete isolation:

• Separate flow configurations per tenant
• Independent session management
• Isolated data storage
• Per-tenant customization

Localization

Build flows that support multiple languages:

• Upload language files per flow
• Dynamic language selection
• User-agent based defaults
• Complete UI translation support

Theming and customization

Customize the look and feel:

• Custom CSS per flow or node
• Brand-specific styling
• Logo and color customization
• Responsive design support

Import and export

Share flows between environments:

• Export flows as JSON files
• Import flows with optional ID preservation
• Copy flows between tenants
• Version migration support

Versioning

Track and manage flow changes:

• Create multiple versions of a flow
• Test new versions without affecting production
• Restore previous versions
• View version history

Debugging

Test and troubleshoot flows:

• Step-by-step execution
• Variable inspection
• Error tracking
• Execution logs

Benefits of IO

For business users

• No coding required: Build complex workflows visually.
• Rapid prototyping: Quickly test new user journeys.
• Easy modifications: Update flows without technical dependencies.
• Clear visualization: Understand workflow logic at a glance.

For developers

• Reduced development time: Focus on business logic, not infrastructure
• Consistent architecture: Standardized approach to workflow management
• Easy maintenance: Visual flows are self-documenting
• Integration friendly: Connect to any API or service

For organizations

• Faster time-to-market: Deploy new journeys quickly
• Lower costs: Reduce development and maintenance overhead
• Better agility: Adapt to changing requirements easily
• Improved compliance: Clear audit trail of user journeys

Next steps

Ready to start using IO? Continue with:

• Getting started with IO: Set up your first flow.
• Flow management: Learn about flow operations.
• Node reference: Explore available nodes.
• Flow categories; Understand flow types.