An AI Workflow Platform With Controlled Role Access

Control who builds and runs your enterprise AI workflows. Jinba combines role based access with approved execution, explicit exception routing, and audit logs for banking and insurance teams.

Book a Demo

Build a workflow for bank IT automation to handle governing access to a KYC review workflow using submitted KYC inputs and approved customer-system records. Deny unauthorized requests and route missing identifiers or conflicting customer records to compliance review before release. Check execution permissions before accessing sensitive inputs and require explicit reviewer approval before releasing a result. Log access outcomes, source references where permitted, validation checks, and reviewer decisions; never publish knowledge changes from this review workflow.

Building workflow...
Scroll to see workflow

Trusted by

Suntory
Writeup Consulting
bloomo
Suntory
Writeup Consulting
bloomo
Suntory
Writeup Consulting
bloomo
Suntory
Writeup Consulting
bloomo
Suntory
Writeup Consulting
bloomo
Suntory
Writeup Consulting
bloomo
Suntory
Writeup Consulting
bloomo
Suntory
Writeup Consulting
bloomo
Suntory
Writeup Consulting
bloomo
Suntory
Writeup Consulting
bloomo
Backed by Combinator

Separate Workflow Building From Authorized Execution

Workflow diagram

A shared automation needs clear ownership and execution permissions. Jinba provides role-based access control, SSO, and audit logging. Builders create and test KYC review logic in Jinba Flow; authorized staff run it in Jinba App. Define standard and exception review paths, and validate your required permission boundaries before deployment.

  • Describe the governing access to a KYC review workflow workflow in Jinba Flow chat, then refine and test its visual flowchart.
  • Deny unauthorized requests and route missing identifiers or conflicting customer records to compliance review before release. Set explicit standard and exception review paths in the workflow.
  • Validate required customer identifiers, document status, and reviewer assignment and enrich them from connected, authoritative systems before review.
  • Record validation and reviewer decisions in the workflow log, and let authorized staff run approved workflows through Jinba App.

Build Deploy and Run Your Governed Workflow

Send weekly metrics to Slack every Monday at 9am
1
Build in Jinba Flow

Define the builder, runner, and reviewer roles for your KYC workflow. Describe the process in Jinba Flow, refine its visual flowchart, and test required inputs and exception paths. Verify the required platform permission boundaries rather than assuming per-step access controls.

test_runner.log
Running workflow test...
✓ Input validation 12ms
✓ Fetch from Sheets API 847ms
✓ Process 24 rows 156ms
✓ Send to #sales 203ms
PASS All steps completed 1.22s
Output preview:
"sent": true, "channel": "#sales"
2
Deploy securely (API / batch / MCP)

Publish the tested workflow as an API, batch process, or MCP server. Configure the agreed deployment with SSO, role-based permissions, and audit logging, then verify allowed and denied operations before production use.

3
Run in Jinba App (guardrailed UI)

Authorized staff submit requests through Jinba App chat or generated forms. The workflow applies configured rules, routes evidence gaps to reviewers, and releases only approved results. Log held and denied outcomes too; proposed knowledge changes use a separate validation and approval process.

Enterprise Ready

Control, security, and support for large organizations.

On-Prem
Jinba
Private

On-premises or private cloud hosting

Run Jinba in your own environment with full data control.

Team Permissions
128 Active
Sarah Chen
Sarah Chen Engineering Lead
Workflows
Michael Ross
Michael Ross Product Manager
Analytics
Guest User
Guest User External Auditor
Admin Access
SSO Enforced
Updated 2m ago

Advanced access control

Role-based permissions and SSO integration.

audit_stream.log
1
[200] 09:14:22 GET /api/v1/health_check
2
[INFO] 09:14:23 Worker node_04 connected
3
[AUTH] 09:15:01 User admin@corp verified
4
[AUDIT] 09:15:02 Role assignment update
5
// Syncing to edge...
6
[200] 09:15:08 Config updated

Audit logging

Complete compliance and security oversight tracking.

User
Marketing
RESTRICTED
HR
ALLOWED
Screening
Automation

Organization management

Spaces, roles, and approvals for your team.

OpenAI
Gmail
Slack
HubSpot
Salesforce
Notion
Linear
GitHub
Teams
Dropbox
OpenAI
Gmail
Slack
HubSpot
Salesforce
Notion
Linear
GitHub
Teams
Dropbox

Pre-built & custom integrations

100+ pre-built integrations plus custom connectors for your internal systems.

Alice
Alice 10:42 AM
We need a connector for our internal CRM. Is this possible?
James
James 10:43 AM
Sure! Can you share the API spec?
Alice
crm_api_spec.pdf
James
Got it. I'll have the connector ready by tomorrow.
James
James Next day
Connector is live!
Alice
Thank you!

