DocumentationMac

Start here

Manifest keeps a register of the hardware an organisation owns, and keeps it in a state an auditor will accept. These pages cover every area of the Mac app, in the order the app itself puts them.

What the product is doing

An asset register is not a spreadsheet with better fonts. The thing being tested, when anyone tests it, is not whether a list exists. It is whether each entry can be tied to a machine somebody has actually seen, whether custody is recorded, and whether the ones that left can account for how they left. Manifest is built around those three questions, which is why verification, custody and disposal have more machinery behind them than adding a row does.

Everything runs on your Mac. The register is a file you hold, the intelligence is on-device, and the iPhone app talks to the Mac directly rather than through us. If you have chosen the cloud track, your organisation gets its own hosted register and the same apps become clients of it.

How these pages are arranged

In the same order as the app's own sidebar, so you can run your eye down both at once.

Getting started

  • First runThe provisioning console: naming the organisation, answering the regulated-data questions, and what those answers decide.
  • Where the register livesThis Mac and my devices, or Starkive Cloud. The one decision that governs every sync afterwards.
  • Bringing in what you haveImporting a spreadsheet, what the resolver matches on, and how repeated vendors become one record.

Overview

  • HomeThe Daily Manifest: what Manifest noticed, the fleet briefing, and the at-a-glance figures.

Portfolio

  • AssetsThe register itself: finding a machine, reading its record, changing it, and doing the same to two hundred at once.
  • ConsumablesStock that is counted rather than tracked: cables, docks, toner, and what happens when it runs low.
  • UsersThe directory: who works here, what they hold, and which fields a sync is allowed to overwrite.

Procurement

  • RequestsSomeone needs a machine: the request, the approval, and the trail it leaves.
  • VendorsWho you buy and lease from, and how a vendor gets attached to an asset.
  • ContractsLeases, support agreements and warranties as first-class records, with the assets that sit under them.

Insights

  • StudioAsk for a dashboard or a report in a sentence, and keep the ones that earn their place.
  • SuggestionsWhat the register has noticed about itself, and why acting on one is a recorded act.
  • LifecycleWhere each machine is in its life, from received to sanitised, and the refresh forecast.
  • FinanceRun-rate, book value, lease rent and amortised capital, and why run-rate is not cash flow.
  • ComplianceThe frameworks your answers derived, the controls your inventory maps to, and the evidence pack.

Administration

  • DiscoverFinding hardware already on the network, and why nothing it finds is written without you.
  • IntegrationsIntune, Entra, Jamf Pro, Okta, CSI Leasing and the vendor warranty APIs.
  • AdminCustom fields, roles, sites, stockrooms, automation rules and the settings that alter other screens.

Reference

Holding the phone instead? The iPhone pages are a separate set, arranged around that app’s four tabs rather than these sixteen areas.

If you have just installed it

Bring assets in before anything else. An empty register teaches you nothing about whether the product fits, and every screen after this one is a view of data you have not put in yet. Import a spreadsheet or connect one source, leave the rest, and come back to Assets when there is something in it.