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

# Architecture Overview

> A high-level view of how Altoura Frontline fits together — the devices, apps, and services that make up the platform.

Altoura Frontline is an integrated platform made up of a few clearly separated pieces. This page gives you the mental model of how they fit together and what each one is responsible for, without diving into deployment-level detail. If you're looking for the deployment steps themselves, see the [IT Admin Guide](/frontline/administration/remote-expert-it-admin/overview-and-prerequisites).

***

## The components

<CardGroup cols={2}>
  <Card title="Altoura Frontline HMD app" icon="vr-cardboard">
    Runs on HoloLens 2. Delivers AR-anchored procedures and the Remote Expert on-device experience for the field worker.
  </Card>

  <Card title="Procedures Portal (web)" icon="browser">
    Browser-based workspace where authors and supervisors create, organize, and publish procedures.
  </Card>

  <Card title="Altoura Remote Expert backend" icon="server">
    Altoura-hosted service that orchestrates Remote Expert meetings and powers live annotations and file sharing between the HoloLens and Microsoft Teams.
  </Card>

  <Card title="Microsoft Teams plugin" icon="microsoft">
    The **Altoura Remote Expert** meeting app that the expert interacts with inside Microsoft Teams.
  </Card>

  <Card title="Microsoft Entra ID" icon="shield-halved">
    Your organization's identity provider. Users sign in as themselves, to your own tenant.
  </Card>

  <Card title="Altoura Portal" icon="gauge">
    Web portal used for device pairing, user management, and tenant-level configuration.
  </Card>
</CardGroup>

***

## How the pieces work together

<Steps>
  <Step title="The worker signs in on HoloLens 2">
    The Altoura Frontline app authenticates the user against your organization's identity. Once signed in, the app is ready to run procedures and start Remote Expert sessions.
  </Step>

  <Step title="The worker runs a procedure">
    The HMD app downloads the latest published procedure, anchors it to the physical space, and renders steps, 3D models, and media in augmented reality as the worker moves through the task.
  </Step>

  <Step title="The worker starts a Remote Expert session">
    Either by searching for a specific expert (Contacts flow) or joining a pre-scheduled Teams meeting (Meetings flow). A standard Microsoft Teams meeting is created in the background.
  </Step>

  <Step title="The expert joins from Microsoft Teams">
    The expert joins the call from the Teams client they already use. For the Contacts flow, they receive a one-click invitation in their Teams chat. For scheduled meetings, they join from their calendar.
  </Step>

  <Step title="The expert adds the Altoura Remote Expert app">
    Inside the Teams meeting, the expert adds the **Altoura Remote Expert** app from the meeting toolbar. A side panel opens with annotation and sharing controls.
  </Step>

  <Step title="Annotations and content flow in real time">
    The expert can capture the worker's live view, draw annotations that appear anchored in the worker's physical space, and share PDFs and 3D models directly to the headset.
  </Step>
</Steps>

***

## Content lifecycle

<Steps>
  <Step title="Author">
    Subject-matter experts create procedures — either in the Procedures Portal (web) or directly on HoloLens 2 in Author Mode.
  </Step>

  <Step title="Enrich">
    They add tasks, steps, 3D models, media, anchor gems, and choice logic so the procedure guides the operator precisely.
  </Step>

  <Step title="Publish">
    Once ready, the procedure is published from the Portal and becomes available to operators across the tenant.
  </Step>

  <Step title="Run">
    Operators on HoloLens 2 pick up the latest version automatically the next time they run the procedure.
  </Step>

  <Step title="Iterate">
    Authors refine procedures based on field feedback. Updates reach every device the next time the procedure is opened.
  </Step>
</Steps>

***

## Identity and security, at a glance

Altoura Frontline is designed to run inside **your own Microsoft 365 tenant**, with identity, permissions, and auditability all under your control.

* **Users sign in as themselves.** No shared Altoura accounts. Every action is tied to a real identity in your tenant.
* **Meetings are owned by the field worker.** Remote Expert calls appear in that user's Teams meeting history and calendar, just like any other Teams meeting they host.
* **Least-privilege access.** Altoura is granted only what it needs to create meetings, notify experts, and resolve contacts — nothing more. It cannot read email, files, calendars, or modify users.
* **No credentials stored by Altoura.** Altoura never stores user passwords. Configuration is based on a single Microsoft-standard app registration in your own Entra ID.
* **Single-tenant by design.** Data, identity, and configuration stay within your Microsoft 365 tenant boundary.
* **Predictable secret rotation.** The one shared secret used by the Altoura backend can be rotated by your IT team on a standard cadence (typically annually).

For the full security write-up, permissions list, and rollout checklist, see [Security Considerations & Setup Checklist](/frontline/administration/remote-expert-it-admin/overview-and-prerequisites).

***

## What your IT team takes care of

Most customers only need a small number of one-time actions from their IT team to bring Altoura Frontline live. The details are in the [IT Admin Guide](/frontline/administration/remote-expert-it-admin/overview-and-prerequisites), but at a glance it comes down to:

* Configure a standard **Microsoft Entra ID app registration** in your tenant.
* **Upload the Altoura Remote Expert Teams app** through Teams Admin Center and (optionally) pin it so experts have it ready.
* **Allowlist the Altoura service endpoint** on your corporate network.
* **Provide the app registration values** to Altoura through a secure channel.
* **Run a short end-to-end validation** to confirm everything is working.

Once done, day-to-day use doesn't require IT involvement.

<Tip>
  Now that you have the mental model, pick the path that matches your role in [Choose Your Path](/frontline/overview/choose-your-path) — or go deeper on [Procedures, Tasks & Steps](/frontline/overview/concepts/procedures-tasks-steps), [How Content Flows](/frontline/overview/concepts/how-content-flows), or [How Remote Expert Works](/frontline/remote-expert/how-it-works).
</Tip>