Editing Card Templates
Card Templates are where you define how physical Credential cards are produced: layouts, fields, encoding, approvals, and optional Duo ID behaviors. The editor is organized into tabs so you can work on one configuration area at a time.
Who this is for
This guide is for administrators who manage Card Templates for a Tenant or production setup (for example: production site operators, template designers, and system operators).
Required roles: System Admin + Production - Create Layouts
To perform the following steps, you need to have the roles listed above.
For an overview of roles in Breeze, see Roles and Permissions.
Open the editor
- Navigate to Templates → Card Templates.
- Find the Card Template you want to update.
- Click Edit Card Template.
The editor opens in a modal dialog with multiple tabs.
Editor tabs
The Card Template editor is organized into the following tabs:
- Production elements — Status, order type, layouts, fields, and general production settings
- Encoding and ranges — CSN readings, encoding files, number ranges, formulas, and manual encoding settings
- Approvals — Approval workflow settings, the Production Site for On-the-Fly Checkout, Duo ID Approval Routing, and Duo ID Auto-Approve
- Access control — AMR Transfer Template connections
- Advanced — Advanced configuration such as background removal settings
- History — When the template was created and last changed, its complete change history and restorable versions, including encoding-related changes. Always the last tab.
Production elements
The Production elements tab contains the core configuration for card production.
The device picker in General Settings reflects your Tenant's Production Site. Only devices available for that Production Site appear in the list. To manage which devices are available, see Managing Devices.
Field settings
Each field in the template can be configured with rules that control how data is collected and displayed. Some text fields can be marked as sensitive to encrypt their values at rest — only users with the Sensitive Data Viewer role can read the plaintext value. See Configuring Sensitive Fields for setup steps, or Sensitive Fields to understand what users see in Credential records.
Status and order type
- Status: Toggle between Active and Inactive.
- Order type: Choose between Single (individual orders) and Batch (bulk orders).
AMR Sync and Duo ID
- AMR Sync: Toggle between Disabled and Activated.
- Duo ID: Toggle between Disabled and Enabled.
When Enabled, you can configure Duo ID Approval Routing in the Approvals tab.
Approvals
The Approvals tab (also labeled Godkjenninger / Order flow in Norwegian) contains settings for approval workflows, the Production Site, Duo ID Approval Routing, and Duo ID Auto-Approve.
Approval settings
The Approvals section controls whether Credentials created from this template require approval.
- Enforced Approval activated: When enabled, Credentials require approval before they can be issued.
- Click Change setting to update the approval configuration.
Production site
Cards are normally made at your Tenant's own Production Site. With this setting, the cards made with one Card Template go to a different Production Site instead. Use it when your Tenant has one Production Site, but one type of card has to be made somewhere else.
Only Tenants that use On-the-Fly Checkout follow this setting. Tenants that order through the cart keep their own Production Site, even when they use this Card Template.
This matters for Card Templates shared across a domain: each Tenant that uses the template follows its own checkout flow. It also applies to users whose role is in the Tenant's Role Exceptions (Enforce default flow on roles): they order through the cart, so their cards go to the Tenant's own Production Site. See Checkout Flows.
Required roles: System Admin on the Tenant that owns the Card Template, and Super Administrator on the Production Site you choose.
Other administrators can still see which Production Site the Card Template uses.
How it works:
- Open the Approvals tab and click Change setting on Production site.
- Choose the Production Site that should make these cards. The list only shows Production Sites where you are a
Super Administrator. - Click Save.
To go back to the Tenant's own Production Site, clear the field and click Save.
What happens:
- New Credentials made with this Card Template on an On-the-Fly Tenant are sent to the Production Site you chose.
- The Production Site is set when the Credential is sent to production: when it is submitted, or, if it has to be approved first, when it is approved. Until then, the Production Site you chose cannot see the Credential, and a rejected Credential is never sent there.
- Credentials sent to production before you changed the setting stay at the Production Site they already have.
- Restoring an older version of the Card Template does not change this setting.
Duo ID Approval Routing
When Duo ID is enabled on your template (in the Production elements tab), you can configure a delegated Tenant for Duo ID approvals. This routes new Duo ID approval requests created from this template to a specific Tenant so you can centralize approvals.
How it works:
- Enable Duo ID in the Production elements tab.
- Open the Approvals tab.
- In Duo ID Approval Routing, select a Tenant in Duo ID Approval Delegated Tenant.
- Click Save.
What happens:
- New Duo ID approval requests created from this template are assigned to the selected delegated Tenant.
- Approvers review the request from the delegated Tenant’s Duo ID requests queue.
The Duo ID Approval Routing section is always visible:
- When Duo ID is Enabled, the dropdown is available.
- When Duo ID is Disabled, the section shows a Disabled indicator and the dropdown is hidden.
Routing is applied when the Duo ID request is submitted. Changing the delegated Tenant later does not move already-submitted requests.
Duo ID Auto-Approve Settings
Duo ID Auto-Approve sends a submitted Duo ID straight to production with no manual approval step. Turn it on only when you're confident in the data quality of the Duo ID submissions your Tenant receives — it skips manual verification entirely.
Auto-approve can only be turned on for a Tenant using On-the-Fly Checkout. If your Tenant uses a different checkout flow, the Enable Duo ID Auto-Approve checkbox is disabled with an explanation, and stays disabled until your Tenant switches to On-the-Fly Checkout. See Checkout Flows.
Required roles: System Admin
Only a System Admin can turn this setting on or off. Other administrators can still see whether it's currently Enabled or Disabled.
How it works:
- Enable Duo ID in the Production elements tab.
- Open the Approvals tab and click Change setting on Duo ID Auto-Approve Settings.
- Check Enable Duo ID Auto-Approve.
- Search for and select the Tenant user to record as the approver on auto-approved requests. Only active users who can approve Duo ID requests are listed: they need the
Approverrole and theAdministratorrole or higher, with access to this template's Tenant. If the template is shared with other Tenants in its Domain, the user also needs access to each of those Tenants, unless Duo ID approval is routed to a delegated Tenant the user has access to. - Click Save.
What happens:
- New Duo ID requests submitted on this template go straight to production — no one needs to open the approval dialog.
- The Tenant user you selected shows as the approver on auto-approved requests.
If the selected user loses the Approver role, or is deactivated or deleted, the setting shows a warning, and new Duo ID submissions on this template go to manual approval until you choose another user. Open the setting again to pick a new approver.
If your Tenant moves off On-the-Fly Checkout after you turn this setting on, new Duo ID submissions fall back to normal manual approval automatically. The setting itself stays on — it takes effect again if the Tenant returns to On-the-Fly Checkout.
If this template also has Duo ID Approval Routing set, Auto-Approve takes precedence: the request goes straight to production and the delegated Tenant is never asked to approve it. Turn off Auto-Approve if you want routed requests to reach the delegated Tenant's approval queue.
Your Tenant's On-the-Fly Checkout flow can define Role Exceptions (the Enforce default flow on roles setting) — roles that always fall back to manual approval instead of going straight to production. If the Tenant user you select as the auto-approve approver has one of those excepted roles, Duo ID submissions on this template wait for approval that never comes, with no error and no notice to anyone.
Pick an approver whose role isn't listed in your Tenant's Role Exceptions. See Checkout Flows for where that list is configured. To check a candidate user's own role first, open their profile's Roles tab — see Managing User Profiles.
Automatic Duo ID reminders
When Duo ID is enabled on a Card Template, you can configure automatic reminder emails to reduce expired requests. Collaborators receive two reminders per pending request: one at the halfway point to expiry and one near the expiry date.
See Duo ID Automatic Reminders for setup steps, cleanup period options, and what happens when a request expires.
Encoding and ranges
The Encoding and ranges tab contains settings used during RFID encoding and numbering.
This typically includes:
- CSN Readings (high frequency / low frequency)
- CardSDK Encoding DSC File(s) (optional)
- Number Ranges (up to 3)
- Formulas (up to 3)
- Manual encoding and optional production instructions
Access control
The Access control tab is where you connect AMR Transfer Templates to your Card Template. These templates control what data Breeze sends to access control systems when Credentials are activated.
Learn more: AMR documentation
Advanced
The Advanced tab contains advanced production settings for this Card Template.
Background Removal Settings
Click Change setting to configure how photo backgrounds are handled for Credentials produced from this template.
Mode — Controls what happens to the background when it is removed:
| Option | Description |
|---|---|
| Solid Color | Replaces the background with a solid color (default: white, #FFFFFF) |
| Transparent | Keeps the alpha channel — requires a card layout that supports PNG with transparency |
Auto-remove — When enabled, Breeze removes the photo background automatically the first time a Credential preview is created from this template. Each photo is processed once; re-creating the preview does not trigger a second removal.
| Option | Description |
|---|---|
| Enabled | Background is removed automatically on first Credential preview creation |
| Disabled | No automatic background removal (default) |
On Duo ID registration, the person sees the preview update once the background has been removed. This can take a little while.
Auto-remove requires Background Removal to be enabled on your Domain.
What you see while a background is removed
How quickly you see the result depends on how the Credential is created:
- Saving a single Credential. Breeze removes the background right away. This usually takes a few seconds.
- Batch orders and pre-production. Breeze removes backgrounds in the background, so the order is not held up. Each preview shows the original photo until its background is removed.
- When removal can't finish right away. If the service is busy or temporarily unavailable while you save a single Credential, the preview shows the original photo with a Removing background… badge. Breeze keeps trying, and the preview updates when it is done. You can carry on with other work.
The Removing background… and Background removal failed badges appear on the Credential preview and on the Credential in Production. If removal can't be completed, the badge changes to Background removal failed and the original photo is kept. Click Try again to start the removal again.
Breeze does not block production while the Removing background… badge is showing. A card produced at that point uses the original photo. Wait for the badge to clear if the card needs the photo without its background.
Removing backgrounds in bulk
In Production, click Remove photo backgrounds, select the photos, and click Remove background on selected photos. One click starts the run, and it continues in the background. Progress shows as, for example, "12 of 40 photos processed". You can close the window and keep working while it finishes. A single run handles up to 500 photos.
When the run is finished, the window also shows how many photos failed or were skipped. A photo that failed is kept as it was and shows the Background removal failed badge, so you can click Try again. A photo is skipped when Breeze is already removing its background or nothing needs to be done.
History
The History tab shows the complete change history for the Card Template — every change, who made it, when, and why — alongside a restorable version of each one.
At the top, Modification history shows when the template was created and last updated, who did it, and the template's current version number.
Change history
The history table lists every change made to the Card Template, including changes to its encoding settings (CSN readings, encoding files, number ranges, and formulas). Each entry shows the date, event type, the user who made the change, and — when one was recorded — the reason and comment. Click View Changes on an entry to see exactly what changed.
Versions and restoring a version
Every change also keeps its own version of the Card Template's settings, listed in the Versions table with its date and who saved it.
Click Restore Version to set the Card Template back to that version. Restoring writes a new history entry and keeps the current state as its own version first, so nothing is lost.
If something the version depends on — such as an encoding file or number range — has changed since that version was saved, a warning icon appears next to it. Restoring the Card Template does not change those related items back; review them separately if needed.
Restoring a version requires the same roles as editing the template. If the production site requires a reason for changes to published templates (see Publication below), restoring one asks for that reason too.
Publication
Some production sites require a Card Template to be explicitly published before further changes need a documented reason. This is off by default and is turned on per production site — see Enabling Card Template publication.
It covers every Card Template produced at that site, so you may see it on your own Card Templates even though the setting isn't yours to change. Ask whoever administers your production site if you need a template published.
When it's in use, the editor header shows one of three states:
| State | What it means | Can it be ordered? |
|---|---|---|
| Published | The customer has approved the design and test card. | Yes |
| Not published | The template already existed when publication was turned on. | Yes |
| Draft | The template was created after publication was turned on, and hasn't been published yet. | Only as a test card, see below |
A template marked Not published keeps working, so turning the setting on never takes existing templates out of use. Publish them when it suits you.
Producing a test card on a Draft
If you can publish Card Templates, you can order a Draft to produce a test card. Publishing records that the customer approved the design and a test card, so that card has to be made first.
Order the Credential as usual in the organisation's portal. Turn on Show drafts above the template picker — Drafts stay hidden until you do, and each one is marked Draft.
The toggle only appears for people who can publish. The organisation's own users never see it, so they still can't order a design the customer hasn't approved.
Test cards appear in the Card Template's history as test orders. Anyone reviewing the template later can see which cards were produced before approval.
Publishing a Card Template
Once a customer has approved the design and a test card, click Publish and add a reference to the customer's approval — for example the email and date. The template is marked Published.
Changing a published Card Template
After a Card Template is published, any further change to it requires a short reason. That covers editing a setting, adding or removing a field, restoring a version, deleting it (archiving instead, see below), changing which other organisations the template is shared with, and changing how it looks up identities. The reason is kept in the Card Template's history, so anyone reviewing it later can see what changed after approval and why.
Unpublishing a Card Template
Click Unpublish to return the template to Draft. You are asked for a reason, which is kept in the history. Ordinary users can't order the template again until you publish it, though you can still order it yourself as a test card. There's no way back to Not published, because publishing is what records the customer's approval.
Save or discard changes
- Click Save to apply changes.
- Click Close to exit the editor.
If you made changes and click Close, Breeze may prompt you to discard your unsaved changes.
If the Card Template is published and its production site requires a reason for changes, clicking Save first asks for a short reason before saving.
Deleting or archiving a Card Template
From the Card Templates list, use Delete to remove a Card Template you no longer need.
If the Card Template is in use — Credentials have been made with it, or it's referenced by a Mobile Credential Template or a user group — Breeze says so as soon as you press Delete, and lists what's using it. You are never asked to confirm a deletion that can't go ahead. Click Archive instead: archived Card Templates cannot be used for new orders, but everything already made with them is kept.
Archived Card Templates show an ARCHIVED label in the Card Templates list. Toggle Show archived to see them, and click Unarchive to bring one back into use.
Deleting, archiving, and unarchiving a Card Template all require the same roles as editing one.