FAQ

What is the Changelog module for?

Changelog helps you communicate updates to the people who need to know about them, whether that's internal staff, IT stakeholders, or customers. You create Entries to announce changes and use Templates to keep them consistent. It works equally well for internal system notices, planned maintenance alerts, or public-facing release notes.

Who typically uses Changelog?

An IT manager might use it to keep staff informed about internal systems and policy changes, while an IT service desk lead could use it to announce planned maintenance and outages company-wide. A product manager at a software company might rely on it to publish customer-facing release notes. All three use the same Entries and Templates features, just for different audiences.

What can each role do in Changelog?

Admins have full access, including settings and subscriber management. Editors can create, edit, and publish entries but don't manage subscribers or settings. Members can create and edit entries but can't publish them. Viewers have read-only access, letting them see published updates without making changes.

How does access and permissions work in this module?

Access follows the workspace-wide RBAC model combined with Changelog's own roles, so what you can see and do depends on both your workspace permissions and your assigned role in the module. An Admin controls who gets which role and manages module-level settings and subscribers. This ensures only the right people can publish or edit sensitive announcements.

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

Most work happens in Entries, where you draft, edit, and publish updates as they happen. Templates help you standardize formatting so recurring announcements, like maintenance notices or release notes, stay consistent without rebuilding them each time. Editors and Admins handle publishing, while Members contribute drafts for review.

Can Changelog trigger actions in other parts of Metadot?

Yes. Entries in Changelog can act as triggers for no-code Workflows, so publishing an update can automatically send an email, create a task, update a field, or fire a webhook. This is useful for notifying subscribers or kicking off downstream processes whenever a new entry goes live.

Are Changelog entries searchable across the workspace?

Yes. Entries are indexed in the workspace-wide search, so anyone with access can find relevant updates without needing to browse through Changelog directly. This makes it easier for staff and stakeholders to locate past announcements when they need context.

How does Changelog relate to people records elsewhere in Metadot?

Because Metadot uses a shared identity model, anyone associated with your Changelog entries or subscriber list is the same underlying identity_core record used across other modules. This means a person your team communicates with here is recognized consistently, even if they also appear as a contact, requester, or customer elsewhere in the platform.