Control what your AI employees can access and do.
Choose the accounts you connect, the tools each employee can use, and the actions that need approval. Here’s how Yodu handles access, credentials, and workspace data.
Separate company workspaces
Data and tool access are scoped to your company workspace. Each workspace has its own runtime container. Employees in the same company can share context; they are not isolated tenants.
Encrypted credentials
Add credentials through connection and secret settings. Stored secrets are encrypted, and normal read APIs do not return their values. Connected services and model providers process data under their own terms.
Configurable permissions
Choose which tools each employee can use, then set its permission mode. Draft only and Ask first limit external actions. Autonomous modes allow broader actions, so check the settings before enabling them.
Activity you can review and access you can revoke
Inspect tasks, evidence, and approvals. Remove employee access, disconnect integrations, or rotate credentials when needed. Contact us for help exporting or deleting a workspace.
Runtime and onboarding checks
During onboarding, we review runtime health, backup records, and the access and approval settings for your workflow. Yodu is not SOC 2 or ISO certified.