On this page0
Unfamiliar word? See Glossary: words used in these docs. Looking for the tasks in order? Begin at Start Here.
Reference
Vendor Pricing Catalog
A reference list of common SaaS vendors’ per-seat plan prices, which persona cost estimates draw on when you pick the software a role needs.
Where To Find It
Security Settings → SaaS Pricing. The tab has two halves:
Pricing Catalog
A short explanation of what the list is, with the notice “No vendor price feed is connected”.
Vendor Seat Plans Catalog
Each vendor, plan tier, price per seat, and when the row was last updated. It comes pre-filled with a reference list of common vendors when your instance is set up.
What You Can Do With It
This is a read-only reference list. The prices came with Zonitix. Nothing refreshes them from the vendors, and they cannot be edited from this page yet, so the screen has no sync button and no schedule. Persona cost estimates are calculated from this list: read them as a guide and check the figures against your own contracts before making a spending or renewal decision. They are not your negotiated rates.
If something here is not working as you expect, start with When something goes wrong.
The plain explanation is above. This part is for IT and developers: the exact settings, permission names, API addresses and data fields behind it. Closed: select the heading above to open it. While it is closed, your browser’s find-on-page (Ctrl+F or Cmd+F) does not search this part.
The screen is at /dashboard/security?tab=pricing.
The Endpoints Behind It
Four routes exist under /user-management/saas-pricing. Only the first is used by the screen today.
GET /plans— the catalog. Needsview_users,manage_usersormanage_security.GET /scheduleandPUT /schedule— read or set the sync schedule. Both needmanage_security. ThePUTbody is{ frequency, cron };cronis standard 5-field syntax (for example0 0 * * 0for Sunday at midnight). An invalid expression is rejected with 400 and the previous schedule keeps running. A change is audited asSAAS_PRICING_SCHEDULE_UPDATE.POST /sync— run the sync now. Needsmanage_security. A manual run is audited asSAAS_PRICING_SYNC_RUN.
A sync run changes no price and does not set a last-synced time (a time left by an earlier release is cleared), because no vendor price feed is connected. POST /sync still answers 200 with a top-level message of “SaaS vendor prices synchronized successfully”, so do not rely on that text. Read details instead: { success: false, synced: false, reason: 'no_vendor_feed', checked, count: 0, message }, where checked is the number of plans in the catalog and count the number of prices changed.