Dedicated Engineer Support

Work side-by-side with our engineers to remove blockers and accelerate your workflow development.

AWS Bedrock Claude 3.5 Sonnet
Azure OpenAI GPT-4 Turbo
Meta Llama 3 Self-hosted 70B

Private model hosting

Use Bedrock, Azure AI, or your own models securely.

On-Prem
Jinba
Private

On-premises or private cloud hosting

Run Jinba in your own environment with full data control.

Team Permissions
128 Active
Sarah Chen
Sarah Chen Engineering Lead
Workflows
Michael Ross
Michael Ross Product Manager
Analytics
Guest User
Guest User External Auditor
Admin Access
SSO Enforced
Updated 2m ago

Advanced access control

Role-based permissions and SSO integration.

audit_stream.log
1
[200] 09:14:22 GET /api/v1/health_check
2
[INFO] 09:14:23 Worker node_04 connected
3
[AUTH] 09:15:01 User admin@corp verified
4
[AUDIT] 09:15:02 Role assignment update
5
// Syncing to edge...
6
[200] 09:15:08 Config updated

Audit logging

Complete compliance and security oversight tracking.

User
Marketing
RESTRICTED
HR
ALLOWED
Screening
Automation

Organization management

Spaces, roles, and approvals for your team.

OpenAI
Gmail
Slack
HubSpot
Salesforce
Notion
Linear
GitHub
Teams
Dropbox
OpenAI
Gmail
Slack
HubSpot
Salesforce
Notion
Linear
GitHub
Teams
Dropbox

Pre-built & custom integrations

100+ pre-built integrations plus custom connectors for your internal systems.

Alice
Alice 10:42 AM
We need a connector for our internal CRM. Is this possible?
James
James 10:43 AM
Sure! Can you share the API spec?
Alice
crm_api_spec.pdf
James
Got it. I'll have the connector ready by tomorrow.
James
James Next day
Connector is live!
Alice
Thank you!

Dedicated Engineer Support

Work side-by-side with our engineers to remove blockers and accelerate your workflow development.

AWS Bedrock Claude 3.5 Sonnet
Azure OpenAI GPT-4 Turbo
Meta Llama 3 Self-hosted 70B

Private model hosting

Use Bedrock, Azure AI, or your own models securely.

Talk to Our Team

Discuss governing access to a KYC review workflow with Jinba. Contact sales to scope the sources, review rules, deployment requirements, and evaluation criteria for your department.

Book a Demo

Frequently Asked Questions

Everything you need to know about Jinba. Can't find the answer you're looking for? Reach out to our support team.

What does RBAC mean for a Jinba workflow?

RBAC means role-based access control: permissions depend on an assigned role. Jinba documents role-based permissions and SSO. Define which teams need builder and runner access, then verify those boundaries in your deployment. Do not assume that platform RBAC proves a specific per-node, record-level, skill-level, or connector-level permission model.

Are role permissions the same as approval routing?

No. Permissions determine whether a user can access an operation; workflow routing determines which authorized reviewer handles a case. Use both. In the example, unauthorized requests stop before customer data is processed, while missing or conflicting KYC data routes to a compliance reviewer.

How do teams build and run the workflow?

Builders describe the process in Jinba Flow, refine its visual flowchart, and test it with representative data. Workflows can be deployed as APIs, batch processes, or MCP servers. Authorized business users run approved workflows in Jinba App through chat and generated input forms. Knowledge connections and review rules must be configured for your use case.

What validation and approvals are included?

Configure required KYC fields, authoritative customer-system checks, and standard versus compliance review paths. Platform access controls and workflow decision rules serve different purposes. In this example, release requires both completed evidence checks and explicit reviewer approval. Missing approval or unresolved evidence produces a held outcome, not an approved result.

What can our team trace during review?

Jinba provides platform audit logging. Configure this workflow to record access outcomes, validation results, reviewer decisions, and release or hold status. Agree log retention, sensitive-data handling, and required evidence with your security team; the exact fields in this example are workflow requirements rather than a claim about a fixed built-in log format.

Can we run Jinba on our infrastructure?

Jinba offers on-premise and private-cloud deployment. The Brain overview describes unmodified raw data in an on-premise store. For an air-gapped requirement, agree a locally hosted model and source connections that work within the network boundary. Managed services such as AWS Bedrock or Azure AI require connectivity and are not interchangeable with a fully disconnected deployment.

How should we start and measure success?

Start with one KYC workflow and representative builder, runner, and reviewer roles. Test allowed and denied requests, missing data, exception routing, and audit evidence before rollout. Agree the integration scope and acceptance criteria with Jinba; deployment speed depends on your systems and security review.

Build your governed workflow with Jinba

Talk to our team about your process, integrations, and deployment requirements.

Book a Demo