Understanding scopes

TeamWork manages a wide variety of documents and the information about them. For some users, this might seem excessive and daunting compared to the tasks that the users regularly perform. Scopes are way of limiting vault functionality and information to named sets that are easier to use. Users may select a scope when working in TeamWork that more closely meets their needs without presenting them with information overload.

Scopes limit users’ ability to create or work with the following objects:

• Custom (and standard) commands
• Document types
• Reference types
• Navigation views
• Reports

Scopes also limit some TeamWork functions:

• Folder access is restricted to a configurable root folder.
• Searches are restricted to accessible folders.

Each scope also defines a toolbar that can contain buttons that are most frequently used by users of that scope.

Note    Users may not work with any other objects than those defined in a scope. When creating scopes, be sure to enable all objects that users might need to work with.

For example, a vault used for managing facilities might benefit from different scopes for as-built documents, design projects, archived documents, or maintenance management. A vault used for managing AEC documents might use a different scope for each customer. And a vault used for manufacturing documents might use different scopes for standard parts, active projects, and inactive projects.

If any scopes are defined in a vault, users must select one when opening the vault. Users may select only those scopes for which they have the Can Use privilege.