Feature Request: Reference/Link Credentials in Asset Layout Fields (with Usage Description)

Hi Hudu team,

We’d like to request an improvement to how credentials can be associated with assets.

Problem / current limitation

Today, credentials can be stored in Hudu, but it’s difficult to structure them directly on an asset in a way that explains what each credential is used for on that specific device/service. In practice, we often have multiple logins tied to the same asset (local admin, iLO/iDRAC, application login, VPN profile, service account, etc.), and it becomes unclear which password belongs to which purpose.

Requested feature

Add a field type in Asset Layouts that lets us select/reference an existing Credential (similar to a relationship picker), and optionally provide a short usage/description per referenced credential.

Example:

•   Field label: “Credentials”•   Inside the asset, we can add one or more credential references:•   Credential: “Server01 - Local Admin”

Usage: “Local admin login for maintenance”

•   Credential: “Server01 - iLO”

Usage: “Out-of-band management”

•   Credential: “App Service Account”

Usage: “Used by the scheduled task / service”

Expected behavior / UX

•   In an asset layout, admins can add a “Credential Reference” field (single-select or multi-select).•   When editing an asset, users can pick one or more existing credentials from Hudu.•   Each picked credential can have an optional text description (purpose/where it’s used).•   The asset view should display these references as clickable links to the credential item (with permission checks applied as normal).

Why this matters

•   Reduces guesswork and mistakes when multiple credentials exist for a single asset•   Makes onboarding and handovers easier (clear purpose per credential)•   Keeps credentials centralized while still making them actionable on the asset

Acceptance criteria (suggested)

•   New “Credential Reference” field type available in Asset Layouts•   Supports single or multiple credential references•   Optional per-reference description field•   Clickable link from asset to credential (respecting existing credential permissions)

If helpful, we can share real examples of how we structure assets and credentials today.