Files
Centralize reusable non-image content in the Nodinite File Library. A runbook, schema, or partner document that appears in ten places should live in one place—so when it changes, ten places don't need manual updates. Upload a file once, reference it everywhere, and update it once to keep all references current.
- ✅ Upload once and reuse the same file in Articles and Shared File Custom Metadata
- ✅ Update a shared runbook, schema, or certificate once—every reference reflects the latest version automatically
- ✅ Search shared files by name, title, description, and tags
- ✅ Use token-based insertion with a stable name slug that works across Test and Production
- ✅ Govern allowed file types and default link behavior with SharedFilePolicy
- ✅ Keep shared assets separate from private Attachment uploads to avoid duplication
Get started with What is the File Library to understand the feature and use Add or manage Article when you want to insert file links into documentation.
Understanding the File Library
The File Library is the Files view on top of the shared asset backend in Nodinite. It stores non-image files such as PDF guides, Word documents, Excel spreadsheets, JSON examples, XML schemas, and ZIP packages as reusable Shared Asset entries. Images have their own Image Library.
Custom Metadata"] SharedFilePolicy["fa:fa-key SharedFilePolicy"] RepositoryModel["fa:fa-sitemap Repository Model"] FileLibrary -- Linked from --> Articles FileLibrary -- Referenced by --> SharedFile SharedFilePolicy -- Governs --> FileLibrary Articles -- Part of --> RepositoryModel SharedFile -- Enriches --> RepositoryModel
This diagram shows how the File Library provides reusable shared assets for Articles and Shared File custom metadata, while SharedFilePolicy governs upload and delivery behavior.
Key Components Explained
| Component | Role | Details |
|---|---|---|
| File Library | Stores each shared file once, with name slug, title, description, and tags | Key Capabilities |
{ndf} token |
Portable, name-based reference to a shared file in Markdown | Token-Based File References |
| Shared File | A Custom Metadata type that references the File Library instead of copying the file | Shared File vs Attachment |
| SharedFilePolicy | System Parameter for allowed MIME types and link behavior | Allowed File Types and Link Behavior |
Unlike a private Attachment, which stores a separate binary copy on each metadata value, a Shared File points to a single reusable file in the File Library. See Shared File vs Attachment for when to use which.

Example of the Insert File picker: search the File Library, filter by tag, or upload a new shared file.
Use Cases
Runbooks and Recovery Guides
Keep one approved PDF or Word runbook in the File Library and reference it from multiple Articles and repository entities. When the procedure changes, update the shared file once instead of hunting for duplicated attachments.
Schemas and Sample Data
Store JSON examples, XML schemas, CSV test data, and other implementation assets beside the documentation that explains them. Token-based insertion keeps those links portable across environments.
Certificates and Partner Documents
Use Shared File metadata to point to certificate instructions, partner onboarding checklists, and signed interface agreements without mixing shared references with private Attachment storage.
Manage files
New 7.12
Open Repository → Files to see every shared file as a card with its file-type icon, title, name slug, Tags, size, and type. Tick Include archived to also show archived files, marked Archived.

The archived file has a red frame and an Archived badge.
Click Action on a card for everything you can do with one file: View, Edit, Copy Reference, Show in Mapify, Show in Mermaid, Archive (or Restore for an archived file), and Permanently Delete.

A live file: Archive retires it, Permanently Delete removes it for good.

An archived file: Restore brings it back.
To act on many files, tick them and open With Selected: Manage Tags opens the Manage Tags dialog, Archive counts the live files, Restore the archived ones, and Permanently Delete all of them.

One live and one archived file are ticked.
Every action asks you to confirm first and needs Modify on Articles in your Role (Permissions). Show in Mapify and Show in Mermaid draw the file with its Tags and the Articles whose text references it, the same way as for images.
What You Need Before Starting
- Access to the Nodinite Web Client
- Create on Articles to upload shared files, and Modify on Articles to edit, archive, restore, or permanently delete them (Permissions)
- The file types you need allowed in SharedFilePolicy
How do I work with Files?
Navigate to Repository → Files in the Nodinite Web Client to access the File Library, upload shared files, add tags, and copy references.
When you want to use a shared file:
- Insert it into Articles as a reusable link via Insert Files from the File Library in Add or manage Article
- Select it from a Shared File custom metadata field on a repository entity, such as an Integration or a System (Add or manage Custom Metadata)
- Reuse the same shared asset in multiple places without duplicating the binary file
Next Steps
Related Topics
- SharedFilePolicy
- Articles
- Custom Metadata
- Image Library
- Macros Reference — the
{ndf}content token - Repository Model