huntitHelp center

Editing, removing — and what can never change

Every client, brand and profile has an Edit button on its name line. It opens a window where you change what can be changed. If you're allowed to delete the record, a delete link sits under the form.

Some fields never change. The only way to change one is to delete and re-add.

What you can edit — and what's fixed

EntityYou can changeYou can't change
ClientName, logo, account manager, status, industry, language, service tier, notesIts onboarded date
Brand / creatorName, type, Tracking (Active / Paused)Its parent client
ProfileTracking (Active / Paused), Media tracking — which formats it collects, and how often each is re-checkedProfile URL, platform, parent brand

A profile can't be moved to a different brand, and a brand can't be moved to a different client. Both are delete-and-recreate, never edits.

A client's logo is a card showing the picture they wear now and where it comes from. Click it to upload or replace. An uploaded logo also carries a Remove that applies straight away, after which their own brand's profile picture or their initials stand in.

Changing a client's language or logo also reaches reports you've already sent. Before you save a new language, the window says what changes and what doesn't.

Switching a format on or off later

In a profile's Media tracking, a format you switch on is tracked from that moment. On a Facebook profile that is collecting, switching on Photos or Text posts when neither was on also imports that format's last 50 posts once — see the profile page.

A format you switch off stops collecting new posts; those already tracked finish their check-ins.

How deletion works

The delete link opens a confirm step.

That step counts what will be lost: for a profile, its collected posts and how many were winners; for a brand, its profiles too; for a client, its brands, profiles, posts and stored reports.

There's no undo.

Who can delete what

  • Deleting a client needs the Delete a client permission, granted to nobody by default, so it stays with the owner unless they hand it out. The client's name must always be typed to confirm, and without the permission the delete link doesn't appear.
  • Deleting a brand or a profile needs Delete brands and profiles, a separate permission granted to managers by default; without it the delete link doesn't appear. Your owner decides who holds each.

What dies, and what survives

You deleteGone foreverSurvives
A profileIts posts, winners, AI analyses, charts, calibration, historyStored reports and their share links, with this profile and its posts removed from them
A brandThe brand and all its profiles, with everything aboveStored reports and their share links, with this brand, its profiles and their posts removed from them
A clientEverything under it — brands, profiles, posts, usage history, its notifications — and its stored reportsNothing. The client's report share links go dead

Saved views that filtered on what you deleted stay under their names and show fewer posts, or none (saved views).

Deleting the client is the one thing that ends a stored report.

Deleting is not the same as pausing

If you only want to stop tracking for a while, pause instead of deleting. Set the profile's Tracking to Paused, or pause the whole brand, or set the client's Status to Paused, to stop everything under it.

Deleting is permanent. Pausing keeps everything already collected, though posts published while paused aren't back-filled — see pausing tracking.

Re-adding starts fresh

If you delete a profile and add the same account again later, it comes back as a brand-new profile:

  • Historical collection runs again, and is billed again.
  • Calibration restarts from zero.
  • The old badges and history don't transfer. Every post collected again is judged for badges from scratch.

Who deleted X, and when

Every deletion is recorded. Open Settings → Activity log to see them, alongside tracking pauses and resumes, changes to what a profile collects, data exports, ownership transfers, role changes, and changes to what each role is allowed to do.

It also records three paid runs — a collection restart, a history import and a re-analysis — plus a client's offboarding and every access change.

Each entry names the action, what it covered, who did it and when.

Reading the log is its own permission, granted to managers and members by default.