v1.5.0

We've got a big update for Beacon! We've added brand identities, full subscriber name support, and a live-preview form builder.

New features in v1.5.0:

• Subscriber name collection. Submission forms, the admin UI, and the token API can now collect and display a subscriber's full name.
• Brand identity & personalization. Create brand identities with custom logos, colors, themes, and email content. Assign them per bucket and changes apply instantly to all consent and preference pages.
• Admin announcements and footer. The admin panel now supports a configurable announcement banner and custom footer. Useful for environment labels or internal notices.
• Bulk record management. Select multiple records in the bucket view and export them to CSV, JSON, YAML, or XML. Bulk actions apply to your selection or the entire bucket.
• Preference links in export. Exports can now include a personalized unsubscribe URL for each subscriber. Configure the permission scope, expiry, and UTM parameters before downloading.
• Wildcard search. All search fields now support * as a wildcard. Try *@gmail.com or a1b2* across records, subscriptions, and the audit log.
• First seen date on subscribers. The subscribers overview now shows when each contact first appeared in Beacon.
• Expanded form localization. Submission forms now support Italian, Portuguese, and Japanese. Consent text and the Privacy Policy link are localized to match the selected language.
• Form builder live preview. The form editor now shows a live preview that updates as you type.
• Embedded form dark mode. Embedded forms now inherit the host page's color scheme and support dark mode. Background and text color overrides are opt-in.
• Version number in settings. The current Beacon version is now shown on the settings page.

Fixes until v1.5.0:

• Fixed form submissions not showing in the audit log. Consent changes made via a submission form were not attributed correctly. They now appear in the audit log under the form's name.
• Fixed permission name inconsistency. Permission names with spaces are now stored with underscores. This prevents records from becoming unreachable due to name mismatches.
• Improved admin panel load times. Several pages now load faster, particularly the bucket overview and identity list.
• Various UI fixes. Corrected styling, improved display for archived and removed buckets, and fixed unintended text selection in the admin panel.
• Updated packages. All dependencies have been updated to their latest stable release.

Please make sure to check out our documentation first, it'll guide you through the basics of the application. You shouldn't expect breaking changes in this update, we would have otherwise informed you here.

Full Changelog: v1.4.1...v1.5.0

v1.4.1

We've made some minor changes in this minor release of Beacon.

Fixes until v1.4.1:

• Fixed token and URL handling. Refactored token generation URLs to use the external API port and corrected default database lookup configurations.
• Resolved comprehensive GDPR compliance gaps. We improved privacy and security measures across erasure rules, error logging, token hashing, tracking flags and various other minor improvements.
• Optimized asset delivery. Added dedicated font serving endpoints and transitioned to self-hosted fonts to eliminate external CDN dependencies.

New features in v1.4.0:

• Consent audit log. A native audit module has been added. All consent changes are now tracked with a full history, including origin, utm tags if enabled, and the consent text agreed to.
• API key management. You can now create and manage named API keys with scoped permissions directly from the admin UI.
• GDPR compliance. We've made various improvements to make sure Beacon complies with the latest GPDR-rules.

Please make sure to check out our documentation first, it'll guide you through the basics of the application. You shouldn't expect breaking changes in this minor update–we would have otherwise informed you here.

Full Changelog: v1.4.0...v1.4.1

v1.4.0

We've got some nice new features in this update of Beacon! We've added API key management utilities, and the requested Audit-feature!

New features in v1.4.0:

• Consent audit log. A native audit module has been added. All consent changes are now tracked with a full history, including origin, IP address, and the consent text agreed to.
• API key management. You can now create and manage named API keys with scoped permissions directly from the admin UI.

Fixes until v1.4.0:

• Fixed broken consent audit trail. Opt-in events were not correctly recorded. All consent events now capture their origin, IP address, and consent text.
• Fixed subscription conflict under high load. Two simultaneous submissions for the same email could result in an error. Beacon now recovers from this automatically.
• Improved bucket list performance. The buckets overview loads significantly faster.
• Improved bucket records pagination. Navigating large buckets is now faster.
• Updated all packages. All dependencies have been updated to their latest stable release.

Please make sure to check out our documentation first, it'll guide you through the basics of the application. You shouldn't expect breaking changes in this minor update–we would have otherwise informed you here.

Full Changelog: v1.3.12...v1.4.0

v1.3.12

We've made some changes in this minor update of Beacon:

Breaking changes in v1.3.x:

• Generate token API-endpoint (only) supports arrays. You'll have to add the array wrapper [ {content} } to your requests, from this version and onwards (e.g. POST on http://localhost:5000/api/tokens/generate).

