2. How information is structured in this manual
  • This chapter informs you about how information is presented to you in this document.
  • We use a structured, rule-based documentation style to make orientation within the content as easy as possible.
  • Whenever possible, we have sorted the chapters by the type of information they contain and by life cycle and usage.

This should allow you to quickly find the information you need and navigate through this manual in a mostly intuitive way without deeper knowledge of the contents.

Although we have linked information between different types of information and chapters below, using the search functionality of the online help manual is the fastest way to find all occurrences linked to the information you are looking up.

Information sorting in this manual

Information type
Content/targeted information
Typical chapters
General information
  • Information about this documentation and how to use it most efficiently
  • Introductory product information
Preparational content
  • Release notes
  • Introductory content
  • Best practices
  • Installation and upgrade information
Installation, configuration, and operation
  • Installation and upgrade information
  • Initial configuration and operation
Configuration management
  • Generic information about configuration and configuration management
Conceptually sorted content
  • Authentication types with usage and administration information
  • Self-services
  • Securing techniques
  • Access control
  • IAM flow concept explained
Technical modules
  • Technical, REST API, and configuration details organized along with the IAM modules (Loginapp, Adminapp, …).
REST API interface
  • Quick access to the REST API specifications.
Customization and extensions
  • Customization and localization of the user interface
  • Third-party licenses

Found errors?

Please report errors in this documentation (release date: 2022/05/13) by mail to documentation-feedback@airlock.com.

  • When reporting errors, please let us know:
  • The full title of the referred document.
  • What kind of problem or error you found.

If ever possible, send us a copy or a screenshot of the affected document page.

Thank you very much for your support! Your feedback is highly appreciated.