Scopes

Meridian Enterprise is used to manage a wide variety of documents and the information about them. For some users, this breadth of information might seem overwhelming when they are trying to perform their day-to-day tasks. Scopes are way of limiting vault functionality and information to specific categories that are easier to use.

Scopes limit access to elements in the user interface, such as commands or options in drop-down lists. Scopes are not used to control access to specific objects in the vault. So, for example, if a vault has a project with a project type that is not in a user's scope, the user can still access the project if he has the required role assignments.

As another example, a vault used for managing facilities might benefit from having 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.

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

  • Custom (and standard) commands

  • Document types

  • Folder types

  • Workflow definitions

  • Project definitions

  • Reference types

  • Navigation views

  • Reports

Scopes also limit some Meridian Enterprise 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.

2021 R2