The procurement policy is your company's rulebook for buying software. Setting it in Nagata means these rules are applied when the chat assistant answers procurement questions.
What the policy covers
| Field | Description |
|---|---|
| Required certifications | Security or compliance certs a vendor must have (e.g., SOC 2, ISO 27001, HIPAA) |
| Banned vendors | Vendors your company has explicitly prohibited |
| No-go integrations | Third-party integrations a vendor must not use |
| Preferred contract length | Your preferred term in months (e.g., 12) |
| Approval threshold | Dollar amount above which purchases need additional sign-off |
| Required owner roles | Which roles must be assigned before a vendor is approved |
| Preferred payment terms | e.g. Net 30, annual upfront |
| Data residency | Where vendor data must be hosted (e.g., US-only, EU-only) |
| Notes | Any free-form rules your policy includes |
Setting your policy
Option 1: Fill in the form — go to Procurement Policy in the sidebar, edit each field, and click Save.
Option 2: Upload a policy document — upload a PDF or DOCX of your existing policy and Nagata pre-fills the structured fields. Review and confirm each field, then save.
How the policy is used
Once saved, your procurement policy is:
- Applied by the chat assistant — when you ask about a specific vendor or tool, the chat will surface any policy conflicts
- Available for procurement research — the Procurement Search page shows tool options against your policy constraints
The policy is advisory, not enforced. Nagata flags conflicts; your team makes the final call.