Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.neuraltrust.ai/llms.txt

Use this file to discover all available pages before exploring further.

Every NeuralTrust tenant is called a Team. A team is the top-level container that holds your users, roles, integrations, audit history, and the products provisioned for you (Agent Runtime by TrustGate, Agent-SPM by TrustLens, TrustTest, and anything else). Team Settings is the admin surface where you configure the team itself — everything that lives above the individual products. Open it from the left-hand nav → Team settings. The docs mirror the sidebar and are organized into the same themed groups.

What you can configure

Team

The tenant’s identity — who it is, who’s in it, and which models it uses internally.

General

Team display name and team deletion.

Users

Members, invitations, roles, and per-product access.

Models

LLM and embeddings providers used by NeuralTrust features.

Identity & Access

How people sign in and what the platform lets them do.

SSO Configuration

Microsoft Entra ID and generic OIDC single sign-on, with break-glass emergency access.

SCIM Provisioning

Automatic user creation and removal driven by Microsoft Entra ID.

User sync & group mappings

Map identity-provider groups to NeuralTrust team roles and product access.

Password Policy

Minimum length, character classes, and common/personal-info blocks.

Audit & Compliance

Evidence for SOC2 and incident response, plus the platform’s security posture and data-privacy model.

Audit Logs

SOC2-grade security event log with filtering, search, and export.

SIEM Integration

Forward audit events to Splunk, Elastic, IBM QRadar, Microsoft Sentinel, or Datadog.

Security posture

Platform-wide authentication, access control, networking, and encryption guarantees.

Data privacy

Data sovereignty, GDPR / HIPAA / SOX compliance, and the privacy-by-design architecture.

Infrastructure

Where the NeuralTrust app and its data plane actually live — and how to deploy them.

Custom Domain

Serve the NeuralTrust app on a hostname you own via a CNAME.

Data plane (Advanced)

Provision a hybrid data plane in your own AWS, GCP, or Azure account — or connect an existing one.

Architecture

Control plane, data plane, and deployment modes (SaaS, Hybrid, On-Premises).

Deployment guides

Cloud-specific install guides for AWS, Azure, GCP, Kubernetes, and Docker.

Feature Flags

Feature Flags

Toggle preview and early-access capabilities for the team.

Who can do what

Access to Team Settings is gated by team role — an organization-wide role that sits above per-product roles.
RoleScope
OwnerFull control of the team. Can change the team name, delete the team, configure SSO, manage break-glass users, rotate SCIM tokens, provision data planes, and toggle feature flags.
AdminDay-to-day administration. Manages users and invitations, verifies email domains, edits group mappings, reviews audit logs, and configures SIEM and password policy.
MemberUses the products they have access to. Cannot see Team Settings.
Individual products (TrustGate, TrustTest, …) have their own role model on top of this — a team Admin is not automatically a product admin, and vice versa. For a fresh team, configure Team Settings in this order:
  1. General — set a human-readable team name.
  2. SSO Configuration — pick Microsoft Entra ID or generic OIDC.
  3. Break-glass access — add at least one emergency user before enforcing SSO.
  4. Password Policy — tighten local passwords for accounts that keep them.
  5. SCIM Provisioning (Entra ID) — automate user creation and removal.
  6. Group mappings — map IdP groups to NeuralTrust roles.
  7. Users — invite anyone not provisioned by SCIM and assign per-product access.
  8. SIEM Integration — forward audit events to your security platform.
  9. Custom Domain — if you want the app on your own hostname.
  10. Advanced — provision a hybrid data plane if you’re on a hybrid or self-hosted plan.

Prerequisites

  • NeuralTrust account with Owner or Admin role.
  • For SSO: administrator access to your identity provider.
  • For hybrid provisioning: admin access to the target AWS / GCP / Azure account.
  • For custom domain: control over the DNS zone of the domain you want to use.

Support

If you hit an issue configuring the team, reach out at [email protected].