Next Topic

Previous Topic

Book Contents

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
  • Deploy Agent 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

Kaseya 2 Share Options

  • Adding a user or user role to the Shared Pane allows that user to use that object. No additional rights, including View, have to be assigned to the user or user role to use that object.
  • Checking any additional rights—such as View, 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.
  • View does not refer to being able to view the object. View means the object's configuration can be viewed but not edited. If an export option is provided, View also enables the user to export the object.
  • Share means the users or user roles can assign share rights.

Legacy Share Options

Certain functions in Kaseya 2 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.

Taking Ownership

When you first create a user-owned object, you are the owner of that object. A user-owned object can only be owned by one user at a time. The owner of an object always has "full rights" to that object.

Master role users have an additional right, called Take Ownership, that allows them to take ownership of any user-shared object. When a user-shared object is selected or edited by a master role user, a Take Ownership option displays. When ownership is taken, the new owner of that object now has "full rights" to the object.

Typically the reason you take ownership of a shared object is to maintain its contents because the original owner can't do so. For example, the owner of a shared object may have left the company and no longer be available. In most cases, master role users can work within the share rights they've been assigned by other VSA users.

Note: Deleting a VSA user from the system assigns ownership of all objects belonging to that VSA user to the VSA user performing the delete.

Note: A master role user can check the Show shared and private folder contents from all users in System > Preferences to see all shared and private folders. For Private folders only, checking this box provides the master role user with all access rights, equivalent to an owner.