CCPulse Access Rights

NICE CXone API & Integrations
1

hello,

I want to restrict user access within CCPulse - is this done within the security tab of persons in CME?

I thought the ranks tab in the same record would do this (ie user/administrator) but a ‘user’ can still create new views for example.

Thanks,

WA

2

Hi,

IMHO ranks are the only way you can restrict the user as CCPulse+ configuration object like templates, views, workspaces are not stored in Genesys configuration. So permissions won’t help you here.

What are you trying to achieve?

R.

2 Likes
3

You can create a special access group and then put all your restricted users in there.

Then depending on what you want to filter, edit the object properties and remove the access of that newly created Access Group ( No access). But make sure the newly created Access Group has read and execute access to those objects you want it to have.

For example:

You want these restricted users don’t see specific DNs: go to that DN and edit the properties. Change the access and remove the access of your newly created access group. If you have regrouped the DNs under a folder just edit the folder properties then and it will affect all the DNs in that folder.

You can do the same for any object instead of DNs. i. e. Places, RPs, even the whole switch

Hope that helps,

Cheers,

4

I want to restrict a users access to modify or delete a workspace or workspace view.

At the moment all the wizard options are blocked but the user can still accidently delete a view or save it afterwards.

How do I prevent this from happening?

Thanks,

WA

5

Rene is right this is outside of Genesys, you need to look at setting permissions on the directory that holds the .stg on the PC. (Group policies?)

6

Hi,

We have given read only rights to all users except ourselves to the network path that the stg ccpulse files are stored e.g f/ genesys/ ccpulse/ ccpulse views. This is the only way we found to do this.

1 Like
7

Hi,

As already mentioned in previous post(s) the only way how you can restrict the users from changing workspace is using Windows security/permissions. Simply make all CCPulse+ files (templates, workspaces etc.) read-only and that’s it. Users still be able to close existing view(s) or create a new one based on predefined templates but these changes will be lost once CCPulse+ application is closed.

R.

2 Likes