FAQ

What is the Changelog module for?

Changelog is where you communicate updates to the people who need to know about them — whether that's staff, customers, or both. An IT manager can use it to announce internal system and policy changes, a service desk lead can post planned maintenance and outage notices, and a product manager can publish customer-facing release notes. Everything lives in Entries, and you can speed up repeat announcements with Templates.

What can each role do in this module?

Admins have full access, including module settings and subscriber management. Editors can create, edit, and publish entries. Members can create and edit entries but can't publish them. Viewers have read-only access, so they can see published entries but can't make changes. This lets you separate the people writing updates from the people approving and shipping them.

How do permissions and access work here?

Your workspace role and the Changelog module's own permissions together decide what you can see and do. For example, someone might be an Editor in Changelog but only a Viewer in another module — access is set per module, not globally. If you can't publish or edit something you expect to, check with your Admin about your assigned role.

What does a typical day-to-day workflow look like?

Most work happens in Entries: draft an update, refine the wording, and — if you're an Editor or Admin — publish it when it's ready. For recurring announcements, like weekly maintenance windows or standard release note formats, start from a Template instead of writing from scratch. Drafts can sit as work-in-progress until someone with publishing rights approves and releases them.

What are Templates used for?

Templates let you standardize the structure of recurring updates, such as maintenance notices, policy change announcements, or release notes. Instead of rebuilding the same layout every time, you start a new entry from a template and fill in the details. This keeps announcements consistent and saves time for anyone publishing regularly.

Can I trigger other actions when I publish an entry?

Yes. Actions in Changelog, like publishing an entry, can trigger automations such as sending an email, creating a task, updating a field, or firing a webhook — no code required. This means a published entry can automatically notify subscribers or kick off follow-up work elsewhere without any manual steps.

How does Changelog connect to the rest of Metadot?

Anyone mentioned or associated with an entry is recognized as the same person across every Metadot module, so a subscriber in Changelog is the same profile you'd see as a contact in CRM or a requester in Tickets — you never re-enter their details. Every entry you publish is also findable through workspace-wide search, so people can locate past updates without digging through the module directly.

Who can see subscribers and manage Changelog settings?

Only Admins can manage subscribers and module settings, such as configuring how announcements go out. Editors, Members, and Viewers focus on entry content itself and don't have access to subscriber management or settings screens. This keeps administrative controls centralized while still letting your team collaborate on content.