Needs attention
Everything currently waiting on a person, across every tenant you can see.
Recent sync failures
Jobs that failed in the last 24 hours. A repeating failure usually means configuration, not a blip.
| When | Tenant | Dataset | Error |
|---|
| Tenant | Dataset | Last success | Interval |
|---|
Client onboardings in progress
Incomplete setup checklists across your tenants. Stalled = no checklist activity for a week.
| Client | Progress | Last activity |
|---|
Departed users holding assets
Users who left the source system but still have equipment checked out, so sync cannot remove them. Check the assets in to release the user.
| Tenant | User | Assets | Action |
|---|
Onboarding
The client setup checklist, per tenant: every SOW phase from kickoff to handoff. Items SnipeGard can prove check themselves; the rest are checked off by a person.
Setup wizard
Works the instance setup step by step - and every step doubles as a standalone tool you can revisit any time. Completed steps are detected from the checklist's own verification.
Connect SnipeGard to the instance. Open the instance's API page, create a personal access token as the admin, and paste it here.
One-click seeding of the documented baselines (existing names are skipped, never overwritten), plus the settings import that lets sync drive status transitions.
One location per physical site; nest only as deep as reporting needs.
Create the client's staff accounts in Snipe-IT, one group each (see ACCESS_AND_ROLES). Passwords are generated and never shown - users set their own via the instance's password reset.
Wire the data sources and field mappings - these live on their own tabs and the checklist verifies them automatically (sources enabled, connections tested, mappings applied, first sync).
The checklist below is the source of truth - anything still pending is either a manual confirmation (check it off with a note) or real work remaining. Print the progress report for the client or the engagement record.
Tenants
Register each Snipe-IT tenant, monitor version health, and keep credentials isolated.
Integrations
Configure data sources (Liongard-backed and direct providers).
Metric wiring and template management.
Metric wiring
Select a tenant and dataset-
1
RequiredLiongard API keyPaste the API key to unlock the rest.
-
2
LockedLoad environmentsFetch the Liongard environments.
-
3
LockedSelect environmentPick the environment for this dataset.
-
4
LockedLoad systemsFetch the systems inside the environment.
-
5
LockedSelect systemChoose the system that owns the metric.
-
6
LockedMetric nameConfirm or edit the metric name.
-
7
LockedEnsure metric UUIDClick ensure to fetch the UUID.
-
8
LockedSave configurationSave when all details are ready.
User sync filters
Applies to any user dataset that includes email addresses (including Liongard-fed records).
Define Liongard metric payloads once, then sync them into tenant accounts.
Template editor
Set the Liongard metric payload fields you want to enforce.
| Query | Inspector version ID |
|---|
https://graph.microsoft.com/.default as Scope, then click Test connection.
offline_access to refresh tokens automatically.https://snipegard.snipe.support/oauth/ninjaone/callbackDatasets
Datasets are usually auto-managed from integration setup. Use Advanced editor only for manual break-glass changes.
Dataset editor
Metadata changes are safe; structural changes are blocked when in use.
microsoft_365).platform.sync_type.dataset_key.Plugins
Enable plugins globally or per tenant, and configure their credentials.
Fieldset mapping
Map source fields to Snipe-IT custom fields using global templates and tenant-specific mappings.
- Select tenant + dataset.
- Add mappings (field suggestions optional).
- Discover scan (optional refresh).
The Liongard metric + records you are syncing.
The Snipe-IT field group that receives mapped values.
Discover fields
Sample the Liongard metric and capture source field keys.
Preview record
Pull one record to confirm field paths before mapping.
Push to Snipe-IT
Create or update fieldsets in the selected tenant.
| Source field | Default field | Enabled |
|---|
Manual sync
Choose a tenant and dataset, then queue a sync job.
Last run
Latest job result and status.
Sync simulation
Dry run changes without touching Snipe-IT.
Job log
Select a job to view its log.
Job history
Analytics workspace for filtering, compare, diagnostics, and export.
History command bar
Filter by tenant, source, status, origin, date, and diagnostics flags.
Job details
Overview, changes, logs, and raw payload for the selected job.
Sync simulation
Dry run changes without touching Snipe-IT.
No job selected.
Sync volume
How many assets and users are under management, and how much sync work ran over the selected period.
| Period | Type | Jobs | Records processed | Created | Updated | Errors |
|---|
Trend analytics
Job count, error rate, archive rate, updates, and average duration over time.
Organization
Manage organization policy and memberships at organization scope.
Organization summary
Current organization context in this workspace session.
Identity
From selected organizationAuthentication policy
Effective organization policy
Microsoft 365
Provider status
Google Workspace
Provider status
Authentication policy
These settings apply organization-wide across tenants.
Core policy
Select organizationSSO providers
Configure provider credentials, endpoints, and group access rules.
Microsoft 365
SSO provider
Advanced settings
Google Workspace
SSO provider
Advanced settings
Memberships
Manage organization members and tenant-level access roles.
Organization members
| Name | Role | Providers | Active |
|---|
Snipe-IT settings
Manage global Snipe-IT config from the UI (stored in Postgres).
Catalogs Publishes now
Maintain status labels and categories used during sync.
Status labels
| Name | Color | Type | Nav | Default | Notes |
|---|
Categories
| Name | Type | Default EULA | Acceptance | Check-in |
|---|
Sync behavior
Required to create assets and models during sync.
Defaults
Sync-requiredFieldsets Fieldset push
Fieldset names, defaults, and aliases used when pushing fieldsets.
User fieldset name
Fieldset nameFieldset defaults
| Dataset | Default fieldset | Phone fieldset |
|---|
Fieldset aliases
| From | To |
|---|
Mapping options UI only
Core field lists used in mapping workflows.
Core fields
Mapping optionsAssets
| Key | Label |
|---|
Users
| Key | Label |
|---|