⇄Easily confused

Category = the role in the business (customer, prospect, supplier). One per contact. Tag = everything else (industry, trade fair, origin). Several per contact.

Both control the audience of a campaign. The test question for both is the same: Whom will I want to write to together one day?

A task is something you do. A follow-up is someone you want to get back to.

“Write quotation” is a task. “Call Mr Meier in two weeks” is a follow-up — it is attached to a person and brings them back onto your desk at the right time.

They are created in different places: tasks in the task list, follow-ups on the contact.

An unsubscribe is a declaration of intent — it cannot be reversed and applies to all future campaigns.

A block is a technical finding — it results from a bounce and can be lifted once the address has been corrected.

Releasing an unchanged address only means producing the same bounce again.

Archiving removes something from the selection and can be undone. Deleting is final — for attachments it removes the file from running campaigns too.

If in doubt, archive. The only case in which deleting is right is something that has to disappear for legal reasons.

Deactivate: the account can no longer get in; the assignment of tasks and histories is kept. That is right in almost all cases.

Delete: the person’s tasks and histories lose their assignment — irrevocably.

For “a team member is leaving”, deactivating on the last working day is the right and sufficient action.

In Aurora Hive Sites these are two different things: saved is not yet published — the real website stays unchanged until you publish.

The live editor shows the page as it looks — and that is exactly what leads to the assumption that it is already live.

In Aurora Hive Live there is no such intermediate stage: there, saving takes effect immediately on the public page.

The live editor is part of the admin area and works on the draft — for people who have access to Aurora Hive Sites anyway.

Aurora Hive Live works on the published page — for people without admin access.

Both show the page as it looks. The difference is who uses it and what is being worked on.

A site is a complete website with its own address. Most people need exactly one. A page is a navigation item within it — Home, About us, Contact.

Mixing them up has a very practical consequence: everything is attached to a site. If an area looks empty, the wrong site is usually selected at the top — the most common mix-up in Aurora Hive Sites of all.

A block on a page is a strip of that one page — heading, text, image, form.

A symbol (reusable block, in the “Symbols” area) is only inserted into pages, not copied: change it once, up to date everywhere.

Rule of thumb: if the same content appears on three or more pages, turn it into a symbol.

Publishing releases the current state — the normal case.

A release bundles changes so that they appear together. Useful for larger redesigns or when something is meant to go online at a fixed time.

You do not need it for everyday work.

The licence controls Aurora Hive Sales: modules, budgets and term are signed into the key, and the instance follows it. Changing it means issuing a new licence.

The subscription is the Aurora Hive Sites plan, with limits for websites, pages and storage. It is also carried in the licence; billing happens with your contracting party, not in the program.

The two run independently of each other.

An instance is a complete system of its own — own database, own users, own licence. Two instances cannot see each other.

A site is a website within an installation of Aurora Hive Sites; several sites share accounts and subscription.

If customers really need to be separate, they are instances. If one customer has two web presences, they are sites.

A template is the complete text of a campaign stage — subject and content.

A text snippet (for contracts) is a piece that is frequently repeated and inserted when creating a document.

And there is a third thing: a paragraph adjustment in a contract applies only to this one send — the template remains untouched.

The preview shows the template with the data of a real contact — in the browser. The quickest way to find a skewed salutation.

The test mail goes out as a real mail to an address of your choice. Only there can you see how a mail program actually displays the text.

Both are needed, and the test mail is best read on a phone.

“Carry on sending” — it only goes to those still waiting. That is the normal case.

“Write to everyone again” — also to those who have already received the mail. That is almost never what is meant, and to the recipient it looks like a mistake.

Read which of the two questions is on the screen.

Development — this is where things are built, with test data. Acceptance — this is where things are checked before they go into production. Production — your real system.

They look the same and have separate data and accounts. That is why the address bar tells you more than the screen content.

And be careful: contract mails can also be really delivered from test and acceptance environments if no protected sending mode is active there.

Protected sending mode: everything runs as usual — campaigns work, logs fill up — only at the end, messages are discarded instead of delivered. Recognisable by the notice in the header.

Paused campaign: sending is at rest; mails already started still go out. Recognisable by the status in the campaign list and by the bar standing still.

Both look similar from the outside and have different causes.

A contact is a person: name, address, history, unsubscribes. They remain, even when the project is over.

An opportunity is a project: client, status, deadline, volume. It ends at some point.

The rule of thumb: what you write to is a contact. What you follow up is an opportunity. The two are connected via the contact people in the opportunity file.

The area used to be called “Vacancies”. It is now called “Opportunities” and so also fits projects, enquiries and tenders.

A note is free text — what you want to record so that someone reads it later.

An activity is an event with a point in time — what happened.

In practice a note is usually enough, and the more important difference is another one: whatever you want to filter by belongs in a field. Whatever you want to read belongs in a note.

They are the same thing: the file is created from the company field on the contacts — there is no “Create company” button.

The most important rule of this area follows from that: a spelling variant creates a separate file. “Müller GmbH” and “Mueller GmbH” are two companies, each with half the history.

Search covers the entire data set — including what is not currently displayed.

A filter narrows down the display and stays set until you reset it.

And a third thing: Ctrl+F is the browser’s search on the open page — it only finds what is currently loaded.

A list that looks unexpectedly empty almost always still has a filter on from earlier.

Data is imported where it belongs — for contacts and for opportunities, above the respective list.

The Import history is the record: who imported which file and when. Nothing is read in there.

A run that has been undone remains in the list, greyed out — disappearing would be more convenient and poor evidence.

For Signature profiles, a crucial difference:

• All roles appear as badges in the header area.
• Only the default role carries facts, competences and projects onto the website.

If maintained content is missing on the page, it is almost always attached to a secondary role. Qualifications, on the other hand, apply across the whole profile.

Opportunity search: delivers opportunities and creates them in the CRM, with a contact person and a verified email address. Costs money.

Data collector: delivers a table — projects, profiles, career histories. It deliberately writes nothing into the CRM; the result is a file.

In short: one delivers work for sending, the other material to look at.

Take down first makes a backup and then removes images, database and files; subdomain and storage space become free.

Remove from the register deletes only the row in the administration — containers, database and files remain and continue to use resources.

This is deliberately kept separate: taking down remains manual work, so that nobody accidentally removes a running customer system.

• Aurora Hive Sales — people and transactions: contacts, campaigns, tasks, contracts. The CRM.
• Aurora Hive Sites — your website: pages made of blocks, design, translate, publish. The content management system.
• Aurora Hive Live — the editor on the finished website: click a text, change it, save.

The similar names are intentional; it is one family. The last two are the ones most often confused, and the difference is important: Aurora Hive Live publishes immediately, Aurora Hive Sites works on the draft.

No. Accounts, addresses, data, websites and licence keys remain as they were. The name has changed, nothing else.

• AURALIS became Aurora Hive Sites.
• AURA became Aurora Hive Live.
• Aurora became Aurora Hive Sales.

Your password still applies, the sign-in address is the same, and not a single entry has been touched in the process. The licence key also keeps its previous prefix — otherwise all keys already issued would have become invalid.

If you still come across the old name somewhere, that is not an error but a place that is still catching up. You can still search under the name you know: anyone typing “AURALIS” still ends up in the right place.