New features in v1.3.x:

• Embeddable campaign/consent forms have been added. You can now configure public forms (e.g. for newsletters) that'll push permissions directly to Beacon.
• Authentication supported. This means that you can use the default master key, custom API keys - or username and passwords to authenticate to the UI.
• Archiving of buckets is now supported. Instead of deleting the entire bucket, you can now archive a bucket instead.
• Subscription overview is also available. You can easily search one's membership in each bucket, based on their identifier.
• Confirmation notifications can now be configured. You can enable e-mail confirmations to the user signing up to a bucket.
• Application settings can now be (only partially) configured from the backend UI.
• Updated all packages. Some packages we using the previous .NET version.

Fixes until v1.3.12:

• Dependencies updated. All packages have been updated to their latest stable release.
• Fixed various styling issues. Small tweaks have been made to optimize the admin-page.
• Fixed SSE-errors. The server-side events were only partially implemented for buckets, which is now finalized.
• Fixed OpenAPI-exposure. The OpenAPI-page was wrongfully exposed on the Admin-page/port.
• Fixed adding permissions to existing buckets. Creating a new permission inside an existing bucket no longer results in a 404 error.
• Fixed consent state for submission forms. Submitting a public form will now always correctly update the consent state to opt-in.
• Fixed race-conditions in e-mail processing. In some cases, e-mails weren't sent out (instead, only when the cron-job was triggered).
• Improved archived bucket visibility. Archived buckets now show clear visual indicators when used in submission forms.
• Improved bucket ui-controls. You can now change the permissions more easily when creating a bucket or permission.
• Improved warnings in the UI. Enabling or disabling some modules will show conditional warrnings (e.g. upon creating new Permissions).

Please make sure to check out our documentation first, it'll guide you through the basics of the application. You shouldn't expect breaking changes in this minor update–we would have otherwise informed you here.

Full Changelog: v1.3.11...v1.3.12

v1.3.11

We've made some changes in this minor update of Beacon:

Breaking changes in v1.3.x:

• Generate token API-endpoint (only) supports arrays. You'll have to add the array wrapper [ {content} } to your requests, from this version and onwards (e.g. POST on http://localhost:5000/api/tokens/generate).

New features in v1.3.x:

• Embeddable campaign/consent forms have been added. You can now configure public forms (e.g. for newsletters) that'll push permissions directly to Beacon.
• Authentication supported. This means that you can use the default master key, custom API keys - or username and passwords to authenticate to the UI.
• Archiving of buckets is now supported. Instead of deleting the entire bucket, you can now archive a bucket instead.
• Subscription overview is also available. You can easily search one's membership in each bucket, based on their identifier.
• Confirmation notifications can now be configured. You can enable e-mail confirmations to the user signing up to a bucket.
• Application settings can now be (only partially) configured from the backend UI.
• Updated all packages. Some packages we using the previous .NET version.

Fixes until v1.3.11:

• Dependencies updated. All packages have been updated to their latest stable release.
• Fixed various styling issues. Small tweaks have been made to optimize the admin-page.
• Fixed SSE-errors. The server-side events were only partially implemented for buckets, which is now finalized.
• Fixed OpenAPI-exposure. The OpenAPI-page was wrongfully exposed on the Admin-page/port.
• Fixed adding permissions to existing buckets. Creating a new permission inside an existing bucket no longer results in a 404 error.
• Fixed consent state for submission forms. Submitting a public form will now always correctly update the consent state to opt-in.
• Fixed race-conditions in e-mail processing. In some cases, e-mails weren't sent out (instead, only when the cron-job was triggered).
• Improved archived bucket visibility. Archived buckets now show clear visual indicators when used in submission forms.
• Improved bucket ui-controls. You can now change the permissions more easily when creating a bucket or permission.
• Improved warnings in the UI. Enabling or disabling some modules will show conditional warrnings (e.g. upon creating new Permissions).

Please make sure to check out our documentation first, it'll guide you through the basics of the application. You shouldn't expect breaking changes in this minor update–we would have otherwise informed you here.

Full Changelog: v1.3.10...v1.3.11

v1.3.10

We've made some changes in this minor update of Beacon:

Breaking changes in v1.3.x:

• Generate token API-endpoint (only) supports arrays. You'll have to add the array wrapper [ {content} } to your requests, from this version and onwards (e.g. POST on http://localhost:5000/api/tokens/generate).

New features in v1.3.x:

