User List by License Type - Full permission Resource Manager (Auto) on a resource that's not meant to have it

book

Article ID: 206050

calendar_today

Updated On:

Products

Clarity PPM SaaS

Issue/Introduction

We have a user that we setup as a Read-Only user and the system is defaulting them to Full user, it is adding on the "Resource - Manager (Auto)" access right even though this person is NOT listed as a Resource Manager on any resources.  

Please advise why this resource is defaulting to a Full license.

 

STEPS:
In the Administration - License Information - User Count by License Type - Click on Full

Resulting portlet is User List by License Type

Filter for the resource

License portlet this user still shows as Full License and Resource Manager (Auto) right although the user should not have it

Environment

Release : Any

Component : CA PPM SAAS RESOURCE MANAGEMENT

Resolution

Regarding your issue with Resource Manager (Auto) right on some resources. This is actually not a defect in the application. We tested creating a new user, then clearing up the Manager field and this worked to remove the right. You should only be careful and clear the actual OOTB field from the Resource list after adding it and it works great. Make sure you do not confuse it with any custom field, you have to update "Manager" or "Resource Manager".

Now why there are orphans and the rights still there although the field has been reset to Administrator? We suspect this was due to a database update done to erase the manager and set it to admin. This being done from the backend, the scripts to remove the rights did not run. We do not recommend doing this as it's an unsupported way to do it.

 

To fix the problem, please do the following:

  1. Identify the resources that have the right stuck behind (i.e. Jane Doe still has Resource Manager (Auto) in License Information
  2. Identify the reporting resources they had i.e. John Smith
  3. Add the Manager field to Resources list
  4. Find the reporting resources by the list First name/Last name ( i.e. John Smith)
  5. Set the manager on the resource to Jane Doe, Save
  6. Now remove the manager or set to Administrator, Save

This should remove the orphaned permission. We tested it and it works every time.

Keep in mind this is not a recommended use of the application. The design is to be using the Manager field and the Resource Managers are considered to be having a Full license.