A guide for administrators and IT teams using Flexigrant, from Fluent Technology, covering the default access, the GMSAIDueDiligence role and the tenant setting.
By default, any user with access to the Manage Grants menu in Flexigrant can run the AI Due Diligence Checker. To limit that, ask our support team to enable the dedicated GMSAIDueDiligence role. To remove the checker entirely, ask for the tenant setting to be switched off. You make both changes by raising a ticket on the support portal.
The checker arrived in Flexigrant v4.66 on 15 September 2026. Your data protection lead or information security team may ask who can use it before anyone does. So may your SRO, the Senior Responsible Owner for a central government programme. This guide gives you the three access states and the exact steps for each one.
Decide which of the three states you want: default, restricted or off. If you are restricting access, write down the names of the users who should keep it. Have your support portal login to hand. If your organisation has a change process for system settings, log this request through it first.
Keep the default if the people with Manage Grants access are the same people who carry out due diligence today. Choose the restricted state if Manage Grants is open to a wider group, such as programme assistants or finance colleagues who never check applicants. Choose off if your governance group has not yet approved any AI use, and revisit it once they have. Whichever you choose, the checker never runs by itself, and only the users you allow can start a check.
Your IT team will ask this before they approve anything. The checker sends only the organisation name and the registered numbers that a user types. It does not send application data, grant records or anything else held in your Flexigrant tenant. Processing takes place in the EU. The score itself comes from a fixed formula, not from the AI. The AI writes analysis notes, labelled as AI-generated commentary, for the officer to check against the source record.