Project Licensing

• Project ID — Each project is managed through a unique Project identifier linking entitlement, Quantity, Platform, contract, and deployment status.
• Project Scope — Scope may include Project Name, owner/end organization, contract, Product, Version, Platform, Quantity, administrator, status, and Activation Policy.
• Platform Pool — Quantity is allocated according to the approved Platform Pool, such as a Windows Pool or macOS Pool. Quantities do not automatically transfer between Platforms.
• Quantity — A project may deploy only the approved number of Licenses/Entitlements. Every Activation or allocation is checked against the remaining available Quantity.
• Product Entitlement — The Project is entitled to the Vietnam Office suite within the scope of the approved contract or project documentation.
• Version Entitlement — The deployed Version is controlled by the Project entitlement scope. Moving to another Version must satisfy the applicable Update/Upgrade policy and approval requirements.
• Activation Policy — A Project may use a deployment-specific Activation Policy, but it may not exceed the granted License/Entitlement and Quantity scope.
• Device Binding — For Windows/macOS, Project Activations remain subject to Device-Bound Licensing unless an approved deployment model specifies otherwise within supported system capabilities.
• Phased or list-based deployment — A Project may allocate Licenses by organizational unit, device group, or deployment phase, but the total may not exceed the granted Quantity.
• Project Pool may not be used outside the Project — Licenses/Entitlements granted to a Project may not be independently transferred to another customer, organization, or project without approval.
• No automatic transfer between Platform Pools — Windows Quantity does not automatically become macOS or Mobile Quantity. Any Platform Pool change must follow the applicable policy and approval process.
• Project Updates — A Project may deploy a new Release within the Version Entitlement and approved deployment plan.
• Project Upgrades — Upgrading to a new Version outside the current scope requires Upgrade Entitlement and the applicable commercial/technical approval before deployment.
• Backend is the authoritative management source — The Vietnam Office backend manages Project ID, Product, Version, Platform Pool, Quantity, Allocation, Activation, Device Binding, Status, and related rights.

Project licensing principle: defined Project → defined Product → defined Version → defined Platform Pool → defined Quantity → defined Activation Policy → deployment within the approved scope → no independent transfer of rights or quantity outside the Project.