SharingAccess

Sharing Access

The system allows you to set the access privileges for global access roles and customized roles, in order to meet the company needs.
You can establish access rules to apply for all roles and, at the same time, assign different rules and exceptions only to specific roles.

** Note: Every time you make changes, press Recalculate. **

Shared permissions:

• Private: only the owner of the VTECRM entity and users with a higher hierarchy role can read, publish, delete and edit data.
• Public (Read only): all users can see entity data; only the owner and users with a higher hierarchy role can publish or delete these data.
• Public (Read, Create/Edit): all users can see, create and edit entity data. Only the owner and users with a higher hierarchy role can delete these data.
• Public (Read, Create/Edit, Delete): all users can see, edit and delete all data.

If you apply access rules to some modules, these are extended to the emails related to the modules. You can define exceptions to the permissions defined by the role hierarchy:

1. Click Add Privileges for the module you want to create the exception
2. At Step 1 select the role owner
3. At Step 2 select the role to which you want to extend the visibility
4. Select the permission: Read Only or Read/Write

---

** Does Sharing Access also works for the Calendar module? **

The exceptions for calendar sharing are not managed from Sharing Access, but is the user who decides how to share his calendar. From Sharing Access you can set the Calendar module as Public or Private.

---

** How does the Public Calendar works? **

The following rules are true only for Public Calendar. All users are able to view all the activities of the other users.

There are three different types of public calendar:

• Read Only: the view possibilities respects the roles hierarchy (from top to bottom) and users can decide to share the calendar (with users that, according to the hierarchy, don’t have permission); the sharing involves Events and Tasks. Read Only means that users can assign tasks to: other users with a lower role and other users that have decided to share their calendar.
  Visibility scheme:

Visibility	Users can see the event	Users can see the content	Users can edit/delete
Public	yes	yes	yes
Standard	yes	yes	no
Private	no	no	no

• Read, Create/Edit: means that all the users can read and edit all the events on the calendar. In this case, an user can assign an event to another user, no matter the role hierarchy. Events with Private visibility can be read by other users, but they can’t view the details or edit them.
• Read, Create/Edit, Delete: means that all users can read, edit and delete all the calendar activities.

---

** How does the Private Calendar works? **

The following rules are true only for Private Calendar.
If the Calendar is set on Private privileges defined by the roles hierarchy: each user can access to activities of the calendar assigned to himself or assigned to users with a lower hierarchy role.

---

** How does the Event Visibility works? **

This field provide a further rule specifically for a calendar event, and can be set as:

• standard: follows the standard Sharing Access, Roles and Profiles rules.
• public: follows the standard rules, the event can be seen also by users you share the calendar with
• private: only the owner (Assigned To) and the administrator user can access to the event details; all other users see the activity (read-only) entitled “Private Event” but they won’t be able to see details.