Skip to main content
This page is for authors, supervisors, and anyone curious how a procedure gets from an idea to a worker’s device. In a few minutes you’ll understand the Portal → publish → device pipeline and where each kind of authoring happens.

​
The pipeline at a glance

1

Author

Subject-matter experts create procedures — in the Procedures Portal (web) or directly on a device in Author Mode.
2

Enrich

They add tasks, steps, 3D models, media, anchor gems, and choice logic so the procedure guides the operator precisely.
3

Publish

Once ready, the procedure is published and becomes available to operators across the tenant.
4

Run

Operators pick up the latest published version automatically the next time they run the procedure on their device.
5

Iterate

Authors refine procedures based on field feedback. Updates reach every device the next time the procedure is opened.
The Procedures Portal is the single source of truth: content is authored once and updated centrally, and every device pulls the current published version.

​
Where authoring happens

Authoring is split across two surfaces, and most teams use both: Start in the Procedures Portal for structure, then finish placement on the device — HoloLens or iPad.

​
Organizations scope everything

In the Procedures Portal, all procedures are organized by Organization. The organization selected in the top navigation determines:
  • Which procedures are displayed
  • Where new procedures are created
  • Which users have access to those procedures
Procedures are not shared across organizations unless explicitly configured — so a procedure published for one business unit, customer, or environment reaches only the operators with access to that organization.

​
How content reaches operators

  • Publishing makes a procedure available to operators across the tenant (within its organization).
  • The device app downloads the latest published procedure when the operator opens it, anchors it to the physical space, and renders steps, 3D models, and media as the worker moves through the task.
  • There is no per-device deployment step for content: update in the Portal, and every device gets the new version on next open.
Each procedure card in the Portal shows its current version, last updated date and author, and availability status — so authors can see at a glance what operators are getting.

​
Getting devices connected

Before a device can pull content, it needs to be signed in. Alongside standard sign-in, the Portal supports device pairing: the device shows a 6-digit PIN, you enter it in the Portal, and the device is signed in with your web session — no typing credentials on a headset. For the wider platform picture — the device apps, the Portal, the Remote Expert backend, and identity — see the Architecture Overview.
Next: put the concepts to work — find your role’s first-day checklist in Choose Your Path.