Control access and see the results
Choose who can view, change and run workflows. Check new settings before using them, then see what ran, which data was written and where an error occurred.
Permissions · version · checks
Checked rules before production writes
Access aligned with roles and scenarios
Execution outcomes with context for investigation
Check changes before publishing
Work with a draft, inspect intermediate data and complete a simulation before using changes operationally. Simulation reads sources, applies transformations and checks destinations without writing to business systems. The published version defines the logic used by configured automated and external launches.
- Draft and published flow versions
- Simulation and intermediate data previews
- Error explanations associated with the relevant blocks
Grant the level of access people need
Use roles to define access to flows and interface sections. API clients can receive read or write permissions for selected flows, while button operators are governed by its access settings. This helps assign everyday execution, integration and logic changes to the appropriate people.
- Roles for flows and system capabilities
- Separate API-client permissions and key management
- Allowed pages and operators for embedded buttons
Assign responsibilities
Separate administration, editing, execution and API-access responsibilities.
Configure the rules
Agree validation, keys, limits and access to organizational resources.
Check the scenarios
Exercise successful runs and expected failures in a controlled environment.
Use the history
Review outcomes and investigate exceptions before repeating actions.
See the actual outcome of a write
History distinguishes successful completion from errors, partial results and cases requiring reconciliation. When an external system does not confirm a write, checking its state before retrying matters. Flows can also detect conflicts between destinations that would modify the same elements.
- Run states and execution logs
- Context for validation, delivery and errors
- Checks for overlapping writes between flow destinations
Configure the environment for your organization
Choose cloud or local hosting and agree access rules for your sources. Connections keep their secrets on the server, while the agent further restricts local resources. Limits, history and API auditing help operate the environment according to the workload and the team’s internal procedures.
- Cloud or locally hosted Data Bridge
- Connection management and agent resource permissions
- Execution, history and API audit limits
Permissions · version · checks
Your questions, answered.
How to connect your data, manage access and get started.
Does simulation avoid contacting sources?
No. It performs real reads and transformations but does not write results to business destinations. Use suitable test sources for demonstrations.
What does Reconciliation required mean?
The system did not receive sufficient confirmation of a write outcome. Check the destination and execution log before repeating the run to avoid unwanted duplication.
Can local folder access be managed separately?
Yes. Specific folders and permitted operations are configured on the agent computer, complementing permissions within Data Bridge itself.
Let’s start with your task.
Tell us which data you need to connect. We will explain how it works and show you an example.
Bring your challenge. See a way forward.
Sources, rules and outcomes — let’s build the conversation around your workflow.