• Embeddable campaign/consent forms have been added. You can now configure public forms (e.g. for newsletters) that'll push permissions directly to Beacon.
• Authentication supported. This means that you can use the default master key, custom API keys - or username and passwords to authenticate to the UI.
• Archiving of buckets is now supported. Instead of deleting the entire bucket, you can now archive a bucket instead.
• Subscription overview is also available. You can easily search one's membership in each bucket, based on their identifier.
• Confirmation notifications can now be configured. You can enable e-mail confirmations to the user signing up to a bucket.
• Application settings can now be (only partially) configured from the backend UI.
• Updated all packages. Some packages we using the previous .NET version.

Fixes until v1.3.10:

• Fixed various styling issues. Small tweaks have been made to optimize the admin-page.
• Fixed SSE-errors. The server-side events were only partially implemented for buckets, which is now finalized.
• Fixed OpenAPI-exposure. The OpenAPI-page was wrongfully exposed on the Admin-page/port.
• Fixed adding permissions to existing buckets. Creating a new permission inside an existing bucket no longer results in a 404 error.
• Fixed consent state for submission forms. Submitting a public form will now always correctly update the consent state to opt-in.
• Fixed race-conditions in e-mail processing. In some cases, e-mails weren't sent out (instead, only when the cron-job was triggered).
• Improved archived bucket visibility. Archived buckets now show clear visual indicators when used in submission forms.
• Improved bucket ui-controls. You can now change the permissions more easily when creating a bucket or permission.
• Improved warnings in the UI. Enabling or disabling some modules will show conditional warrnings (e.g. upon creating new Permissions).

Please make sure to check out our documentation first, it'll guide you through the basics of the application. You shouldn't expect breaking changes in this minor update–we would have otherwise informed you here.

Full Changelog: v1.3.9...v1.3.10

v1.3.9

We've made some changes in this minor update of Beacon:

Breaking changes in v1.3.x:

• Generate token API-endpoint (only) supports arrays. You'll have to add the array wrapper [ {content} } to your requests, from this version and onwards (e.g. POST on http://localhost:5000/api/tokens/generate).

New features in v1.3.x:

• Embeddable campaign/consent forms have been added. You can now configure public forms (e.g. for newsletters) that'll push permissions directly to Beacon.
• Archiving of buckets is now supported. Instead of deleting the entire bucket, you can now archive a bucket instead.
• Subscription overview is also available. You can easily search one's membership in each bucket, based on their identifier.
• Confirmation notifications can now be configured. You can enable e-mail confirmations to the user signing up to a bucket.
• Application settings can now be (only partially) configured from the backend UI.
• Updated all packages. Some packages we using the previous .NET version.

Fixes until v1.3.9:

• Fixed various styling issues. Small tweaks have been made to optimize the admin-page.
• Fixed SSE-errors. The server-side events were only partially implemented for buckets, which is now finalized.
• Fixed OpenAPI-exposure. The OpenAPI-page was wrongfully exposed on the Admin-page/port.
• Fixed adding permissions to existing buckets. Creating a new permission inside an existing bucket no longer results in a 404 error.
• Fixed consent state for submission forms. Submitting a public form will now always correctly update the consent state to opt-in.
• Fixed race-conditions in e-mail processing. In some cases, e-mails weren't sent out (instead, only when the cron-job was triggered).
• Improved archived bucket visibility. Archived buckets now show clear visual indicators when used in submission forms.
• Improved bucket ui-controls. You can now change the permissions more easily when creating a bucket or permission.
• Improved warnings in the UI. Enabling or disabling some modules will show conditional warrnings (e.g. upon creating new Permissions).

Please make sure to check out our documentation first, it'll guide you through the basics of the application. You shouldn't expect breaking changes in this minor update–we would have otherwise informed you here.

Full Changelog: v.1.3.8...v1.3.9

v.1.3.8

We've made some changes in this minor update of Beacon:

New features in v1.3.x:

• Embeddable campaign/consent forms have been added. You can now configure public forms (e.g. for newsletters) that'll push permissions directly to Beacon.
• Archiving of buckets is now supported. Instead of deleting the entire bucket, you can now archive a bucket instead.
• Subscription overview is also available. You can easily search one's membership in each bucket, based on their identifier.
• Confirmation notifications can now be configured. You can enable e-mail confirmations to the user signing up to a bucket.
• Application settings can now be (only partially) configured from the backend UI.
• Updated all packages. Some packages we using the previous .NET version.

Fixes until v1.3.8:

