NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm

Task Security

Summary

This document attempts to explain Task Security in ClientSpace.  For more detailed information about security entities refer to Security Entities info in our workspace security doc..
 



Security Hierarchy
  • Default Security (No Incident Security Entities) - If you are the Creator, AssignedTo or Owner of the task, your user account will have View & Edit rights to existing tasks. Notification Users will have View Access to the task, but unless additional security is provided by other entities the task fields will be read-only.  You can Add Tasks to Org, Contacts or a dataform. Due Date field and Mark for Deletion field are read only by default.
  • Incident_AllowTaskMaintance - Allows user to edit tasks even though they are not one of the principal users of the task. (Creator, AssignedTo, and Owner)
  • Incident_DueDate - Gives users rights to edit Due Date field.
  • Incident_MarkForDelete - Gives users rights to edit Mark for Deletion field.
  • Incident_Dash_CanViewAllUsers - Unlocks the User search field on the Task Search Module.
  • Incident_Can_Add_Without_Dataform - Put the Add button on the Home dashboard and the Task Search Module. Still presents the workspace selector.
  • Incident_btnMassUpdate - Gives access to the Mass Update button on task lists.
  • Incident_btnGotoWorkSpace - Gives access to the Go To Workspace button on Task Search Module (Classic Only).


Global Admin Security

It is also important to note that Global Admin users will have full rights to View, Add and Edit tasks regardless of whether they are one of the principal users on the task or have any of the above security entities.

Giving users access to mass update tasks

The User must be in a Role with the Incident_btMassUpdate entity.

To give users access to mass update tasks:

  1. Determine the Roles to which the user is a member.
  2. Add Incident_btnMassUpdate to one of the user's roles or add the user to a role that already has that entity by following the Role Administration guidelines.
  3. Go to System AdminSecurity > Roles.
  4. Filter roles by Role Title, Users that are associated with the role, or Entity Name of the associated Security Entities.
  5. If a user needs to have access to a particular security entity, you can do one of the following:
    • Add the user to a role that already contains the required entity by filtering roles by targeted entity.
    • Add the security entity to a role that the user is already associated with by filtering roles.
  6. Add the appropriate View, Add, Edit, Delete, and Admin rights for the role.
  7. To see if a user is already in a role with a specific entity, filter the Roles by user and Entity.
  8. You can also use a wildcard when searching for roles. When setting search parameters, place a % symbol before your search string to make it a wildcard keyword search.  ex %Service Case





  



NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm