Connect Hudu to link each client to its Hudu company. Debut files the client’s credentials there and sees when each password is filled in and changed. Debut never keeps a password. Owners and admins connect it on the Practice and Firm plans.
Make an API key in Hudu
In Hudu, open Admin → API Keys → New API Key. Name it Debut, and set Limit scope to Full Access.
Turn on Password access. Without it, Debut cannot read or file anything.
Leave Destructive actions and Export off.
Optional: to accept the key only from Debut, add 20.9.26.3 to the key’s IP allowlist. Every call Debut makes to Hudu comes from that address.
Copy the key. Hudu shows it once.
Connect it in Debut
Open Settings, choose Integrations, and in the Documentation card choose Connect beside Hudu.
Enter the Hudu address you sign in to Hudu at.
Paste the API key.
Choose Connect Hudu.
Debut tries the key first. Nothing is saved until Hudu accepts it and lets it list passwords.
Link a client to its Hudu company
Open the client and choose its Setup tab.
In the Hudu card, pick its Hudu company. A company with the same name as the client is chosen for you.
Choose Save.
If Hudu has no company for the client yet, choose the link Have Debut make followed by the client’s name.
How credentials are filed
Once a client is linked, its credentials are filed in Hudu as they are added. Each becomes an entry with a name, a login and a placeholder where the password goes. An entry with the same name is linked instead of made again. To stop this for one client, choose Stop filing on its Hudu card.
To stop filing for every client, turn off File new credentials in Hudu on the connection’s page.
Entries already in Hudu are offered on the client’s Credentials tab, under In Hudu, not on the ledger. Tick them and add them to the ledger.
How rotation is tracked
A credential linked to its Hudu entry counts as received when the entry’s password is filled in. It counts as rotated when the password changes after that.
The switch A first password in Hudu counts as rotated is on for each client to start.
On, the first password put in place of the placeholder counts as a new one your team set. The credential is rotated then.
Off, the first password counts as the one the old provider handed over. Its next change is the rotation.
A sheet of passwords uploaded on the Credentials tab is always taken as handed over.
What Debut keeps
Debut reads the names, logins and change dates of password entries. No password is stored, logged or shown in Debut. For a password waiting to be rotated, it keeps only a one-way fingerprint, deleted once the rotation is seen.
Connecting Hudu at a new address unlinks every client. Link each one again once the new companies are read.
Related guides
Integrations in Debut
Connect NinjaOne