Information entries in Devolutions Hub Business centralize reference data such as contact details, asset identifiers, or policy notes in shareable, permission-controlled records. Unlike pure credential entries, an information entry focuses on descriptive fields, links, and documentation so teams can look up values like support contacts, door codes, serial numbers, or policy references alongside their passwords.
Because these entries live in the same vaults and inherit the same roles and permissions model, administrators can decide exactly who may view or edit sensitive information. A typical pattern is to store vendor contract information in an information entry and link it from the related privileged accounts, ensuring everyone troubleshooting an issue sees both operational details and business context.
Share your feedback