Source
Versioning, permissions & audit trail — found from sitemap — FileHold
Checked for FileHold on 11 Nov 2026
- Page
- https://filehold.com/numbering-versioning-2/
- Checked
- 11 Nov 2026, 16:05 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:e647891bf16066999494177ef32d3447484967b1382697316d1d54eff0f47060
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Document ID automatic Report an error
“The document management software automatically assigns a unique number to every single document that is added to FileHold. This number called the FileHold ID Number, it can not be edited by users and is never duplicated in the system. This document numbering can not be turned off.”
-
Version decimal increment Report an error
“In the case of a different version of the same document the number is incremented by a decimal number to indicate a new version. (i.e. A new document added to FileHold may get number 403. If that document is checked out and changed and than checked back in it would get the unique number 403.1.”
-
Version tracking Report an error
“Version control allows managers to track the history of a document as it evolves, it records the date when the version was changed and by whom.”
-
Version checkout clients Report an error
“Every time a document is checked out from FileHold using a standard web browser, Microsoft Office applications or using the FileHold Desktop application it becomes a candidate for automatic version control.”
-
Version start Report an error
“The actual version numbering system starts at version #1 and is incremented by 1 number each time the document is changed and is checked back in.”
-
Overwrite prevention Report an error
“Version control prevents documents from being overwritten or deleted as documents are updated by more than one party. All versions of the file are maintained by the system in the event that a rollback is required.”
-
Metadata numbering Report an error
“In addition to the formal numbering / Versioning solutions the software provides there is near infinite numbering / Versioning possibilities using metadata fields. Metadata fields are flexible, controllable and searchable”
-
Reporting services Report an error
“Using the software’s reporting services (based on SQL Reporting Services) all metadata fields are reportable so there is unlimited flexibility to generate reports based on any custom numbering systems a customer may wish to develop.”
-
Document control number admin Report an error
“Document control number Fields are created and modified in the Library Administration section of FileHold therefore the creators must have at least Library administration rights.”
-
Document control number immutable Report an error
“Once a document number field is assigned to a schema and documents are created using this schema parameters cannot be modified.”
-
Document control number generation Report an error
“There are two ways to generate document control numbers: They can be auto-generated by the FileHold System. Entered manually by the user In either case, the software will ensure that the control number is unique to the document. When used, document control numbers are mandatory.”
-
Document control number locked Report an error
“Control numbers must be assigned to a document when it’s added to the software and are unable to be modified later.”
-
Document control number auto hidden Report an error
“If the document control field is auto-generated, the value is not displayed when adding the document.”
-
Document control number prefix Report an error
“Each document control field has a prefix which must be different from all other prefixes. This ensures that each document control number is unique across the entire library.”
-
Manual version control Report an error
“In addition to the FileHold automatic version control the software has a feature to allow users to manually generate and control more sophisticated version schemes that reflect the real world of major and minor releases in document Versioning (i.e. A more complex version Control number would be 6.02.001).”
-
Manual version admin enabled Report an error
“The version control capability is turned on by the library administrator when creating schemas for documents that might require manual Versioning.”
-
Manual version rules Report an error
“Versions control numbers are not mandatory. They can be assigned when adding a document or checking in a document and can be modified, separately for each document version, at any time. By default the version number is carried over from the last version when document is checked in. Version numbers don’t have to be unique.”
-
Cloud available Report an error
“Check our FAQ, or ask an expert about FileHold Cloud”
Scores citing this record
- The Data Protection Officer Versioning, permissions & audit trail
- The Data Protection Officer Audit-proof archiving & retention
- The IT Integrator Versioning, permissions & audit trail
- The IT Integrator Audit-proof archiving & retention
- The IT Integrator Pricing transparency
- The Records Manager Capture, OCR & indexing
- The Records Manager Versioning, permissions & audit trail
- The Records Manager Audit-proof archiving & retention
- The Records Manager European sovereignty
- The Skeptic Versioning, permissions & audit trail
- The Skeptic Audit-proof archiving & retention
- The Mittelstand Owner Versioning, permissions & audit trail
- The GoBD Auditor Versioning, permissions & audit trail