Delete a Changelog Entry Only When Unseen (iCampaign)

Release notes you write in Dazos Admin are shown to users inside every iCampaign instance. You can now remove an entry directly from the Changelog screen — but only while nobody has opened it yet. Each row tells you, before you try, whether it can still be removed.
​

You'll need:

Access requirements: The status badge and the Delete action are visible only to administrators. Anyone else who opens the Changelog screen sees the list and the Edit action, with no badge and no Delete.
​

⚠️ If you are an administrator and still do not see the badge on any row, contact Dazos support — it usually means the panel could not reach one of the instances and is still waiting on it.
​

From the left-hand menu, click Changelog.

The list shows every release note you have written, with its version, title, release date, and visibility. Each row now also carries a status badge in the first column, next to the row menu.
​

The badge answers one question: has anyone seen this release note yet?

💡 Tip: Hover over a badge to see the full explanation, including the names of any instances that could not be checked.
​

Open the row menu — the small button beside the checkbox — on a row marked Not read. The menu offers Edit and Delete.

⚠️ Important: Deleting a release note is permanent. There is no undo, and the entry cannot be restored from this screen.
​

On a row that is not marked Not read, the Delete item is greyed out and does nothing when clicked. Hovering over it explains why.
​

If a delete is refused, the message tells you exactly what stopped it:

An entry that has already been seen cannot be removed from this screen at all. If you genuinely need it gone, raise it with engineering.
​

What counts as "seen": Each instance keeps its own record of which user has opened which note — the same record that decides whether the release-notes popup appears for them. If that record exists anywhere, the note counts as seen.
​

What happens when an instance does not answer: An instance that cannot be reached, or whose setup has not finished, is treated as seen, never as unseen. That is deliberate: the panel will not delete a note on the assumption that an instance it could not ask has nothing to say. The delete is refused and the instance is named.
​

Because of that, one unreachable or half-configured instance is enough to make every entry undeletable until it is back. If Delete is greyed out across the whole list and every badge says Not checked, the problem is an instance, not the entry.
​

Why the badge can lag slightly: To keep the screen responsive while searching and paging, the badges are reused for up to half a minute before the instances are asked again. The delete itself never uses that shortcut — it always asks the instances afresh. So on rare occasions a badge may offer Delete on a note somebody has just opened; the delete is then refused, with the reason, and nothing is lost.
​

If you run into issues: