"We finished the setup in Minuet and there's nothing Minuet-related in FirstIgnite" is the most common thing people ask after connecting. Usually nothing is broken. There are three separate controls, they're held by three different people, and connecting only satisfies one of them.
The three controls
Control | Held by | If it's missing |
API access in Minuet: the Endpoint Access Group and the Minuet user the client runs as | Your Minuet administrator | Specific features return nothing, or report missing permissions |
The Inteum user permission on a FirstIgnite account | FirstIgnite. You can't grant this yourself | That person sees nothing Minuet-related. No tab, no badge, no settings page |
Operations | A FirstIgnite team owner or admin | The feature is visible but locked, with "This is turned off for your team." |
Two settings screens matter, one in each product, and they're easy to mix up. This documentation always says which one it means.
In FirstIgnite: Minuet Settings, at
app.firstignite.com/inteum/settings, oreu.firstignite.com/inteum/settingsif your institution is on the EU environment. Operations, field mappings, connection status. This is what every "ask your admin to turn it on" message means.In Minuet: Setup → System Settings → Third Party Services → FirstIgnite for the connection itself, and Setup → System Settings → Advanced → API for the Endpoint Access Group and the API client.
Hidden versus locked
Hidden means the FirstIgnite account doesn't have the Inteum user permission. This is the answer to "I connected and I see nothing" and to "my colleague can't find the Minuet Marketing tab". Only FirstIgnite can fix it. Ask your FirstIgnite contact to add the Inteum user permission to the accounts that need it.
Locked means they have access but the operation is off. They see the feature with "This is turned off for your team." and a link to Minuet Settings, and a team owner or admin can switch it on.
The operations
All in the Operations section of FirstIgnite's Minuet Settings. Owners and admins only. Everyone else sees the page read-only. Everything is off until you turn it on.
CRM panel
Lets people see whether a record is already in Minuet, and view Marketing Projects, Marketing Targets, activity and agreements inside FirstIgnite. See Matching and adding contacts and companies in Minuet CRM and Working with Marketing Projects and Targets.
Turn this on first. It's read-only, and it's what the match badge depends on. With it off, the badge doesn't appear at all.
Send organizations & contacts
Lets people add FirstIgnite organizations and contacts to Minuet, one at a time or in bulk, either creating new records or linking to ones that already exist.
Matching and linking work with this off. What it gates is creating. Someone reconciling a record can still link it to an existing Minuet record, but the create option is locked.
Push marketing targets
Lets people create Marketing Targets in Minuet from FirstIgnite, creating the company or contact too if it isn't there yet. See Working with Marketing Projects and Targets.
CRM activity logging
Logs outbound email sent from FirstIgnite as Minuet remarks. See Logging FirstIgnite emails and activity to Minuet CRM.
Contact enrichment sync
Pushes FirstIgnite's enrichment into the Comments field of a contact or company already linked. See Matching and adding contacts and companies in Minuet CRM.
Sync AI Summaries to Minuet
Writes generated technology summaries to a field on the Minuet technology automatically, as soon as each summary finishes, replacing whatever is in that field. Leave it off unless that's what you want. The manual sync in the sidebar works without it and asks before overwriting anything. See Syncing FirstIgnite summaries to Minuet safely.
What each operation needs from Minuet
Customers often want the smallest set of endpoints for the one feature they care about. Here it is.
These are in addition to the baseline 17 covering the portfolio, technology detail, patents and documents, which you need for anything at all. Full list with paths and priorities: Minuet API endpoints required by FirstIgnite.
Operation | Endpoints |
CRM panel |
|
Send organizations & contacts |
|
Push marketing targets |
|
CRM activity logging |
|
Contact enrichment sync |
|
Sync AI Summaries to Minuet |
|
Enabling an operation can be refused
When you switch an operation on, FirstIgnite checks that Minuet is granting every endpoint it needs. If any are missing it refuses the toggle rather than letting you enable something that would fail the first time someone used it. It names what's missing.
Add those endpoints in Minuet, re-test the connection from Minuet Settings in FirstIgnite, then enable the operation.
This check reads Minuet's list of accessible endpoints. It doesn't call them. An endpoint can be granted and still return nothing if the Minuet user behind the client can't see those records.
Sync AI Summaries is the exception. That toggle isn't checked, so it will switch on whether or not Minuet is granting the write endpoint. If it isn't, the sync fails when someone uses it rather than when you enable it.
What a normal user can do
Someone with the Inteum user permission but no admin rights can use everything the team has enabled: browse the portfolio, run summaries and assessments, match and link records, view the panel, create marketing targets, send companies and contacts, log emails, sync summaries.
What they can't do is change any of it. The Minuet Settings page opens read-only with "You don't have permission to edit these settings. Contact your team administrator to make changes." FirstIgnite doesn't show them credentials or field mappings at all.
One more thing needs a project owner or a team owner/admin: linking a FirstIgnite project to a Minuet technology. A member the project is merely shared with can't do it.
The other settings
Owners and admins can also configure, on the same Minuet Settings page:
Field Mappings set where FirstIgnite writes in Minuet. The main use is sending the AI summary somewhere other than the Non-Confidential Summary.
Additional Fields visibility controls which of your Minuet user-defined fields appear in FirstIgnite and feed into AI output. This is instance-wide and field-level, not per record. Hiding a field here doesn't stop a mapping writing to it, and the settings page flags that combination.
Tech assessment names set how assessments created from a technology are named: generated from the input, the technology ID, the technology name, or ID and name together.
If something isn't working, see Troubleshooting the Minuet integration.