2072167 - Permissions - Cascading Goal Permission - Goal Management

• How do we control cascade permissions?

• Goal Management

• Cascading a goal is controlled at the goal template level so a person will only be able to cascade goals for their role as defined in the template permissions. For this reason different people may not be able to cascade goals as someone else might be able to. Roles are defined relative to you such as E, EM, EH etc.
• We also support the wildcard * role that enables a person to cascade to all. When set to * we can send to anyone except self.

• Note: Cascade-update=push-down only controls how the child goal's value is updated by the parent goal. This means that changes that are made in the Parent goal are pushed down to the child goal. The field permissions are not related to the cascade-push, so in this case, if the role "E" has write permission as is defined in the customers goal template, then they will be able to edit their goals.

<permission for="cascade-push">

<description><![CDATA[

Management hierarchy may push down through hierarchy.

]]></description>

<role-name><![CDATA[*]]></role-name>

</permission>

Roles you might use to allow the cascade of goals while at same time limiting who they can cascade to are

EM

EMM
EMMM etc to control levels

ED

EDD

EDDD etc to control the levels

EM+ will not allow to cascade up to everyone.

<permission for="cascade-push">

<description><![CDATA[

Management hierarchy may push down through hierarchy.

]]></description>

<role-name><![CDATA[EM+]]></role-name>

</permission>

cascading goals , KBA , LOD-SF-GM-TMP , Template Management , How To