Overview of Clarity Licensing Changes (Version 16.2.3 and Higher)

Products

• Clarity PPM SaaS
• Clarity PPM On Premise
• Clarity FedRAMP

Issue/Introduction

The logic for the licensing portlet has been updated to include resources who may have left the organization previously but are still associated with system activity.

• Instead of calculating the licensing period based on the month of the timesheet period, the portlet now counts the month the timesheet was posted as the licensing period.
• Example: An employee departed the company in August 2024.
  • Some of their historical timesheets from July/August 2024 remained unsubmitted. These were subsequently submitted and posted in the current month (July 2025) as part of year-end close activities.
  • As a result, the user appears on the current month's license report as consuming a restricted license, despite having left the organization nearly a year prior.

Environment

Clarity 16.2.3 and higher

Cause

This is due to a licensing design change implemented in version 16.2.3.

Resolution

In previous releases, Clarity counted user licenses based solely on assigned access rights. The methodology for identifying restricted users has been enhanced to provide more accurate license management.

What's New?

• Enhanced identification of restricted users now includes individuals present in Clarity transaction tables or posted timesheet tables, ensuring accurate license management based on system activity.
• Two new fields have been introduced in the 'User List by License Type' portlet: User Status and Sub License Type.

 

How do we calculate the user license types within Clarity? 

Based on the following conditions, a Clarity User will be counted as a Full, Restricted, or View License Type:

Sl. No.	User's Status	Access Rights by License Type (Requires At least One Access Right)	Result
1	Active	Full	User is counted under the 'Full' license type.
2	Active	Restricted (and no Full rights)	User is counted under the 'Restricted' license type.
3	Active / Locked / Inactive	View (and no Full rights)	Users who are not already counted under the Full license type, but are involved in either Clarity transactions tables or have posted timesheets within the calendar month, regardless of their status, are counted under the 'Restricted' license type.
4	Active	View (and no Full or Restricted rights)	User is counted under the 'View' license type.

 

Know About the New Fields

• User Status: Indicates the user's current status (e.g., Active, Inactive, Locked).
• Sub License Type: Indicates the specific condition that resulted in the user being counted under a Restricted license type. This column will only populate when reviewing “Restricted” license count details. The following values may be displayed:
  • User with restricted access: Includes users with an “Active” status who have been granted at least one access right of the “Restricted” license type AND do not hold any access rights of the “Full” license type.
  • User in transaction tables: Users who are not already counted in the Full license type AND are included in Clarity transaction tables within the calendar month, regardless of their current status.
  • User with Posted Timesheet: Users who are not already counted in the Full license type AND have posted timesheets within the calendar month, regardless of their current status.

Consider the following scenarios to understand how user license types are calculated:

• Scenario 01: Transition from View Only to Restricted License Type. When a user classified as 'View Only' generates an unposted transaction, executing the Post to WIP job changes their license type to 'Restricted' based on that transaction history.

• Scenario 02: Transition from Restricted Access to Posted Timesheet in Sub License Type. If a user's status changes from Active to Inactive, but they still have a timesheet that is subsequently posted, running the Post Timesheet job updates their Sub License Type from 'User with Restricted Access' to 'User with Posted Timesheet'.

 

Additional Information

More Information can be found here: Broadcom Documentation - Release Notes