• Fixed various styling issues. Small tweaks have been made to optimize the admin-page.
• Fixed SSE-errors. The server-side events were only partially implemented for buckets, which is now finalized.
• Fixed OpenAPI-exposure. The OpenAPI-page was wrongfully exposed on the Admin-page/port.
• Fixed adding permissions to existing buckets. Creating a new permission inside an existing bucket no longer results in a 404 error.
• Fixed consent state for submission forms. Submitting a public form will now always correctly update the consent state to opt-in.
• Fixed race-conditions in e-mail processing. In some cases, e-mails weren't sent out (instead, only when the cron-job was triggered).
• Improved archived bucket visibility. Archived buckets now show clear visual indicators when used in submission forms.
• Improved bucket ui-controls. You can now change the permissions more easily when creating a bucket or permission.
• Improved warnings in the UI. Enabling or disabling some modules will show conditional warrnings (e.g. upon creating new Permissions).

Please make sure to check out our documentation first, it'll guide you through the basics of the application. You shouldn't expect breaking changes in this minor update–we would have otherwise informed you here.

Full Changelog: v1.3.7...v.1.3.8

v1.3.7

We're happy to share another update of Beacon, a lightweight consent management platform. Handle email consent states independently from any ERP, CRM or marketing-automation platform.

Features

• Free, open-source!. We intend to keep it that way.
• Easy management. It manages permissions in buckets. Easily accessable from an intuitive admin-panel.
• Multi-database support. You'll be using SQLite by default, but we support: SQL Server, PostgreSQL, MySQL.
• Multi-language support. Some of the most common languages are supported.

We've made some changes in this minor version:

New features in v1.3.x:

• Embeddable campaign/consent forms have been added. You can now configure public forms (e.g. for newsletters) that'll push permissions directly to Beacon.
• Archiving of buckets is now supported. Instead of deleting the entire bucket, you can now archive a bucket instead.
• Subscription overview is also available. You can easily search one's membership in each bucket, based on their identifier.
• Confirmation notifications can now be configured. You can enable e-mail confirmations to the user signing up to a bucket.
• Application settings can now be (only partially) configured from the backend UI.

Fixes until v1.3.7:

• Fixed various styling issues. Small tweaks have been made to optimize the admin-page.
• Fixed SSE-errors. The server-side events were only partially implemented for buckets, which is now finalized.
• Fixed OpenAPI-exposure. The OpenAPI-page was wrongfully exposed on the Admin-page/port.
• Fixed adding permissions to existing buckets. Creating a new permission inside an existing bucket no longer results in a 404 error.
• Fixed consent state for submission forms. Submitting a public form will now always correctly update the consent state to opt-in.
• Improved archived bucket visibility. Archived buckets now show clear visual indicators when used in submission forms.
• Improved bucket ui-controls. You can now change the permissions more easily when creating a bucket or permission.

Please make sure to check out our documentation first, it'll guide you through the basics of the application. You shouldn't expect breaking changes in this minor update–we would have otherwise informed you here.

Full Changelog: v.1.3.6...v1.3.7

v1.3.5

We're happy to share another update of Beacon, a lightweight consent management platform. Handle email consent states independently from any ERP, CRM or marketing-automation platform.

Features

• Free, open-source!. We intend to keep it that way.
• Easy management. It manages permissions in buckets. Easily accessable from an intuitive admin-panel.
• Multi-database support. You'll be using SQLite by default, but we support: SQL Server, PostgreSQL, MySQL.
• Multi-language support. Some of the most common languages are supported.

We've made some changes in this minor version:

New features in v1.3.x:

• Embeddable campaign/consent forms have been added. You can now configure public forms (e.g. for newsletters) that'll push permissions directly to Beacon.
• Archiving of buckets is now supported. Instead of deleting the entire bucket, you can now archive a bucket instead.
• Subscription overview is also available. You can easily search one's membership in each bucket, based on their identifier.
• Application settings can now be (only partially) configured from the backend UI.

Fixes until v1.3.5:

• Fixed various styling issues. Small tweaks have been made to optimize the admin-page.
• Fixed SSE-errors. The server-side events were only partially implemented for buckets, which is now finalized.
• Fixed OpenAPI-exposure. The OpenAPI-page was wrongfully exposed on the Admin-page/port.
• Fixed adding permissions to existing buckets. Creating a new permission inside an existing bucket no longer results in a 404 error.
• Fixed consent state for submission forms. Submitting a public form will now always correctly update the consent state to opt-in.
• Improved archived bucket visibility. Archived buckets now show clear visual indicators when used in submission forms.
• Improved bucket ui-controls. You can now change the permissions more easily when creating a bucket or permission.

Please make sure to check out our documentation first, it'll guide you through the basics of the application. You shouldn't expect breaking changes in this minor update–we would have otherwise informed you here.

Full Changelog: v1.3.4...v1.3.5