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

# Core Concepts

> Learn the SDX terms you need before managing sites, policies, workflows, and monitoring.

Altostrat SDX is easier to use when you separate the things you manage from the systems that carry out the work. A site is the object you see in the portal. The device job plane, management tunnel, metadata store, and workflow engine are the systems that keep that site useful.

## Organization Model

<CardGroup cols={2}>
  <Card title="Organization" icon="building-2">
    The top-level account boundary. Organizations contain workspaces, users, teams, billing settings, and governance configuration.
  </Card>

  <Card title="Workspace" icon="database">
    The tenancy and billing container. Workspaces hold the SDX resources your team operates.
  </Card>

  <Card title="Team" icon="users">
    The collaboration boundary for day-to-day access. Teams collect users and apply roles to the resources they can work with.
  </Card>

  <Card title="Role" icon="key-round">
    A permission set. Portal navigation and actions are scope-gated, so users only see what their role allows.
  </Card>
</CardGroup>

## Network Objects

<CardGroup cols={2}>
  <Card title="Site" icon="map-pin" href="../fleet/managing-sites-devices">
    A site represents a managed MikroTik router and its operational context: status, tunnel information, metadata, tags, notes, backups, metrics, faults, and feature assignments.
  </Card>

  <Card title="Management VPN" icon="shield-check" href="../resources/management-vpn">
    The outbound management path between a site and Altostrat regional infrastructure. It supports remote access, synchronous commands, and management-side operations.
  </Card>

  <Card title="Policy" icon="sliders-horizontal" href="../fleet/control-plane-policies">
    A reusable configuration object that can be attached to one or more sites. Examples include control plane, content filtering, BGP threat, security group, and prefix list policies.
  </Card>

  <Card title="Tag and Metadata" icon="tags" href="../fleet/metadata-and-tags">
    Structured context you attach to sites and other resources. Tags support filtering, reporting, workflow conditions, and operational ownership.
  </Card>
</CardGroup>

## Execution Concepts

<CardGroup cols={2}>
  <Card title="Heartbeat" icon="activity">
    A regular check-in from the router. Heartbeats feed online status, last-seen data, device inventory, and availability reporting.
  </Card>

  <Card title="Device Job" icon="list-checks">
    A queued unit of work for a router. Scripts, backup requests, policy pushes, ARP syncs, VPN updates, and selected feature actions all use the same job pattern.
  </Card>

  <Card title="Synchronous Command" icon="zap">
    A live command sent through the management server when the site is reachable. Use this for current state, not for reading static configuration you can get from backups.
  </Card>

  <Card title="Workflow Run" icon="workflow">
    One execution of a workflow. Runs have triggers, node results, logs, and context passed between actions and conditions.
  </Card>
</CardGroup>

## Operational Concepts

<CardGroup cols={2}>
  <Card title="Fault" icon="triangle-alert" href="../monitoring/fault-logging">
    A normalized operational incident, such as a site outage or WAN state change. Faults feed dashboards, notifications, workflows, and SLA reporting.
  </Card>

  <Card title="Schedule" icon="calendar-clock">
    A reusable time window. Schedules can control when automations, reports, scripts, and notifications should run or deliver.
  </Card>

  <Card title="Notification Group" icon="bell" href="../monitoring/notifications">
    A routing rule for who gets told about operational events, and through which channels or integrations.
  </Card>

  <Card title="Report" icon="file-chart-column" href="../monitoring/reporting">
    A generated operational artifact, such as an SLA report or vulnerability report, built from stored platform data.
  </Card>
</CardGroup>

## Next Step

<Card title="Read the Operating Model" icon="route" href="./operational-model" arrow="true" cta="Continue">
  Learn how heartbeats, jobs, live commands, faults, notifications, and reports behave in real operations.
</Card>