Documentation
    {{docApp.userSession.userId}}
    {{docApp.userSession.userName}}
    {{docApp.userSession.email}}
    Issuer : {{docApp.userSession.issuerInstance}}
    Expires : {{new Date(docApp.userSession.validUntil).toLocaleDateString()}}

{{docApp.title}}

{{docApp.description}}

INDEX

Documentation Library

Search for information on Hornbill Documentation.

{{docApp.searchError}}

{{docApp.searchResultFilteredItems.length}} results for "{{docApp.currentResultsSearchText}}" in {{docApp.searchFilterBySpecificBookTitle}}

Have questions about this site?

What is this site?

  • This website is Hornbill's new product documentation website and is currently under development.
  • It is intended that all existing and future public-facing documentation we produce will be available to search, browse and share.
  • Hornbill's current documentation is available at Hornbill Wiki but over time this content will be migrated to this documentation site.
  • Please feel free to have a look around at any time.

Why has Hornbill created this site?

  • Hornbill's products have moved on considerably since we introduced it almost 10 years ago. At the time, the MediaWiki tool was sufficient, but we have outgrown it.
  • Our customers are more enterprise focused and more self-sufficient than ever before, so for 2023 and beyond we have established a new documentation platform and team to drive our documentation initiative forwards.
  • We are aiming to deprecate the use of Hornbill Wiki for most Hornbill related documentation.
  • We want to enable our growing partner network with product resources and information, documentation beyond our Wiki approach is required.
  • We could definitely do with some help, and may even pay for some! If you have domain knowledge and would like to help, please check out our Hornbill Docs Contributor Guide and contact the Hornbill docs team at docs@hornbill.com.

What will this site be good for?

  • Community contribution will be facilitated, encouraged, and most welcome.
  • High quality documentation, will be kept up to date as rapidly as our products evolve.
  • Real-time content search and discovery.
  • Articles organized into books, books into libraries, creating a more natural and logical structure to our documentation.
  • Legacy API documentation and various other documentation sources will all be consolidated into a single unified documentation system.
  • Documentation available in browser as well as printable/viewable as PDF on demand.
  • Personalized documentation experience, allowing dark/light mode, article subscriptions, social media sharing and other useful features.
  • Almost all publicly available documentation on docs.hornbill.com will be open-source and available to fork on GitHub, allowing customers to derive their own custom documentation around Hornbill products should they wish to.

What is the timeline for this site?

  • We have taken the decision to publish and make available early, there is very little content at this time.
  • As and when we have completed/usable documentation, it will be published here.
  • We have a host of additional features we wish to add over time, so please watch this space.
  • We expect most of our existing documentation should be reviewed/migrated to docs.hornbill.com over the coming months.
  • The documentation project will be ongoing, will continue to expand, evolve and improve day-by-day.

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

{{book.title}}
More...

Cryptography Controls and Usage

Your data and its security are as important to Hornbill as it is to you and we therefore encrypt all data in transit and at rest using a minimum of 256 bit.

All cryptographic tools used are sourced from legitimate sources and thus compliant with all relevant UK regulations related to cryptography. All encryption techniques utilize a minimum of AES 256-bit encryption and longer where possible.

All Hornbill controlled keys (SSH, Access, DB Encryption, DISK Encryption, Instance Encryption) are unique and randomly generated as required. Each key is then stored in a central password encrypted file that only permitted members of the cloud team can access (Access to each set of keys depending on roles). All keys are regenerated whenever a team member leaves the team or changes roles which affects access. All keys are valid for a maximum of 2 years before needing to be regenerated at which time the encryption technique used will be re-evaluated to confirm that this is still appropriate.

For external transport, we support and recommend secure protocols when providing integration (for example POP3S\IMAPS)and all web applications are served over HTTPS (All checked weekly via SSL Labs and others to ensure no known vulnerabilities)

A record of all encrypted data is kept and the encryption used is reviewed regularly to ensure that it is still fit for purpose.

All physical media that leaves Hornbill controlled sites is encrypted and records are kept detailing sender, Recipient, proof of receipt, encryption used, and dates.

Internal Policy

All Disks, Laptops, removable hard drives, and USB memory devices are encrypted in line with the above conditions. All traffic that leaves the cloud network must be encrypted. All customer data stored at rest (DB\File Backups etc) must be contained within the encrypted volume and any data pushed to off-site backups must be encrypted in transit and at rest on target.

  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document