Ploy now connects to Freshservice for ticketing, plus a range of other improvements.

• Freshservice Ticketing integration: You can now integrate with Freshservice as your ticketing system, helping you manage access requests and other identity related issues in your native ITSM, or use it as a centralised backup for identity related work.

• API key management: Existing keys can now be edited (rename or change permissions) without revoking them. Scope options are grouped by category in the picker.

• Tags API: Create, update, and delete tags via the Ploy API using a key with tags permissions.

• Access review scoping: Campaigns can now be scoped to access rows carrying a specific tag, not just tags on the employee or resource.

• Luna: Luna can now draw on Ploy's accumulated knowledge about your environment when answering questions.

• User importer: Human identities can now be imported using an external ID alone, without an email address.

• Employee page: "Last Working Day" is now available as a column in the custom view picker.

• Profiles in the public API: create, read, update, and delete profiles via the API, with the full filter definition included.

• Resource and integration lookups: the resources endpoint now accepts exact-match filters by name, external ID, domain, and application status; new read-only endpoints for integrations and messaging channels are also available.

• Jira knowledge source, service-account auth: when setting up Jira as a knowledge source, you can now choose between OAuth and a service-account API token scoped to specific projects, so Ploy can only read what that account can access.

• Signup source on active access: the origin of a shadow-IT signup, captured by the browser extension, now stays visible after access moves to the active tab, so you can always trace how it started.

• API docs: nested object schemas now expand inline, and the navigation panel scrolls independently of the content panes.