Skip to main content

Start here: set up and use Tutela

Documentation for Tutela v3.9.0.

Start with your current task. If Tutela is already installed, use your organization's deployment address to sign in; this documentation website is not the application.

Prerequisites​

  • Your deployment address, or the installation package if you are deploying Tutela.
  • An account with the permissions needed for the task. Ask your administrator when a named page is not visible.

Deploy and verify​

  1. Deploy and activate Tutela in the AWS account and region agreed with your operator.
  2. Configure the first administrator, team access and an AI connection in your deployment's Settings and Settings > Runtime setup.
  3. Verify your installation with a harmless request and its matching Activity record.

Choose an AI connection​

You want to protectSetup location in TutelaWhat to check afterward
Browser use of supported AI sitesSettings > Runtime setup > Downloads > BrowserA test prompt is inspected and recorded; a connected extension alone is insufficient.
An application's AI requestsSettings > Runtime setup > Providers and DownloadsThe application uses your Tutela gateway and its request appears in Activity.
An agent's tool callsTools & MCP ServersThe client uses the registered Tutela connection and a read-only call produces evidence.

Use your deployment's Help Center for the setup procedure matching the installed client. A detected application is not automatically connected to any of these paths.

Operate and investigate​

Find an answer​

Search accepts task names such as “restore backup” or “missing activity.” It searches locally in your browser. If a guide differs from your installation, record the page address, product and client versions, and the step that differs.

For help, open Settings > Support & diagnostics in Tutela or contact support@h2htech.com if the application is unavailable.

Validate​

  • You selected a guide for the task and connection you actually use.
  • You checked its access requirements and expected result.
  • You have an owner for any failed or unconfirmed step.

Next steps​

Match documentation to your installation​

Stable releases come from Tutela's stable release process. The public documentation site describes its identified product release; an individual installation may run an earlier build. Check the installed version before assuming a newer Help article or fix is present. An application release, a corrected deployment package and a documentation revision can have different identifiers. Ask the operator for the release notes and matching package rather than installing an arbitrary branch tip.

Fresh installations use the established first-sign-in flow and require a password change. They do not contain customer policies, provider connections or demo activity. After onboarding, customers configure providers and policies themselves. Real-time search is built in and becomes usable through a supported search-capable provider connection. An upgrade preserves existing customer configuration and passwords.