Security
Security is part of the managed workflow model.
Underdata keeps recurring data work inside managed workspaces where access, approved sources, review state, sharing, and publishing can be controlled around the workflow.
Security question
Who can access the workflow, what sources can it use, and when is the answer safe to share?
Managed workspace boundaries
Underdata is operated as a managed SaaS, so workspace access, membership, settings, and plan boundaries are part of the service model.
- Workspace membership
- Plan and access controls
- Central settings for recurring work
Governed source access
Workflows are designed to run through approved data sources instead of ad hoc copies, helping teams keep sensitive analysis inside controlled execution paths.
- Approved data-source connections
- Execution tied to workflow context
- Less spreadsheet handoff for repeated questions
Review before sharing
Security also depends on how answers move. Underdata helps teams review results, preserve context, and publish only the outputs that should reach business users.
- Review state before publication
- Sharing controls
- Published dashboards and apps connected to source workflows
Security controls follow the workflow
- Invite
Grant workspace access to the people who should participate.
- Connect
Use approved data sources for governed workflow execution.
- Run
Keep execution and supporting evidence attached to the workflow.
- Review
Confirm the answer before it becomes reusable operating work.
- Share
Publish dashboards and apps with the right audience and context.
What security supports
Business users receive the right answer through the right published surface.
Analytical evidence stays connected to governed sources and workflow history.
Teams can discuss access, data handling, and operating requirements with Underdata before launch.
Review security with the workflow scope.
During private beta, Underdata works with each team to understand access, source, review, and publishing requirements for the first workflows.