ReasonTrail for Teams is now available

Security

Access is scoped before context is assembled.

This page describes implemented product boundaries and operating practices without claiming certifications or guarantees that have not been documented.

01

Authentication

Server-side sessions protect browser routes. Where public signup is enabled, new email/password accounts require email verification. Microsoft and Google sign-in follow the configured connection and ReasonTrail membership rules. Team organizations can configure OIDC or SP-initiated SAML 2.0 with signed assertions. Company identities must be explicitly linked from an existing authenticated account; identity-provider membership alone does not grant ReasonTrail access. Mutations use CSRF protection, and accounts or organizations can be suspended.

02

Tenant isolation

MCP validates organization, project access and token restrictions server-side. Authorized project agents can search non-private turns of linked conversations; other members cannot open transcript pages, private turns or source metadata.

03

Provider boundary

Only selected context is sent. Provider keys remain server-side; models do not receive database credentials.

04

Review + authorization

Important proposals remain reviewable. Sensitive Operator approvals are scoped to a single owner and run.

MCP and Operator v1

Models do not receive unrestricted system access.

These restrictions describe ReasonTrail MCP and Operator v1. A separately enrolled Runtime executes authorized Work in its mapped workspace under its own provider and execution policy.

× No unrestricted shell access× No unrestricted filesystem access× No arbitrary repository mutation× No deployment access× No browser automation access× No credentials or database connections

Data operations

Inspectable records and bounded logs.

ReasonTrail preserves failed runs, verification evidence, approvals, and audit history for diagnosis.

PostgreSQL storageBackupsJSON exportsMarkdown exportsAudit eventsBounded, redacted logs