Tenants
Register each Snipe-IT tenant and keep their 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.
Auto sync schedule
Global interval for enabled tenant datasets.
Enabled tenant integrations
0Last 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.
Trend analytics
Job count, error rate, archive rate, updates, and average duration over time.
Compare selected jobs
Select exactly two jobs to compare changes and diagnostics.
Action deltas
Field deltas
Plugin deltas
Job details
Overview, changes, logs, and raw payload for the selected job.
Sync simulation
Dry run changes without touching Snipe-IT.
No job selected.
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 |
|---|