ReasonTrail for Teams is now available

Security

Project Secrets

Store project credentials without exposing them to members, chats, models, Resources, or MCP results.

Store, do not reveal

Project managers use Project → Secrets to enroll, rotate, enable, disable and revoke credentials. The optional username and credential value are envelope-encrypted and never appear in lists, browser read responses, exports, Resources, Brain memory, prompts or MCP results.

For MCP enrollment, the agent sends safe metadata to begin_project_secret_enrollment. The human opens the returned 15-minute authenticated link and enters the value there—not in chat.

Request an exact use

  1. List safe labels with list_project_secret_capabilities.
  2. Request one exact operation with request_project_secret_use.
  3. A project manager approves or denies it in Secrets.
  4. A typed server-side connector consumes the ten-minute grant once.

Approval never discloses plaintext to the model. Storage and approval do not perform an action unless a typed connector exists for that operation.

Membership and revocation

Members can request only capabilities whose audience allows project members. Current project and organization access is checked on every request and again before consumption. Removing access, rotating, disabling or revoking a credential cancels outstanding authority.