UPDATE RE: Employee alignment and Hierarchy May 15, 2025


We have updated the CFM's custom overnight script so that it will assign the first Report Manager for each company providing they are the RM that only has permission to see 'Users that Report to Them' (so no other Security Profile that elevates their User Visibility). (Kenna’s update #2) This will not impact any manual updates to employee reporting structure. (Claires update #1)

 

If Joe is first in company ABC to self-register as RM (looking chronologically at user registration date/time for that company with designation as RM YES),  he

  • Gets Supervisor and Report Manager(custom) security profiles via script 
  • gets all same company employees reporting to him.

 

Then Sally registers as RM - she 

  • gets Report Manager security profile via script 
  • but no users are assigned to her.

Intellek/IAAR wants Sally to be the primary RM 

  • adds Supervisor security profile to sally's account.
  • Intellek/IAAR removes Supervisor and changing Report Manager YES to NO in Joe's account. 
  • Bulk edits all company users to report to Sally.
  • tomorrow the manual edits will stand and the script will not move users to report to Joe.
IMPORTANT NOTE: Users (JOHN) for this company still designated as RM(custom) and John was chronologically first to register, new users registering for that company will be aligned with John as a manager. Best practice when establishing Hierarchy - check the company for all users with Supervisor and RM security profiles and remove those profiles for anyone who shouldn't be in the list.  Change RM YES to NO.


Hierarchy is established later and Joe needs to see all the people too, so Intellek/IAAR

  • Sets joe up as Report Manager Full Hierarchy and Supervisor
  • Sets up joe as Sally's Manager
  • Joe sees Sally and all of the company employees who report to Sally
  • Sally sees all of the company employees  



The Report Manager Script works this way. https://intellek.freshdesk.com/a/tickets/16009


1. A daily script will check for anyone who has selected who mark Yes to the Report Manager? (Practice Area) field in self-registration. The script will assign three security profiles 1) Standard User 2)Supervisor and 3) Report Manager (custom).

Note: If more than one person marks Report Manager? Yes for a company, then the incorrectly marked users will need their security profiles manually adjusted (remove Supervisor, and Report Manager). Intellek can do this with IAAR permission.

IF a User selects Report Manager and they are not, they could be assigned to Users that they shouldn’t see. Ogletree accepts the risk and responsibility of this.  


2. A daily script will run to assign the FIRST User that selected Yes to ‘Report Manager?’ for each Company and assign that Report Manager as Manager to all Users with the same Company Code. There should only be one "Report Manager? > Yes" for each Company. The Report Manager will be assigned the default Manager (system Administrator).

Note: If more than one person marks Report Manager? Yes for a company, only the first one will be aligned as the manager for all that company's users. With IAAR direction, Team Intellek can manually correct the Report Manager? field to No and security profiles for someone incorrectly aligned in that role. The Script will index overnight, and assign all company employees to the corrected Manager (the only person for that company marked as Report Manager? Yes).



In the examples below, Mark sees Employee 1, because he is Employee 1’s “Manager”. Sally sees Employee 1 because she has the full Hierarchy security profile, allowing her to see everyone under her chain of command. She sees Bob and all of his people (which includes Mark and all of his people)

 

Example: Company Code XYZ

 

Sally is the 1st person to register as Report Manager?, Yes for XYZ company (XYZ).

  1. An overnight script runs to set up Report Manager?, Yes users with the following Security Profiles (added to the default Standard Learner Security Profile)
  • Report Manager (custom)
  • Supervisor 

 

  1. Management Status

An overnight script is run for the 1st person to register as Report Manager?, Yes for each company to set that person up as the Manager for all other users in that company. In our example the Supervisor/ Manager field for ALL XYZ User accounts is given a value of Sally. After 24 hours, Sally will be able to see all XYZ users in the LMS.

 

  1. Reports to
  • Sally’s own Supervisor/Manager field is given the default value of System Administrator.

 

Mark and Bob are the 2nd and 3rd people to register as Report Manager?, Yes for XYZ. 

  1. An overnight script runs to set up Report Manager?, Yes users with the following Security Profiles (added to the default Standard Learner Security Profile)
  • Report Manager (custom) - this will be a meaningless designation if no users ‘report to’ to this user
  • Supervisor - this will be a meaningless designation if no users ‘report to’ to this user

 

  1. Management Status – No script is run for 2nd & 3rd … Report Managers, Yes users. No users “report to” Bob or Mark automatically. If multiple RMs are needed (hierarchy), Report Manager accounts will need to be manually corrected or updated. All users with the same Company Code “Report to” Sally.

 

  1. Reports to
  • Bob and Mark’s Supervisor/Manager field has the value of Sally

 

Decide what the structure needs to look like. If a user needs to see other users, They must first have both Report Manager (custom or Full Hierarchy) and Supervisor Security Profles, then they need users who report to them based on the order/structure you establish. Who is at the bottom of the chain with direct ”reports” and who is at the top of the chain with full hierarchy. Follow the steps we went through together Friday to set up this type of structure: