IO flow management

Flow categories

IO organizes flows into categories based on their purpose:

• Authentication flows manage user login and logout processes. For example: username and password authentication, multi-factor authentication (MFA), social authentication, passwordless login, and session management.

• Self-service flows enable users to manage their own accounts for user registration, password reset, profile updates, account recovery, and preference management.

• Admin flows support operations for user provisioning, account lifecycle management, bulk operations, and administrative tasks.

• API flows support backend integrations and web hooks for API orchestration, data synchronization, event-driven workflows, and integration with third-party services.

• Consent flows manage user consent and preferences. For example, cookie consent, data processing consent, communication preferences, and GDPR compliance.

• Custom flows can be created to meet your organizations specific requirements.

• Library flows include reusable sub-flows that can be called from other flows. For example, shared logic components, common validation routines, and modular workflow building blocks.

Flow types

Start node

Every flow begins with a Start node that defines: the entry point, the initial context and state, and the output connectors.

Processing nodes

The main body of the flow contains: frontend nodes for user interaction, backend nodes for processing logic, decision nodes for conditional routing, and integration nodes for external services.

End nodes

Flows terminate with End nodes. End Success signals that the flow completed successfully. End Failure signals that the flow encountered an error.

Flow settings

Flows support various configuration options:

General settings

• Name: Unique identifier for the flow
• Description: Detailed explanation of purpose
• Active: Turn flow execution on or off
• Default: Set as primary flow for the category
• Tags: Tag flows for easy filtering. Use categories to organize flows by purpose.

Execution settings

• Session TTL: Specify how long the session remains valid
• Node tracking: Log detailed execution information
• Error handling: Configure error behavior

Localization settings

• Language files: Upload translations
• Default locale: Set fallback language
• Locale detection: Automatic language selection

Security settings

• Authentication required: Enforce authentication
• Authorization rules: Control access to the flow
• Data encryption: Protect sensitive data