Common Components Help

AEF Help

Determining a Route's Scope

The scope for a route determines who can be assigned tasks in the route, who can access the route, and in some cases, what content can be added to the route. The following are possible values for the route's scope:

• Organization--The route creator can add only people from his/her own company and one other company.
• All--The route creator can add people from any company, including roles and groups.
• project space--If Program Central is installed, the scope can be a specific project space. To see information about the project space, click its name.
• workspace, folder, subfolder--If Team Central is installed, the scope item can be a workspace, folder, or subfolder. This defines not only the route members, but also the upper limit for content that can be added to the route. For example, if the scope is the workspace, the content can be from any folder or subfolder and the route's members can be any person added to the workspace. If the scope is a particular folder or subfolder, the content can only be from that folder and any of its subfolders. The routes members can only be people who have at least Read access to the scope folder. To see information about the workspace/folder, click its name.

If Team Central is installed, and the scope of the route is defined as a workspace or a folder or subfolder, the scope can further limit the access and content of the route. The scope can:

• Limit the content of the route to the content within the scope item or below it in the workspace hierarchy.

For example, if the scope is the workspace, the content can be from any folder or subfolder in the workspace. If the scope is a particular folder or subfolder, the content can only be from that folder and any of its subfolders. So to add content from multiple top-level folders, the route's scope must be the workspace. To add content from different subfolders within a folder, the scope must be at least the folder (and can be the workspace).

You can add files to a route that are not initially in the scope of the route by uploading an external file to the route. However when adding the file, you must place the external file in a folder within the route's scope.

Note that accesses also limit the content that can be added to a route. The people who add content to the route, which is either the creator or route members who have Add access, can only add content from folders that they have at least Read access to.

• Limit the people who can be assigned tasks to workspace members who have Read access to the scope item.

For example, if the scope is a workspace, the task assignees can be any member of the workspace. If the scope is a folder or subfolder, only members who have Read access to the folder or subfolder can be assigned tasks.

• Associate the route with a particular folder, subfolder.

For example, you may want to associate a route with a particular folder because the folder belongs to a project team. A folder-scope route is listed on the Routes page for the workspace and for the folder but not on the Routes page for other folders in the workspace. Associating a route to a folder may be especially useful for routes that have no content. A folder-scope route that contains no content is still listed on the Routes page for the folder, even though it doesn't contains items from the folder.