⁂How the three programs work together

• Aurora Hive Sales when it is about people and processes: contacts, campaigns, tasks, contracts, candidates.
• Aurora Hive Sites when it is about your website: building, designing, translating and publishing pages.
• Aurora Hive Live when someone should only change a text occasionally without learning a content management system.

You can use each one on its own. The combination pays off when the same people both look after customers and maintain the public image.

The website wizard in Aurora Hive Sales creates a complete website from your details. With an agency key for the customer’s website, you connect it to Aurora Hive Sites and hand it over there.

Before the handover, a preview shows what would change. Into an empty website, everything is transferred; into a website with content, only what you choose per page — the customer’s existing content is never deleted or overwritten in the process.

After that: Aurora Hive Sites leads, and there is only one store. Aurora Hive Sales no longer keeps its own copy but is a window onto it: the pages are shown live from Aurora Hive Sites, and whatever you change in Aurora Hive Sales is saved directly there. If your customer changes something in Aurora Hive Sites or with Aurora Hive Live, you see it in Aurora Hive Sales immediately — with a notice, history and log.

If you and your customer have changed the same page at the same time, Aurora Hive Sales does not save blindly, but shows both changes side by side and lets you decide. Every earlier version can be restored with one click.

Aurora Hive Sites ships it: when a website is published, the editor for the finished page goes out with it.

This leads to a practical trap: after changes to the delivery, Aurora Hive Live may need to be published again so that the current version is on the page. If Aurora Hive Live no longer appears after a change-over, publishing again is the first thing to try.

Yes. Aurora Hive Sales and Sites are independent programs with their own user management; an account for one is not an account for the other.

Aurora Hive Live is the special case: who may change something there is determined via Aurora Hive Sites — there is no separate account management.

Not automatically. Form responses from Aurora Hive Sites end up in Aurora Hive Sites; contacts in Aurora Hive Sales stay in Aurora Hive Sales.

If you want to connect the two, there are two ways today: export the responses from Aurora Hive Sites and import them into Aurora Hive Sales, or set up the form so that the response goes as an email to a mailbox that Aurora Hive Sales syncs — it then appears in the inbox and can be created as a contact from there.

The second way is the more convenient one and needs no manual work.

Aurora Hive Sales stands for “Advanced Unified Relationship Orchestration for Retention & Acquisition” — the acronym describes what the CRM does: organise, keep and win relationships.

Aurora Hive Sites is the content management system, Aurora Hive Live the editor on the finished page. The similarity of the names is intended: it is a family, not a coincidence.

Do not confuse Aurora Hive Live with the term “inline editor” from older documents — it refers to the same tool.

With Aurora Hive Sales if you want to win customers — it has the quickest effect and needs the least preparation.

With Aurora Hive Sites if your website is the more urgent problem: a site without a legal notice (Impressum) or with third-party services is a risk that does not wait.

Aurora Hive Live comes last in both cases — it requires a published website.

What you should not do: everything at once. Three new programs in one week means that none of them is used properly.

Only in one place. Aurora Hive Sales has its address book, Aurora Hive Sites its websites and form responses — contacts and form responses are not synchronised.

The connection is the website itself: after a website built in Aurora Hive Sales has been handed over, Aurora Hive Sites leads, and Aurora Hive Sales accesses the same pages directly with the agency key. So there are not two versions that need to be synchronised, but one that both programs see.

Where you need a bridge, the practical way is via email: a form whose response goes to a mailbox synced by Aurora Hive Sales ends up in the inbox there.

By task, not by hierarchy:

• Whoever looks after customers: Aurora Hive Sales, Caller role.
• Whoever maintains the website: Aurora Hive Sites.
• Whoever only changes a text occasionally: Aurora Hive Live — no admin account needed.
• Whoever administers: Aurora Hive Sales as admin, Aurora Hive Sites with the corresponding rights.

Being sparing pays off above all with Aurora Hive Live: there, every change goes without an approval step onto the public page.

Yes. In customer management, brand and logo can be stored per customer — they apply to the instances created; Aurora Hive Sites also has its own settings for the look of the websites built.

The same applies to the logo everywhere: PNG, JPEG or WebP, 512 KB at most — SVG is deliberately not accepted, because it can contain executable parts.

By defining one leading place for each piece of information:

• Contact details are led by Aurora Hive Sales.
• Website content is led by Aurora Hive Sites — even if you edit it from within Aurora Hive Sales.
• Legal master data is kept separately in both programs, and that is where double maintenance actually arises. Keep it in sync when something changes.

Everything else hardly overlaps. Wherever you notice that you are typing the same thing twice, it is worth checking whether it really is two things.