Security

Access is checked on the server.

Workspace membership and roles determine access to protected operations. Administrative actions check current membership rather than relying only on a previously issued session. Business access is checked within the workspace.

Browser-initiated changes use same-site and anti-forgery checks. Public provider callbacks and workflow entry points use their route-specific authentication or token checks.

Integration credentials are encrypted.

The integration credential vault uses AES-256-GCM authenticated encryption with a fresh nonce for each encrypted value. Its authentication context binds the encrypted value to the context used when storing it.

Configure credentials through your workspace's connection settings. Use the permissions required by the operations you intend to run, and revoke or replace credentials in the provider when access should end.

AI uses the context you configure.

AI requests can send instructions, customer content, selected knowledge, and tool results to the configured model provider. Review the provider's data terms before using sensitive information in a workflow.

Choose the agent's tools and run limits deliberately. Provider retention and usage charges depend on the account and service in use.

Put people before consequential actions.

A workflow can pause for human approval before continuing along its approved or rejected path. Place that step before the external action that needs review. Run history and step results help your team inspect what happened.

A connection being verified does not mean every action is appropriate. Review the account, target records, and permissions for each process.

Review your deployment requirements.

For requirements such as hosting region, retention, backup recovery, or a data processing agreement, obtain the applicable details from your NodeHub operator before placing regulated or sensitive data in the workspace.