PureEngage On-Premises

Discussion Thread View
Expand all | Collapse all

CCPulse/Pulse Access Restriction.

  • 1.  CCPulse/Pulse Access Restriction.

    Posted 12-10-2019 05:28
    Team,

    We are trying to create the following restriction in the access groups in pulse and ccpulse application.
    1. Groups using CCPulse/Pulse should be able to access only the objects (Agent and Queues) which is under them.
    2. They should not be able to create view for other objects in the environment.

    And i also studied about access groups in CME help, And we need to know about the Replace Permission Recursively and propagate option.

    And also please provide your helpful suggestion in this topic.

    And i will explain below the scenarios we tried.

    We created the new access group.
    We created the new agent. And ranked as ccpulse administrator. (For logging in CCPulse)
    And we moved the created new agent to the new access group.
    And we given the full controls to the access group. And automatically it enables the propagate option.
    And whether we need to give the Replace Permission Recursively option.
    Please provide your helpful feedback.

    Thanks,
    Anandapriyan.R




    Thanks,
    Anandapriyan.R
    #Reporting/Analytics

    ------------------------------
    Anandapriyan Ravichandran
    Pointel (formerly Touch Point)
    ------------------------------


  • 2.  RE: CCPulse/Pulse Access Restriction.

    Posted 12-12-2019 02:42
    Team,

    Please provide your helpful suggestion in this access for agent groups or access groups.


    Thanks,
    Anandapriyan.R

    ------------------------------
    Anandapriyan Ravichandran
    Pointel (formerly Touch Point)
    ------------------------------



  • 3.  RE: CCPulse/Pulse Access Restriction.

    Posted 12-12-2019 12:31
    You need to deny read access to the folders/objects you want to deny access to. There is no automatic propagation, well unless you left the checkbox enabled when doing the permissions modifications.

    ------------------------------
    Jorge Cornejo
    VS Telecom LTDA.
    ------------------------------



  • 4.  RE: CCPulse/Pulse Access Restriction.

    Posted 12-13-2019 07:23
    Team,

    Thanks for your helpful reply.  Now the role based control is working fine.
    Super pulse admins
    Pulse admins
    Users
    In Object based control, On the particular object properties, Under accessible objects --> It displays all the users. With the full permission, How can we give only permission to the particular user. All other permission should be removed.
    When we remove read access from default access groups like, Administrators,Users,Default. It throws error while saving. Please provide your helpful suggestion.

    Thanks,
    Anandapriyan.R

    ------------------------------
    Anandapriyan Ravichandran
    Pointel (formerly Touch Point)
    ------------------------------



  • 5.  RE: CCPulse/Pulse Access Restriction.

    Posted 12-18-2019 03:33
    Team,

    Can you please suggest the links or documents for setting the permission on object based controls for ccpulse and pulse.
    And in CCPulse application, i have used to login with the user which we added in the access groups.
    The application getting logged in. For all the users, And we can able to create the view.
    Can you please provide your valuable suggestion in the access restriction for object based and role based controls in CCPulse and pulse application.

    Thanks,
    Anandapriyan.R

    ------------------------------
    Anandapriyan Ravichandran
    Pointel (formerly Touch Point)
    ------------------------------



  • 6.  RE: CCPulse/Pulse Access Restriction.

    GENESYS
    Posted 12-19-2019 13:13
    https://docs.genesys.com/Documentation/EZP/latest/Deploy/UserAccess

    ------------------------------
    Olena Chapovska
    Genesys - Employees
    ------------------------------



  • 7.  RE: CCPulse/Pulse Access Restriction.

    GCAP Member
    Posted 01-06-2020 19:20
    Edited by Jason McLennan 01-06-2020 19:20
    Managing Object Based permissions within Genesys is not specific to CCPulse. At the end of the day it's very similar to how you might manage permissions on folders in a windows or *nix based world. But here's some tips.

    • Always use Access Groups to assign permissions to objects. While you can assign permissions on objects to individual users, it becomes a nightmare to audit.
    • Consider the folder structure for your objects. Ideally you want to be placing permissions on folders, not individual objects, and propagating those permissions. But be careful where you do propagate. If you apply propagating access at the tenant level, then you're effectively giving permission to everything under the tenant.
    • Don't use Replace Recursively. Plan your permissions properly and you wont need it. If you do use it, you may end up giving more permissions than you desired.
    • If you assign the None Permission to an access group (GA) or add an access group to the permissions of an object and remove all permissions (GAX) then any user whos a member of that access group will not have any access, even if they're a member of an access group that gives them other permissions. None overrides everything for that user.
    • Standard agents will generally only need Read access (or Read and Execute for apps) on most objects. They shouldnt need to change anything. Exceptions are if they're also an administrator, or thy should have Change access to their own Person object as your using WDE and saving their options to their annex.

    So looking at your CCPulse lets say your using Configuration Units (or Business Units), and we create a Business Unit Called BU1 and an Access Group called BU1_Users. You'd look to do something like the below:

    Give Read Accesss, not Propogating to:
    • Tenant
    • Business Unit Folder
    • Switch

    You'd then give read access, Propogating to:
    • BU1 Users folder
    • BU1 Agent Groups folder
    • BU1 Places folder
    • BU1 DN Groups Folder
    • BU1 Camapign/Calling List Folders
    • BU1 DN folders on the switches (extensions, VQs)



    They'll also generally need Read and Execute against the CCPulse applcation, Stat Servers and I think hosts these applications run on.
    Hopefully this points you in the right direction.
    Planning your folder structure and access groups (along with roles) up front rather than applying them haphazardly can save you a lot of trouble down the line.

    ------------------------------
    Jason McLennan
    Commonwealth Bank of Australia
    ------------------------------


  • 8.  RE: CCPulse/Pulse Access Restriction.

    Posted 01-07-2020 03:29
    Hi team,

    Thank you very much. For your useful and helpful reply.

    Thanks,
    Anandapriyan.R

    ------------------------------
    Anandapriyan Ravichandran
    Pointel (formerly Touch Point)
    ------------------------------