Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The Edit License screen allows updating an existing software license record and is accessible at /it/licenses/:id/edit.

Overview

The Edit License page loads the existing license via useLicense. If not found, a “License not found” message is shown. The form is rendered using the shared LicenseForm component pre-populated with the existing data. Fields include: name, software name, license type, status, total seats, optional description, optional software version, optional publisher, optional license key, optional purchase date, optional activation date, and optional expiry date. On save, updateLicense is called with the updated data and the user is redirected to the license detail page.

Who it’s for

Requires IT_PERMISSIONS.VIEW (outer ITViewGuard). No additional per-route permission gate.

Before you start

  • You must hold IT_PERMISSIONS.VIEW to access this screen.
  • The license must exist.

Steps

1

Open the edit form

From the license detail page, click the edit action to navigate to /it/licenses/:id/edit.
2

Update license fields

Modify the relevant fields in the LicenseForm — name, type, seat count, dates, and other optional attributes.
3

Save changes

Submit the form. On success, the user is redirected to the license detail page.

Key concepts

  • LicenseForm — Shared form component used for both creating and editing licenses.
  • total_seats — Number of licensed seats available for assignment.
  • license_key — Optional; SME should confirm sensitivity and masking requirements.
  • expiry_date — Optional date when the license expires.

IT Service Management

IT Service Management overview.

Governance & parity

Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/it.tsx
  • src/cores/it/pages/licenses/EditLicensePage.tsx