SnipeGard Console
Workspace overview
Organization --
Tenants in scope --
Queue depth --
Failed jobs --
Last run --

Tenants

Register each Snipe-IT tenant, monitor version health, and keep credentials isolated.

Tenant registry
Checked 0/0
Updates 0
Vulnerable 0
Stale / unknown 0
Registered tenants
0
Security alerts No vulnerable tenants

Integrations

Configure data sources (Liongard-backed and direct providers).

Sources
Liongard Liongard Active

Metric wiring and template management.

Datasets are preloaded in the database via schema defaults.

Metric wiring

Select a tenant and dataset
Setup order
  1. 1
    Liongard API key
    Paste the API key to unlock the rest.
    Required
  2. 2
    Load environments
    Fetch the Liongard environments.
    Locked
  3. 3
    Select environment
    Pick the environment for this dataset.
    Locked
  4. 4
    Load systems
    Fetch the systems inside the environment.
    Locked
  5. 5
    Select system
    Choose the system that owns the metric.
    Locked
  6. 6
    Metric name
    Confirm or edit the metric name.
    Locked
  7. 7
    Ensure metric UUID
    Click ensure to fetch the UUID.
    Locked
  8. 8
    Save configuration
    Save when all details are ready.
    Locked
Liongard setup quick guide Add API key, pick environment + system, then set metric name/UUID. Save configuration after step statuses are complete.
Credentials are stored only for this tenant.
Controls whether this dataset can run at all (manual + auto).
Controls scheduler queueing only. Manual sync still works when this is off.
Leave blank to use the global auto-sync interval.
Prevents mass archiving when record counts drop unexpectedly.

User sync filters

Applies to any user dataset that includes email addresses (including Liongard-fed records).

Comma or newline separated. Used for user syncs.
Matches the group list in Microsoft 365 or Google Workspace user payloads.
Metric templates Templates

Define Liongard metric payloads once, then sync them into tenant accounts.

