The AgilePoint Task List Web Part for SharePoint can be placed in various locations in SharePoint. The AgilePoint Task List Web Part interacts with one or more servers (e.g. AgilePoint, SharePoint, and/or database servers) whenever they are viewed or refreshed. This interaction is necessary and unavoidable in most cases, and is part of the AgilePoint system's expected usage patterns.
In some environments, the location for which the AgilePoint Task List Web Part is placed could have unintended effects on the system's performance. For example, in an environment where there are many thousands of SharePoint users, but only a fraction of those users interact with AgilePoint, placing the AgilePoint Task List control on an entry or Top Level site page that is frequently accessed by the entire group of SharePoint users may place additional unnecessary load on the AgilePoint system when the page is accessed by users that don't need access to the Web Part. In such a scenario, it may be better to place the Web Part on a sub site location that is only accessed by a more appropriate group of AgilePoint users and/or that is only accessed when necessary. You will notice errors being written to the AgilePoint Event Logs in the Event Viewer when a SharePoint site is being accessed (that includes the AgilePoint Task List Web Part) by a non-registered AgilePoint user.