Download as txt, pdf, or txt
Download as txt, pdf, or txt
You are on page 1of 1

In this video, we will explore the

Line of Sight using the Goal Plan. The visibility up, down, and across the
organization depends on the
logged in user and their role. We are logged in as Manny Manager. Manny is
currently looking at his own
goal plan and viewing his own goals. This is the Employee View. But Manny is also a
manager of people. If the right role-based
permissions are in place, he can navigate down
to his direct reports', goal plans, and view their goals. Let's navigate to
Edward's goal plan. Manny is now looking at Edward's goal plan. He can see Edward's
goals as a manager. So this is the Manager View. From the main menu, Manny can
search for any other
user in the organization, or he can choose to go
back to his own goal plan. From the same drop-down, he has the option to navigate
across
the organization to his peers. Let's select Walter White. A pop-up message informs
us that the user does not have permission to access
this particular goal plan. This means that the
role-based permissions do not allow Manny to view his peers' goal plan. Manny also
go up the organization. Going up the organization means he is
going to view his manager's goal plan. Let's select Donna Director. Manny
successfully accesses
Donna's goal plan. So he's looking up at his manager's
goal plan and his manager's goals. This is the Direct Report View. Based on the
Line of Sight, we define which roles can
access which goal plans. This is defined in our role-based
permissions configuration. Notice how Manny cannot
add a goal for Donna. He cannot edit any of Donna's goals, and he can also not see
all of Donna's goal fields. Based on the Line of Sight, we define what the users
can see and
do on a goal plan, based on their role. This is configured in the
Goal Plan Template XML.

You might also like