Templates 0

    Template editor

    Set the Liongard metric payload fields you want to enforce.

    Queries
    Query Inspector version ID
    Sync to Liongard Uses the tenant source Liongard token.
    Select the dataset that already stores the Liongard API key.
    Microsoft 365 Microsoft 365 Not connected
    What you need before saving In Microsoft Entra, create an App registration with Microsoft Graph application permissions, then copy Tenant ID, Client ID, and a Client Secret value. Use https://graph.microsoft.com/.default as Scope, then click Test connection.
    Credentials are stored only for this tenant.
    Overrides the global auto-sync interval when set.
    Used only when policy is static. Write-only; leave blank to keep stored value.
    Fetch groups to pick from a searchable list.
    If fewer records return, archiving is skipped.
    Idle.
    Google Workspace Google Workspace Not connected
    What you need before saving In Google Cloud, create a service account and JSON key, then enable domain-wide delegation. In Google Admin, authorize the service account client ID for Admin SDK scopes. Save delegated admin email + service account JSON, then click Test connection.
    Overrides the global auto-sync interval when set.
    Write-only. Paste full JSON key to store or rotate.
    Credentials are stored only for this tenant.
    Used only when policy is static. Write-only; leave blank to keep stored value.
    Idle.
    NinjaOne NinjaOne Not connected
    NinjaOne setup quick guide Configure Base URL + OAuth values, then test/authorize connection. Set organization filters and archive guard before enabling scheduled syncs.
    Your NinjaOne instance base URL.
    OAuth host (usually app.ninjarmm.com).
    Overrides the global auto-sync interval when set.
    Connect NinjaOne to load organizations.
    Use the record preview to confirm the field path.
    Credentials are stored only for this tenant.
    Must include offline_access to refresh tokens automatically.
    If fewer records return, archiving is skipped.
    Use percent-based guard for large tenants.
    Items per request to NinjaOne.
    Upper bound on pagination loops.
    Idle.
    Redirect URI: https://snipegard.snipe.support/oauth/ninjaone/callback

    Datasets

    Datasets are usually auto-managed from integration setup. Use Advanced editor only for manual break-glass changes.

    Dataset catalog
    Datasets 0

      Dataset editor

      Metadata changes are safe; structural changes are blocked when in use.

      Auto mode is on. Enable Advanced editor to create or edit dataset definitions manually.
      Display name shown in dropdowns and sync history. Keep it short and human-readable.
      Provider that owns this dataset. Change only when creating a brand-new dataset definition.
      Controls display order in lists. Lower numbers appear first.
      Stable key used in dataset string. Use lowercase + underscores (example: microsoft_365).
      Logical bucket for sync behavior.
      Unique key within the platform + sync type. Use lowercase + underscores.
      Asset matching key used during sync. For device datasets, this must match your mapping strategy.
      Canonical identifier used by mappings and jobs. Usually auto-computed as platform.sync_type.dataset_key.
      Only enable direct editing for break-glass fixes or legacy key compatibility.
      Optional notes for admins (scope, source API, caveats).
      Disabled datasets stay configured but are excluded from manual and scheduled sync runs.

      Plugins

      Enable plugins globally or per tenant, and configure their credentials.

      Plugin hooks
      Idle.

      Fieldset mapping

      Map source fields to Snipe-IT custom fields using global templates and tenant-specific mappings.

      Tenant mappings
      Scope: select Global or a tenant.
      Global mappings are templates. Select a tenant to manage tenant mappings.
      Liongard metric dataset you want to sync.
      Where mapped fields will land in Snipe-IT.
      Select tenant and dataset.
      Suggested order
      1. Select tenant + dataset.
      2. Add mappings (field suggestions optional).
      3. Discover scan (optional refresh).
      Select tenant + dataset to begin.
      Dataset = Source

      The Liongard metric + records you are syncing.

      Fieldset = Target

      The Snipe-IT field group that receives mapped values.

      Discover fields

      Sample the Liongard metric and capture source field keys.

      Waiting for request.

      Preview record

      Pull one record to confirm field paths before mapping.

      Waiting for request.
      
                    
      Fields 0

      Push to Snipe-IT

      Create or update fieldsets in the selected tenant.

      Waiting for request.
      Field mappings
      0
      Source field Default field Enabled

      Manual sync

      Choose a tenant and dataset, then queue a sync job.

      Queue ready

      Last run

      Latest job result and status.

      --
      Tenant
      --
      Dataset
      --
      Finished
      --
      Result
      --

      Sync simulation

      Dry run changes without touching Snipe-IT.

      Idle
      No preview loaded.
      Recent sync jobs
      0

        Job log

        Select a job to view its log.

        --
        No job selected.

          Job history

          Analytics workspace for filtering, compare, diagnostics, and export.

          Archive

          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.

          Idle
          Timeline zoom Full range

          Job details

          Overview, changes, logs, and raw payload for the selected job.

          Idle
          No job selected.
          Tenant
          --
          Source
          --
          Status
          --
          Origin
          --
          Created
          --
          Duration (ms)
          --

          Organization

          Manage organization policy and memberships at organization scope.

          Org admin No organization loaded
          Current workspace organization
          Open SnipeGard Admin Console Select organization.

          Organization summary

          Current organization context in this workspace session.

          Identity

          From selected organization
          Name --
          Organization ID --
          Slug --
          Tenants in org 0

          Authentication policy

          Effective organization policy
          Auth mode --
          Allow local login --
          Allow SSO login --
          Require TOTP --
          Session TTL --

          Microsoft 365

          Provider status
          Enabled --
          Group mode --
          Allowed groups 0

          Google Workspace

          Provider status
          Enabled --
          Group mode --
          Allowed groups 0

          Snipe-IT settings

          Manage global Snipe-IT config from the UI (stored in Postgres).

          Global config
          Idle.
          Effective source Editing global defaults
          Catalogs: global Sync behavior: global Fieldsets: global Mapping options: global

          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 Next sync

          Required to create assets and models during sync.

          Defaults

          Sync-required
          These labels drive sync status transitions and cannot be removed while referenced.
          Used when creating models in Snipe-IT.

          Fieldsets Fieldset push

          Fieldset names, defaults, and aliases used when pushing fieldsets.

          User fieldset name

          Fieldset name

          Fieldset defaults

          Dataset Default fieldset Phone fieldset

          Fieldset aliases

          From To

          Mapping options UI only

          Core field lists used in mapping workflows.

          Core fields

          Mapping options

          Assets

          Key Label

          Users

          Key Label