Prepare your account and extension
Create or open your Hice account and use the extension package intended for your browser. Sign in through the extension, open a LinkedIn profile and try one save. Verify that the record appears in the correct workspace and that your user has permission to create that record type.
Package availability does not mean every browser uses the same installation method. Follow the instructions for the channel supplying the extension. If you cannot find an official link for your environment, ask Hice for it rather than installing an unrelated package with the same name.
Chrome and Edge
Chrome and Edge use packages for the Chromium environment. Install the version distributed for your chosen browser, enable it and make its button accessible. After signing into Hice, open a profile and verify that the panel shows a coherent preview before saving.
If evaluating the extension for a team, also try a user with limited permissions. Seeing the button is not a complete test: create a candidate or contact, retrieve it in the database and check that saving the same profile again does not create a duplicate.
Firefox
Firefox uses its own package and authorization flow. Follow the distributed version's instructions and grant the permissions needed for the extension to work on LinkedIn and Hice. Then try an open profile, checking the preview and save.
If the panel does not launch, verify that the extension is enabled in the browser profile you are using and that Hice sign-in is complete. A private window or company policy may require different configuration; do not confuse a browser restriction with missing profile information.
Safari
Safari uses the package intended for Apple's environment and activation in Safari extension settings. Follow the Hice distribution path for your device: uploading a Chrome package is not sufficient. Check site permissions and then try saving a profile.
Do not infer iPhone or iPad support from availability for Safari on Mac. Installation, device and site access should be checked against the distributed package. The operational criteria remain the same: a readable preview, an explicit user choice and a record retrievable in the Hice workspace.
Brave, Opera and Vivaldi
Brave, Opera and Vivaldi also document support for Chromium extensions. This lets you evaluate a compatible package, but does not replace testing your Hice version in your browser.
Verify sign-in, preview, saving and record retrieval. For a team, also check company extension policies. Browser engine compatibility and distribution of a Hice package should be verified together; separate pages repeating the same instructions for every brand are unnecessary.
Check duplicates before adding a person
Hice checks record identity and can reject a new save when it detects a duplicate, for example the same LinkedIn profile or an email already recorded. Matching names need attention: identical names do not prove that two records describe the same person.
When a warning appears, find the existing record and check company, source and contact details. Complete that record rather than changing the name to bypass the check. When evaluating software, examine how duplicates are identified and handled rather than assuming every incomplete identity can be recognized.
