Examples of Access to Nonprivate Succession Plans
In the automatic plan access method, only the named owners of the plan and employees who have access to the named or inferred plan incumbents can access nonprivate succession plans.
In this topic that includes some scenarios, you learn more about:
-
How plan incumbents determine access to nonprivate succession plans
-
How transfers can affect access to nonprivate succession plans
This image shows a reporting hierarchy in First Software. It shows the employees who report to the managers, and the employees the HR specialists have security access to. The managers and HR specialists shown in this image have the privileges to create and manage succession plans.
Nonprivate Incumbent Plan
Tate Scott creates a nonprivate Incumbent type succession plan for Devon Smith and names it D Smith Succession Plan. He adds Carlos Diaz as a Candidate Manager.
Now, let's see what access privileges the managers and HR specialists shown in the image have for this succession plan.
Employee |
View Plan |
Modify Plan Name |
Add Candidates |
Delete Plan |
Comments |
---|---|---|---|---|---|
Lucy Noh |
No |
No |
No |
No |
Lucy can't view the plan because she isn't a named owner. Also, her person security profile doesn't let her access Devon Smith's data. |
Carlos Diaz |
Yes |
No |
Yes |
No |
Carlos Diaz is the Candidate Manager. He can view the plan and add candidates. But, he can't change the plan name or delete the plan. |
Alex Anders |
Yes |
Yes |
Yes |
Yes |
Alex Anders isn't a named owner. But, Devon Smith is a direct report. This enables Alex to access Devon Smith's data. So, Alex Anders can manage the plan. |
Tate Scott |
Yes |
Yes |
Yes |
Yes |
Tate Scott is the default plan owner as he created the plan. |
Nonprivate Job Plan
Carlos Diaz creates a nonprivate Job type succession plan for the Senior Software Developer job. He names the plan Senior Software Developer Plan CD. As Vijay Singh and Devon Smith are both Senior Software Developers, they're the inferred incumbents of this plan.
Let's discuss what access privileges the managers and HR specialists shown in the image have for the Senior Software Developer Plan CD succession plan.
Employee |
View Plan |
Modify Plan Name |
Add Candidates |
Delete Plan |
Comments |
---|---|---|---|---|---|
Lucy Noh |
Yes |
Yes |
Yes |
Yes |
Vijay Singh reports to Lucy Noh. This enables Lucy to access Vijay's data. So, Lucy can access the Senior Software Developer Plan CD plan and manage it. |
Carlos Diaz |
Yes |
Yes |
Yes |
Yes |
Carlos Diaz is the default owner as he created the plan. |
Alex Anders |
Yes |
Yes |
Yes |
Yes |
Devon Smith reports to Alex Anders. Alex's person security profile lets him access Devon Smith's data. So, he can access the Senior Software Developer Plan CD plan and manage it. |
Tate Scott |
Yes |
Yes |
Yes |
Yes |
Tate Scott's person security profile lets him access Devon Smith's data. So, he can access the Senior Software Developer Plan CD plan and manage it. |
Plan Access Affected by Transfers
Devon Smith is transferred to another project and now reports to Lucy Noh. Tate Scott no longer has security access to Devon Smith's data. But, Carlos Diaz can now access Devon Smith's data. Another Senior Software Developer, Robin Marlow now reports to Alex Anders. Tate Scott has the security privilege to access this employee's data.
The administrator in First Software runs the Succession Plan Incumbents process to update the succession plan incumbent table for the changes resulting from employee transfers. Let's see how Devon Smith's transfer affects access to the D Smith Succession Plan plan.
Employee |
View Plan |
Modify Plan Name |
Add Candidates |
Delete Plan |
Comments |
---|---|---|---|---|---|
Lucy Noh |
Yes |
Yes |
Yes |
Yes |
Lucy Noh can manage the D Smith Succession Plan plan as Devon Smith now reports to her and she has access to Devon Smith's data. |
Carlos Diaz |
Yes |
Yes |
Yes |
Yes |
Carlos Diaz is the Candidate Manager for the D Smith Succession Plan plan. But, now he also has the security privilege to access Devon Smith's data. So, he can view and manage the plan. |
Alex Anders |
No |
No |
No |
No |
Alex Anders is not a named owner. After Devon Smith's transfer, Alex can't access Devon Smith's data. So, he can no longer view the D Smith Succession Plan plan. |
Tate Scott |
Yes |
Yes |
Yes |
Yes |
Tate Scott is the default plan owner as he created the plan. |
Let's also find out how Devon Smith's transfer affects access to the Senior Software Developer Plan CD succession plan. Now, Vijay Singh, Devon Smith, and Robin Marlow, who all have the Senior Software Developer job, are inferred incumbents for the Senior Software Developer Plan CD succession plan.
Employee |
View Plan |
Modify Plan Name |
Add Candidates |
Delete Plan |
Comments |
---|---|---|---|---|---|
Lucy Noh |
Yes |
Yes |
Yes |
Yes |
Vijay Singh and Devon Smith now report to Lucy Noh. This enables Lucy to access their data. So, Lucy can access the Senior Software Developer Plan CD plan and manage it. |
Carlos Diaz |
Yes |
Yes |
Yes |
Yes |
Carlos Diaz is the default owner as he created the plan. |
Alex Anders |
Yes |
Yes |
Yes |
Yes |
Robin Marlow, another Senior Software Developer now reports to Alex Anders. Alex's person security profile lets him access Robin's data. So, he can access the Senior Software Developer Plan CD plan and manage it. |
Tate Scott |
Yes |
Yes |
Yes |
Yes |
Tate Scott's person security profile lets him access Robin Marlow's data. As Robin Marlow is an inferred plan incumbent, Tate Scott can access the Senior Software Developer Plan CD plan and manage it. |