Forge integrations
Runs inside Atlassian and synchronises supported external source systems into Assets.
How it works
Two collection paths. One Assets outcome.
Each LT Census product owns a different source and runtime. Their records meet at a shared set of controls for Jira Service Management Assets.
Product flows
External source systemsLT Census Connect
EnvironmentLT Census Discovery
Jira Service Management Assets
Step 01
Collection belongs to the product.
Connect uses built Forge integrations for Apple Business Manager, Iru / Kandji and Zluri. The separate resource engine collects supported environment inventory from outside Atlassian, with Google Cloud as the launch scope.
LT Census Discovery
Runs on LTS operated infrastructure outside Atlassian and synchronises supported Google Cloud resources into Assets.
Shared controls
A common model starts after collection.
These controls express the family relationship without erasing the products’ different capabilities or trust boundaries.
Translate source-specific records into a consistent model for Jira Service Management Assets.
Measure the current collection against the last recorded run and classify the difference.
Create or update the required objects in Jira Service Management Assets.
Record the outcome so teams can see what the selected product found and what changed in Assets.
Shared language, separate implementations.
Scheduling, comparison and reporting make the family familiar. They do not make the products one application.
Connector configurationCollection scopeSchedulingNormalisationChange detectionExecution reporting
LT Census
Start with the source and trust boundary.
Choose Connect for known source systems or Discovery for environments whose resources need to be found.