Sharing User-Owned Objects

Each user has the ability to create user-owned objects—such as filtered views, reports, procedures, or monitor sets. Typically these objects start out as private objects. As a private object no other user can see them or use them. These user-owned objects can be shared with other user roles or with individual users. In some cases, a Master role user can make a user-defined object public for all users. Share options can include the right to use an object, edit, export, delete, or share an object with additional users. Share rights are set by each individual object separately. You can elect to share a user-owned object with:

  • Any user roles you are a member of, whether you are currently using that user role or not.
  • Any individual users that are members of your current scope.

If share rights for an object are granted by both user role and individual user, share rights are added to one another.

Typically a Share button displays on any page or dialog that edits a user-owned object. Individual Share buttons sometimes display next to each user-owned object in a list.

Examples of user-owned objects in the VSA are:

  • View Definitions
  • Manage Packages install packages
  • Monitoring Dashlets
  • Agent Procedures folders
  • Service Desk Procedures folders
  • Monitor Sets folders
  • SNMP Sets folders
  • Reports folders
  • Report Sets folders
  • Service Desk ticket named filters

NOTE   Folder trees have specialized rules about how folders are shared. See Agent Procedures > Schedule/Create > Folder Rights in online user assistance for details.

Sharing Options

  • Adding a user or user role to the Shared Pane allows that user to use that object. No additional rights have to be assigned to the user or user role to use that object.
  • Checking any additional rights—such as Edit, Create, Delete, Rename, or Share—when you add the user or user role, provides that user or user role with those additional rights. You have to remove the user or user role and re-add them to make changes to their additional rights.
  • Share means the users or user roles can assign share rights.

Legacy Share Options

Certain functions in the VSA still set sharing rights using a legacy dialog as follows:

  • Share rights are assigned by object. There are three sharing checkbox options. The first two checkboxes are mutually exclusive and determine what share rights are assigned. If neither of the first two checkboxes are checked, the shared object can only be seen by the users given share access, but the object cannot be used nor edited. The Shared and Not Shared list boxes and the third checkbox determine who can see the object.
    • Allow other administrators to modify - If checked, share rights to the object includes being able to use it, view its details and edit it.
    • Other administrators may use but may not view or edit - If checked, share rights to the object only allows using it.
    • Make public (seen by all administrators) - If checked, ensures that all current and future VSA users can see the object. If blank, only selected user roles and users can see the shared object. If blank, and new users or user roles are added later, you have to return to this dialog to enable them to see the specific object.