> ## Documentation Index
> Fetch the complete documentation index at: https://www.scrums.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How the Platform Works

> Follow the path from workspace setup and tool connections to governed deployments and engineering intelligence.

## The platform flow

Scrums.com connects your engineering systems to a governed workspace. You can then deploy catalog records, delivery scopes, engineers, and teams while measuring them through one operating layer.

### 1. Create a workspace

Your workspace holds members, integrations, policies, deployments, and reporting. Start with [first-time setup](/docs/getting-started/first-time-setup).

### 2. Connect your tools

Connect source control, project management, CI/CD, quality, communication, and observability systems. Scrums.com normalizes their signals without requiring you to replace your existing workflows.

### 3. Deploy what you need

Choose an item from the [AI Catalog](/docs/catalog/overview), define an [AI Development scope](/docs/ai-development/scopes), or add capacity through [Hire](/docs/hire/overview). Checkout creates a separately tracked deployment for each service line.

### 4. Apply governance

Workspace roles, policies, approval boundaries, and audit records determine who can see and operate each deployment. Agent actions follow the same governance model.

### 5. Measure and improve

Use [team observability](/docs/platform/team-observability) to follow delivery, workflow, quality, and capacity trends. Name the constraint, make a change, and measure the result.

## Identity model

The core hierarchy is:

**Organization → Workspace → Service line → Deployment**

Projects are cross-cutting labels. They help you group work without changing the ownership hierarchy.

## Related

* [Core concepts](/docs/platform/core-concepts)
* [Deployments](/docs/products/deployments)
* [Integrations](/docs/integrations/integrations)
* [Governance](/docs/governance/governance)