At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| JSON terminology manifest | Load and validate its schema | Reviewable import | Maximum 256 KB |
| Source revision and policy version | Preserve source context | Revision-bound import identity | Values must meet bounded contract rules |
| Up to 1,000 terms | Compare observations with governed policy | Findings and import summary | The import does not change source code |
| Repeated identical manifest | Reuse the existing import | Idempotent result | Changed evidence needs a new manifest identity |
How it works
- Generate the supported manifest in the source environment.
- Open Offline Manifest Sync.
- Choose the local JSON file.
- Review the loaded manifest text.
- Select Import manifest.
- Open the import and review its findings.
Example
A restricted repository cannot grant ongoing access. Its controlled pipeline produces a terminology manifest for one immutable revision. An administrator reviews and imports the file. Compliance Glossary records the revision-bound observations and findings without connecting to that repository after import.
What this does not mean
Offline sync trusts the validated manifest as supplied evidence. It does not inspect the repository, modify source files, or prove that the manifest covers every file. Teams must protect the generation process and revision identity.
Related questions
Next step
Use offline sync when permanent repository access is not approved.
View on Atlassian Marketplace