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

# Concepts

> Understand the public concepts used in the Acrity Console.

## Workspace

A workspace groups users, repositories, credentials, connectors, webhooks, API keys, review settings, and billing data. Most Console screens always operate within the active workspace.

The diagram below shows how these objects relate. A workspace holds its members and configuration, and each repository is where a pull or merge request becomes a review.

```mermaid theme={null}
graph TD
    Workspace --> Repositories
    Workspace --> Credentials
    Workspace --> Connectors
    Workspace --> Webhooks
    Workspace --> APIKeys["API keys"]
    Workspace --> Policy
    Workspace --> Billing
    Workspace --> Members
    Repositories --> Request["Pull / merge request"]
    Request --> Review
```

## Repository

A repository is the unit where Acrity tracks pull requests or merge requests. Each repository can inherit workspace settings or have its own overrides, such as language, branch rules, PM tool, and review behavior.

## Automated review

An automated review is an assessment generated by Acrity from an authorized PR/MR. The Console shows history, status, findings, suggestions, and related events without turning the repository into a browsable copy of the code.

## Review tiers

Acrity exposes two public review modes:

| Tier | When to use                                                                |
| ---- | -------------------------------------------------------------------------- |
| Fast | Faster feedback for common changes and continuous flow.                    |
| Deep | More comprehensive analysis for sensitive, larger, or higher-risk changes. |

Settings can be defined at the workspace level and adjusted by repository when needed.

## Connected app

A connected app uses the provider's official flow, such as a GitHub App or OAuth, to authorize access to repositories and external tools. It is the preferred option when available.

## Credential

A credential is a secret registered by a Workspace admin, such as a VCS token or PM tool token. Secrets are stored encrypted and are not shown again in plaintext after registration.

## Connector

A connector is a component installed in the customer's environment to integrate a private or self-hosted VCS. It lets Acrity coordinate reviews without requiring the private VCS token to be stored in the Acrity cloud.

## Outbound webhook

An outbound webhook is a notification sent by Acrity to external systems when relevant events happen in the workspace. The destination can validate the origin with an HMAC signature.

## API key

An API key enables programmatic access to public Acrity API resources. Each key should have minimum scopes, an appropriate expiration, and IP restriction when possible.

## Audit Trail

Audit Trail centralizes technical and administrative events visible to a Workspace admin (platform admins also have access), helping diagnose connections, webhooks, repository states, and technical review events. Track reviews in the [Ops dashboard](/en/guides/ops-dashboard); use Audit Trail only for technical event details and diagnostics.