Once the process is defined, it's necessary to map it to the real life. For example, once you define that project manager is accountable for approving of time tracking records, and published that on the corporate site, it would clearly make sense to provide possibility to navigate from that definition to time tracking records location. That allows increasing efficiency and speed of process adoption as well as simplifies adherence control.
 
In order to do that, ShareProcess provides possibility to link any model element to corresponding entity from real life, for example, link "Report" in model to report template stored in corporate repository; or link "Defect tracking system" with actual URL of such system.
 
Note that security policy is fully respected: users that are not allowed to access certain organizational assets will not be able to access them, even though they may see the link in published process suite. Additionally, you may manage accessibility of certain published process-related information by restricting access to corresponding web folders. Alternatively, you may split model into several independent parts and manage them fully separately, for example, define different suites of processs per business unit.