Permissions

feature permissions those permissions are automatically created at the first launch of the tenant, they are designed to manage access to hyperportal`s features you can set those permissions only for crm groups in the group editor you can learn more about groups here go to crm > groups, choose a required group then you can add or delete permissions in the 'permissions' form group`s permissions are extended to its users those permissions are 'bulk edit' \ enables the editing of multiple items at a time 'export' unlocks the possibility to export data 'forms' gives access to the hyperforms 'hyperbi ' gives access to the hyperbi 'mail templates' gives access to the email templates configuration 'integration ' gives access to internal data from outside 'workflows' \ gives access to the workflows module 'process cancellation' gives access to the process cancelation 'custom data ' and 'portal' these features enable access to all common hyperportal features if it`s disabled the users in the group won`t be able to use the service 'portal administrator' \ gives the administrative rights to users in the group this means that the users will be able to and edit any permissions on the portal groups with this permission can also create new entities and modify existing ones data permissions data permissions can be given to groups and individuals they can be edited in the entity editor, you can learn more about it here there are three separate types of permissions view, create and delete they can be set separately for example certain groups or individuals could only view items but not edit or delete them because they only have a 'view' permission you can also edit permissions for each separate property individual permissions can be given at the bottom of the permission tab keep in mind that you can give individual permission only to users that are in the 'contact' entity items you can learn more about adding new users here process permissions you can set permissions for processes and tasks those permissions are divided into view, delete and execute permissions those groups and individuals that have view permissions will be able to open and view processes, those with execute permissions can start new processes, and users with delete permissions can remove processes users that have 'execute' and 'view' permissions will be able to start the process from the workflows dashboard you can also edit permissions for each separate task individuals and groups will be able to view and execute only those tasks that they have permission for users with 'execute' and 'view' permissions for manual tasks will be able to see those tasks on the workflows dashboard multiple permission sources we know that permissions come from three different sources(feature permissions (admin rights), data permissions, and individual permissions) if the user was given permission to only view the item by one source but to view and edit it by the other source, then the permission with higher elevation will work only let`s look at the example james smith is in a hyperportal users group he wants to create a new 'xdms order' entity item, but the group that he is in doesn`t have permission to add a new item james smith will still be able to add an item because he has individual permission set for him in the 'xdms order' entity