Skip to main content

What FirstIgnite reads from a Minuet technology

Two questions come up constantly. What actually leaves our Minuet instance, and why isn't the field we filled in showing up in FirstIgnite? They share an answer.

A technology opened in FirstIgnite: ID, title, status, disclosure date, the managers, a View in Minuet link, and tabs for Overview, Files, Patents and Grants

A technology opened in FirstIgnite: ID, title, status, disclosure date, the managers, a View in Minuet link, and tabs for Overview, Files, Patents and Grants

What crosses the wire

The two reads behave differently, and the difference matters for a security review.

Browsing the portfolio. FirstIgnite asks for a fixed set of 22 columns. Nothing else is requested.

Opening one technology. Minuet returns the full record, and FirstIgnite keeps the fields listed below plus your user-defined fields. Everything else is discarded on receipt rather than never requested. If a field must not leave your instance at all, the control is field permissions on the Minuet user, not this list.

The fields FirstIgnite keeps

Identity. Name, alternate title, technology ID, status, disclosure date.

Classification. Categories and interests (shown as keywords).

People. Inventors, lead inventor, manager and manager email, IP manager, project.

Content. The non-confidential summary (shown as the existing summary), comments (shown as additional notes), federal grant flag, net revenue, total budget.

Relationships. Owners, researchers, responsible parties, client departments.

Related records. Patents and grant awards attached to the technology.

Plus every user-defined field on the technology, with its label as your instance names it. This is how FirstIgnite reads whatever your office has added without anyone mapping it first.

It also keeps a few dates so the portfolio can sort and filter: created, updated and status dates. What it discards is the rest of the financial and licensing detail.

Documents

FirstIgnite reads document details to populate the picker. In the normal assessment or summary workflow, it downloads the files you select. The picker says how many you can choose for one run, 20 in total across all tabs by default, and any that can't be read are skipped rather than stopping the run. A file listed under more than one tab counts once.

In Tech Assessment, and in Summarize launched from FirstIgnite's Minuet portfolio, the picker lists files from three places, each on its own tab: the technology itself, its disclosures and its patents. On Minuet 20.1010 or later, the Technology, Disclosure and Patents tabs can also include supported remark, email and activity attachments associated with those records, each labelled with where it came from. Private remark attachments are excluded from the picker.

Two controls decide what can be listed:

  • Disclosure files are listed only after your Minuet administrator enables the Disclosure endpoint (POST /api/disclosures). See Enable new FirstIgnite endpoints in Minuet.

  • A FirstIgnite team admin can turn off Include remark, email and activity attachments under Minuet Settings. This limits future listings to direct documents. It does not remove files already imported.

Documents on other records, such as agreements, aren't listed.

Why a field you filled in isn't showing

In the order worth checking:

It's a user-defined field that's been hidden in FirstIgnite. Under Minuet Settings → Additional Fields visibility in FirstIgnite (depending on your location, app.firstignite.com/inteum/settings or eu.firstignite.com/inteum/settings), a team owner or admin controls which of your custom fields appear in FirstIgnite and feed into AI output. If a field is excluded there, FirstIgnite strips it after fetching. It exists in Minuet, FirstIgnite receives it, and you never see it. This is the most common cause and the easiest to fix.

The Minuet user can't see it. The account the integration runs as has its own record and field permissions. If it can't read the field, FirstIgnite gets nothing. A permission refusal on one column can fail the whole request, so a single missing permission can empty an entire list rather than blanking one field.

It's a standard field outside the set above. Opening a technology can return more fields than this view shows. If the field you need isn't listed here and isn't a UDF, it isn't included in this view.

What FirstIgnite never receives

  • Fields your Minuet permissions hide from the account it runs as

  • Records excluded through Record Access Control

  • Endpoints you haven't granted

  • Remarks marked private in Minuet

  • Agreement financial detail: royalty rates, revenue, estimated values, payables, billing comments, and the free-text summary

  • Content in Minuet's legacy rich-text comment field

It reads on demand

FirstIgnite doesn't replicate your Minuet database. It reads a page of records when someone browses, and one technology when someone opens it. There is no bulk import and no background copy.

Related

Did this answer your question?