Security
Permissions, review, and scoped access remain part of every protected workflow.
Teri can help prepare sales-execution work, but TeriTrak’s backend remains responsible for identity, authorization, validation, and protected persistence.
Security principles
Sensitive changes stay reviewable
Deal-stage changes and other sensitive updates remain pending until an authorized user reviews them.
Permissions are enforced by the backend
Protected requests are checked against the user, organization membership, role, and permitted record access before data is returned or changed.
Data stays within its authorized scope
Private records remain private, and shared-deal access is limited to the collaboration context granted for that opportunity.
Integration credentials stay out of AI
Provider passwords, authorization tokens, and integration secrets are not sent to Teri or included in AI context.
AI output is validated before persistence
Structured AI results are checked against required fields, relationships, permissions, and business rules before a write is applied.
Identity and access
Protected requests are evaluated using the authenticated user, organization membership, role, team assignment, entitlement, record visibility, and collaboration scope where applicable.
Private and shared records
Private sales records remain scoped to authorized users. Shared-deal collaboration grants access to the relevant opportunity context without automatically exposing unrelated private records.
- Private receipts remain private unless specifically shared through an approved workflow.
- Raw voice recordings and raw transcripts are not general management-reporting data.
- OAuth credentials and refresh tokens are never exposed as ordinary customer records.
AI-assisted actions
Teri produces structured proposed actions. Required fields, relationships, permissions, stale-record protections, and business rules are validated before protected writes are accepted.
Have a security or procurement question?