The following table describes the locations where a shared competency can be edited (in various ways) and deleted.
| If you share a competency, can you | in its home org unit? | in the org unit it’s shared with? |
|---|---|---|
| Delete the competency or its learning objectives | Yes | No |
| Edit the competency | Yes | Only the property “Make competency and its children visible to users who can be evaluated” |
| Edit its learning objectives | Yes | Only the property “Ready for Evaluation” |
| Add or remove learning objectives | Yes | No |
| Add or remove sub-competencies | Yes | No |
| Attach the competency beneath another competency | Yes | No |
| Add or remove activities | Yes | Yes |
The competency property Make competency and its children visible to users and the learning objective property Ready for Evaluation can be set independently within each org unit.
If these properties have never been modified within an org unit, they will automatically synchronize with the settings in the home org unit. However, once one of these properties is changed in an org unit other than the home org unit, it becomes completely independent from the settings in the home org unit.
For example, say you have a competency that was created inside the English Department org unit and shared with the course offering English 135. As long as you do not change the competency’s visibility property within English 135, it will automatically update to match the setting inside the English Department; if the competency is hidden in the English Department, it will also be hidden inside the course offering. If you change the setting inside the course offering, however, then it will no longer be linked to the setting in the English Department. So if you hide the competency inside the course offering for some reason, and then make it visible again, and then you hide it within the English Department, it will not automatically be hidden inside the course offering because the settings are no longer linked.