You manage contacts through the printer's embedded web server (EWS), not the control panel: open a browser, type the printer's IP address, sign in as administrator, then go to Scan/Digital Send → Address Book to add or delete entries. The control panel can search and select saved contacts but cannot create them on this model. Everything below assumes you're on the same network as the printer and have the administrator password.
What the E78630 Address Book Actually Controls
The Flow E78630 stores email destinations in a dedicated Address Book that feeds every scan-to-email and fax-to-email workflow on the device. Each entry carries a display name, one or more email addresses, and optional attributes like an SMTP server override. That last field matters more than most people expect: if your network sends mail through a relay that rejects certain domains, a per-contact SMTP setting is the workaround.
Capacity is generous but finite. HP's documentation for the LaserJet Enterprise and Flow line lists a maximum of 2,000 contacts in the address book, with up to 4 email addresses per contact. Confirm the current figure on HP's support page for your firmware revision, since limits have shifted across firmware families. For a 40-person office, capacity will never be your constraint.
Two categories of entries exist. Local contacts live only on this printer. Network contacts pull from an LDAP directory server you configure under Scan/Digital Send → Address Book → Network Contacts. Deleting a network contact in the printer does nothing to LDAP; the entry returns on the next sync. Keep that split in mind before you spend twenty minutes deleting rows that keep reappearing.
The address book also drives autocomplete on the control panel. When a user starts typing a name at the scanner, suggestions come from these stored entries. A stale contact doesn't just clutter a list — it invites a scan to a departed employee's inbox.
Accessing the Embedded Web Server Before Touching Contacts
Find the printer's IP address first. On the control panel, tap the network icon or navigate to Settings → Network → Wired Network (or Wireless) and read the IPv4 address. Static addressing is strongly preferred for printers precisely because admin workflows like this one depend on a stable address; DHCP reservations work equally well.
Open a browser on a computer on the same subnet and enter https:// followed by the address. Modern firmware forces HTTPS and will warn about the self-signed certificate — proceed past it. The EWS sign-in screen appears with fields for administrator credentials. The factory default for many HP Enterprise devices sets the administrator PIN to the device serial number, but your reseller or IT provider has likely changed it; HP's support documentation confirms the serial-number default for this family.
If the admin password is lost, recovery requires a cold reset, which wipes stored network and address book settings. Physical access to the printer is required for that procedure, and it is documented in the service manual rather than the user guide. Plan the reset during downtime — it takes roughly 15 to 20 minutes including network reconfiguration.
Three failure modes appear at this stage. A browser timeout usually means the printer sits on a different VLAN than your workstation. A certificate error you can bypass but repeated login rejection suggests the account is locked after failed attempts. And a page that loads without an Address Book option means you signed in with user-level credentials rather than administrator.
Adding a Single Email Contact Step by Step
Here is the exact sequence on current Flow firmware. The labels below match the EWS menu text; wording can drift slightly between firmware releases, so treat the final label as confirmable on your own device's screen.
1: Sign in to the EWS as administrator. 2: Select Scan/Digital Send in the top navigation. 3: Open Address Book in the left panel. 4: Click Add Contact (sometimes labeled Add or a plus icon, depending on revision). 5: Choose Email as the contact type. 6: Enter a Display Name — this is what control-panel users see and search. Use "Accounts Payable – Maria Chen" rather than just "Maria" if multiple people share first names. 7: Enter the Email Address. The field validates format on save; a typo like a missing @ blocks the save with an inline error. 8: If your environment needs it, expand SMTP Settings and override the server for this contact only. 9: Click Save, then OK on the confirmation.
The new contact is searchable from the control panel within seconds — no reboot required. If it doesn't appear, force a panel refresh by backing out to the home screen and re-entering the scan workflow.
Failure handling: a save that silently reverts usually means a duplicate address exists under a different display name. The E78630 permits duplicate email addresses but flags them in some firmware builds. Search the full address book for the address string before re-adding.
Bulk Importing Contacts With the CSV Template
Typing dozens of addresses one at a time is the wrong move for anything past about five entries. The EWS provides an Import function under the Address Book panel that accepts a CSV file, and HP publishes the column structure on its support site for the Flow and Enterprise families. The core columns are display name and email address; additional columns cover fax number, SMTP override, and category tags.
Export first. Click Export in the same panel to download your current address book as CSV. Open it in a spreadsheet application and you'll see the exact headers your firmware expects — this beats guessing at the template, because header names have changed across firmware generations. Append new rows beneath the exported data, keep the header row intact, and save as UTF-8 CSV.
Reimport replaces or merges depending on the option you pick at upload. Choose merge behavior unless you intend a full overwrite; a replace-import on a book with 300 contacts and a file with 12 wipes 288 of them. There is no undo beyond a backup export taken beforehand, so take one every time.
Watch for two import traps. Spreadsheet software often strips leading zeros from phone-style fields and can mangle accented characters in display names if the file isn't saved as UTF-8. Also, rows with an empty display name may import with the email address as the name — check the result list after import rather than assuming success from the green confirmation banner.
Removing One Contact and Confirming It's Actually Gone
Deletion is a two-click operation with one verification step that most people skip.
1: Sign in to the EWS and open Scan/Digital Send → Address Book. 2: Search or scroll to the contact. 3: Tick the checkbox beside the entry, then click Delete. 4: Confirm on the dialog.
Now verify. Return to the control panel, start a scan-to-email, and type the first few letters of the removed contact's name. If the name still autocompletes, you deleted a local entry while an LDAP-synced twin remains — check Network Contacts in the EWS and remove it at the directory server instead. That is the single most common "deletion didn't work" report on this device family.
If deletion is greyed out entirely, your signed-in account lacks address-book edit rights even though it can view settings. Account roles are managed under Security → Access Control; an administrator can grant address-book modification to a secondary account without handing over full device control.
Deleted contacts do not go to a recycle bin. The only recovery path is a prior CSV export or a device backup file if your fleet management tool captures one. For a contact removed in error, retype it — it takes less time than hunting for a backup that may not exist.
What Changes When Contacts Live in an LDAP Directory
In organizations running Active Directory or another LDAP server, the printer's local book should hold almost nothing. Configure the directory connection once under Scan/Digital Send → Address Book → Network Contacts → LDAP Setup, entering server address, port (389 for plain, 636 for LDAPS), bind credentials, and search base. After that, the panel queries the directory live.
The practical consequence: when an employee leaves, IT disables the account in the directory and the printer stops offering the address everywhere at once, with no printer-side cleanup. That is the operational argument for LDAP over local entries in any environment above roughly 25 users. The trade-off is latency — directory searches on a slow link can take a second or two per keystroke on the panel.
Hybrid setups are common and confusing. A contact can exist both locally and in LDAP, producing duplicate suggestions at the panel. HP firmware generally prefers the local entry for exact-name matches, which means an outdated local copy can shadow the current directory record. Audit local entries quarterly and delete any that duplicate directory contacts.
If LDAP search returns nothing after configuration, test the bind credentials from a directory tool on a workstation before blaming the printer. Authentication failures surface in the EWS logs under Troubleshooting → Logs, and the error string there names the failing stage — bind, search base, or filter — which saves a long guessing session.
Fixing the Failures That Block Contact Edits
| Symptom | Likely cause | Fix |
|---|---|---|
| Address Book greyed out after sign-in | Account lacks edit role | Grant address-book rights under Security → Access Control |
| Deleted contact reappears | LDAP-synced entry | Remove at the directory server, not the printer |
| CSV import fails with no detail | Header row mismatch or non-UTF-8 encoding | Export a fresh template from the same firmware, match headers exactly |
| Save button does nothing | Invalid email format or duplicate flagged | Correct the address syntax; search for the duplicate |
| Panel shows old contact list | Cached panel session | Exit to home screen and re-enter scan workflow |
| Changes lost after power cycle | Settings not committed before restart | Re-apply and save; wait for the confirmation dialog each time |
The greyed-out Address Book is the failure worth dwelling on, because it looks like a permissions bug and is actually correct behavior. HP ships this family with role-based access control enabled, and the built-in administrator role is the only one with address-book modification by default. A delegated "device manager" account can change network settings and still see an inert Address Book.
The LDAP reappearance problem has a nastier edge case. If the directory server is unreachable when you delete a local override, the printer may re-cache the directory entry on the next successful sync and restore the suggestion. Delete at the source during a period when you can confirm the sync completed.
Panel caching resolves on its own within a minute or two in most cases. If it doesn't, a power cycle is safe — address book changes are written to persistent storage on save, so a restart won't lose committed edits.
Keeping the Address Book Clean Without Extra Tools
A quarterly fifteen-minute routine prevents nearly all address-book incidents. Export the CSV on the first business day of each quarter, open it beside your current staff or distribution list, and diff the two. Anything in the export but not on the list is a deletion candidate; anything on both with a changed address is an edit. The diff takes minutes in any spreadsheet application.
Second habit: never name a contact after a person alone. "AP Invoices" survives staff turnover; "Dave" becomes a mystery six months later. Shared-function names also survive reorganizations, which is when stale contacts cause the most misdirected scans.
Third: keep the exported CSV somewhere the next administrator can find it, labeled with the date. It is the only realistic rollback. A device backup through HP's fleet tools covers this too, but many small offices run these printers standalone with no management console at all.
Fourth: when someone leaves, remove the local entry the same day you disable their network account. The two tasks belong on one checklist. A departed employee's inbox still receiving scanned financial documents is a data-handling problem, not just clutter.
Cost and Time of the Two Approaches Compared
Manual entry runs about 45 seconds per contact once you're signed in and know the field layout — realistic for five contacts, painful for fifty. Bulk CSV import takes roughly 3 minutes of file preparation plus under a minute to upload, regardless of whether you're adding 10 contacts or 200. That comparison alone decides the method for most offices.
| Method | Setup time | Per-contact time | 50 contacts total | Rollback available |
|---|---|---|---|---|
| Manual EWS entry | Under 1 min | ~45 seconds | ~38 minutes | None |
| CSV import | ~3 min | Negligible | ~4 minutes | Prior export file |
| LDAP directory | One-time config, typically 10–15 min with credentials in hand | None after setup | Not applicable | Directory-side only |
The arithmetic favors import by more than half an hour at fifty contacts, and the gap widens with volume. Manual entry only wins when you're changing one or two entries and the export-edit-import cycle would take longer than typing them.
There's a hidden cost in the LDAP route: it needs directory credentials and someone who understands search bases. In a small office with no directory server, that setup time has no payoff. In a 200-person company, the manual approach costs more in a single quarter than the entire LDAP configuration.
One more time figure worth budgeting: a cold reset to recover a lost admin password adds 15 to 20 minutes of downtime plus reconfiguration of network settings and re-import of your CSV. Keeping the admin credential in a password manager is the cheapest insurance in this whole workflow.
FAQ
Can I add an email address from the printer's touchscreen instead of a browser?
No — this model's control panel supports searching and selecting saved contacts but not creating them. The add and delete functions live in the embedded web server, which is why every procedure here starts with the printer's IP address and an administrator sign-in. Some older LaserJet families allowed panel-side entry; the Flow E78630 does not.
How many contacts can the address book hold?
HP's documentation for this printer family lists a maximum of 2,000 contacts with up to 4 email addresses each, though you should confirm the figure against your firmware revision on HP's support page. Practically, offices under a few hundred people never approach the limit. Directory-synced entries don't count against local storage in the same way.
Why does a contact I deleted keep showing up at the scanner?
A directory-synced entry is almost certainly the cause. Deleting a local row leaves the LDAP record intact, and the panel pulls it back on the next search. Open Network Contacts in the EWS, confirm the entry originates from your directory server, and remove it there. If no directory is configured, check whether a second administrator re-added it.
Does deleting a contact remove it from scan job history or logs?
No. Job logs record destinations actually used, and those records persist under the device's job history independent of the address book. If you're cleaning up after a departed employee, review the job log separately for scans sent to their address and address any documents that already went out.
What's the default administrator password on a new E78630?
Many HP Enterprise and Flow devices ship with the administrator PIN set to the serial number, and HP's setup documentation covers this, but resellers and IT providers routinely change it during installation. Check with whoever deployed the printer before attempting recovery. A lost credential means a cold reset with physical access.
Can I import contacts exported from a different printer model?
Often yes, but header rows differ between firmware families and models, so import the file only after comparing its headers to a fresh export from the E78630 itself. Mismatched headers fail silently or produce garbled display names. Export, compare, adjust, then import — in that order.
Do address book changes need a printer restart?
No. Committed changes appear at the control panel within seconds, and a restart doesn't help if a contact still isn't visible — that points to panel caching or an LDAP override. Restarting is safe for committed edits but solves very little in this workflow.
What happens to the address book after a factory reset?
A cold reset wipes local contacts along with network settings, which is why a dated CSV export belongs in your records before any recovery attempt. Directory-synced entries return automatically once LDAP is reconfigured, since they live on the server. Local-only contacts are gone unless you have that export.