1. Introduction

The Package Validity page provides administrative insight into a customer’s currently active subscription package, received from the webshop.
The system automatically enforces package limits (Admin, Worker, Resource) and validates whether the user can create additional records based on the purchased package.

2. Data Source

All package-related data is received from the webshop via API.
These fields are read-only in the system and cannot be edited manually.

The following values are imported:

• Package Type – the name of the purchased package
• Validity Date – the expiration date of the package
• Optional: additional transaction metadata for audit purposes

3. Page Structure

The page consists of two main areas:

1. Package Information (upper section)
2. Resource Usage Summary (lower section)

3.1. Package Information

This section displays all key subscription details received from the webshop.

Fields:

• Validity Date: The package expiration date. This field is read-only.
• Package Type: The currently active package (e.g., Starter, Standard, Pro). Read-only.
• Package Contents: The system displays the maximum number of Admins, Workers, and Resources permitted for the package.

Note: The package contents are stored at database level. They are not sent by the webshop. Each package’s limits are defined internally in the system.

3.2. Resource Usage Summary

The system automatically counts how many items the customer has created in each category:

• Admins
• Workers
• Resources

For each category, the page shows:

• Used: Currently created items
• Limit: Maximum allowed based on the package
• Remaining: How many can still be added

If the customer reaches the limit in any category, the system prevents further creation.

4. System Logic

4.1. Limit Enforcement

Whenever a user attempts to create a new Admin, Worker, or Resource, the system:

1. Checks the customer’s active package type
2. Retrieves the pre-defined limits from the database
3. Compares the current usage with the limit
4. If the limit is reached →
   • The system blocks the action
   • A warning message is displayed (e.g., “Your package allows a maximum of 5 Admins.”)

4.2. Package Validity Check

When performing any action related to user or resource management, the system verifies that the package is still active.
If the package is expired:

• New entities cannot be created
• The system may restrict access depending on configuration