1. Overview
  2. Admin Guide
  3. Admin Guide Overview

Admin Guide Overview

Overview

The Admin Guide provides centralized control over access, governance, and system configuration in Peridot.

It is designed for teams responsible for securing AI usage across an organization, including cloud infrastructure engineers, security teams, and platform administrators.

Peridot operates as a control layer across AI systems. The Admin Guide defines how that control is enforced—through identity, permissions, environments, and auditability.

Who This Is For

This section is intended for:

  • Cloud infrastructure teams managing AWS, Azure, or GCP environments

  • Security engineers responsible for data protection and governance

  • Identity and access management teams configuring SSO and provisioning

  • Platform teams responsible for operational reliability

If you are responsible for system access, data exposure risk, or compliance, this section applies to you.

What Admins Control

Administrators are responsible for configuring and maintaining:

Identity and Access

  • User authentication (SSO)

  • Role-based access control (RBAC)

  • Group and role assignment

Governance and Enforcement

  • Policy visibility and control

  • Incident access and triage permissions

  • Enforcement boundaries

System Configuration

  • Integration access

  • Model provider configuration (BYOK)

  • API and token access

Audit and Compliance

  • Audit log access

  • Log exports

  • Activity tracking

How Peridot Maps to Cloud Architecture

Peridot is designed to align with enterprise cloud environments:

  • Identity providers (Okta, Entra ID, Google) map to user access

  • Cloud infrastructure (AWS, Azure, GCP) provides data and execution context

  • Peridot enforces governance across both layers

This means administrators do not manage isolated systems—they manage control across existing infrastructure.

Operational Responsibilities

In production, administrators are responsible for:

  • Defining access boundaries

  • Ensuring policies are enforced correctly

  • Monitoring audit logs and activity

  • Managing integrations and system access

  • Maintaining compliance requirements

In Production

A properly configured admin layer ensures:

  • No unauthorized access to AI systems

  • All activity is traceable and auditable

  • Policies are consistently enforced

  • Data exposure risks are minimized

Next Steps

  • Manage users in Members

  • Configure access in Roles and Permissions

  • Enable identity providers in SSO

Was this article helpful?