FirstIgnite can write a summary it generates from a Minuet technology back onto that technology. There are two paths, and they behave very differently. Read the next section before you turn anything on.
Before you start: the summary has to have been generated from a Minuet technology, you can only sync a summary you own, and your Minuet administrator must have granted POST /api/technology (listed as "Write a summary back" in the endpoint list).
The two paths, and the one that overwrites
Manual sync. You open a summary, choose Sync, and FirstIgnite shows you the destination field and whatever is already in it. If there is existing content you choose whether to keep it or replace it. FirstIgnite writes nothing without that confirmation.
Automatic sync. If a team admin switches on Sync AI Summaries to Minuet under Minuet Settings in FirstIgnite (app.firstignite.com/inteum/settings), FirstIgnite writes every generated summary to the destination field the moment generation finishes, and it replaces whatever is in that field. There is no prompt, no preview, and no append option on this path.
Leave automatic sync off unless you want the field overwritten. It is off by default. If your team keeps hand-written text in the Non-Confidential Summary, automatic sync will replace it. That includes anything published through Tech Publisher. Use the manual path instead.
The rest of this page is about the manual path.
Where the summary goes
Out of the box, the destination is the technology's Non-Confidential Summary. You don't have to configure anything to use it.
To send summaries somewhere else, a team owner or admin adds a field mapping under Field Mappings in FirstIgnite's Minuet Settings. Pick the FirstIgnite AI summary (technology.aiSummary) as the source field, then pick the Minuet field you want as the target. It has to be an HTML field or a user-defined field; FirstIgnite refuses a plain-text Minuet column and says so.
You can also save a summary to the technology's Documents as a PDF. That's a separate choice, not a fallback if a text save fails. See Uploading FirstIgnite files to Minuet Documents.
Every sync also stamps the technology's Non-Confidential Summary date to today.
Syncing to an empty field
Open a summary generated from a Minuet technology.
Open the Minuet panel in the sidebar.
Choose Sync.
Check the technology and the target field shown.
Choose Save summary.
FirstIgnite checks the field first. If it's empty you'll see "This field is currently empty — your summary will be written to it." and it still asks you to confirm.
The Sync to Minuet panel for an empty field: the technology and the mapped target field are shown, and FirstIgnite still asks you to confirm before writing
Syncing when the field already has something in it
FirstIgnite shows the existing content under Currently in field, with an Open in Minuet link. What you can do depends on what's there:
Existing text: choose Add below to keep it and add the summary underneath, inside a block FirstIgnite marks as its own, or Replace whole field… to overwrite it. You'll be asked to confirm, because this can't be undone.
A summary FirstIgnite saved before: Replace earlier summary swaps out that block and leaves the rest of the field alone.
The field can't be read: only Add below is offered, never Replace. FirstIgnite tries to read the field again when you save, and if it still can't, nothing is written.
Nothing is preselected. You have to choose.
The Sync to Minuet panel when the mapped field already has content: the Currently in field preview, with the save options below it
Adding below is the safe path in both directions. Your team's notes stay exactly as written, and when you sync the same technology again you can replace FirstIgnite's earlier block in place rather than stacking up copies. Replacing the whole field does not work that way. It wipes the field, including any FirstIgnite block already there, and writes the summary on its own with no marker.
In an HTML field the marker is an invisible HTML comment. In a plain-text user-defined field it is a visible [FI:BEGIN summary …] line, so if you map to one of those, expect to see that marker in Minuet.
Check the destination before you confirm
The Currently in field preview and the Open in Minuet link both follow the field your team has mapped. If the technology or the field isn't what you expected, cancel and ask an admin to check the field mapping. FirstIgnite writes where the mapping points.
If a sync doesn't go through
"Sync in progress; retry." Someone else is syncing the same technology right now. Wait a moment and try again.
"Minuet is unavailable; try again." FirstIgnite couldn't read the current field content, so it stopped before writing anything. Nothing changed.
"Unauthorized to sync this summarization." You can only sync a summary you own.
The option is locked or missing. The technology write endpoint isn't granted in your Endpoint Access Group, or the summary wasn't generated from a Minuet technology.
For anything else, see Troubleshooting the Minuet integration.