Get Started with Redwood for Oracle Cloud HCM Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
SupervisorTEM vs. Default Supervisor Role
Summary
The Permissions do not matchContent
Release 16B, in July 2016, introduced "New" Supervisors that were not assigned permissions by SupervisorTEM in data integrations. Any Supervisors created after 16B would be assigned supervisor permissions by this new way. Any Supervisors already created before 16B were not affected.
Which means that since 16B our Supervisors do not all have the same set of permissions.
We have 2128 Supervisor Accounts; 270 of those are since 16B.
Note, too, that some of the permissions granted to Supervisors in 16B do not exist on a users permission list (Manage User Communications, for instance).
In the image below are the Default Supervisor Permissions of 16B and a the Supervisor Permissions of an active Pre 16B Supervisor.
0