User sees more that he should

Arnold_Tomašovský

Hello everyone,

I would like to ask you for a help...

I was asked to create a separated HelpDesk for a particular set of users. So I "mirrored" the existing setup (meaning, new queue, new Service/Request offerings, new Group, new User Role...) in SCSM to prepare the Cireson.

What is fine - they see in Cireson, what they should, no problem there. However they see even the "normal" Helpdesk which should be invisible for them.

Can you help me out, what did I miss? Is there an additional setup in permissions in Cireson?

Thanks a lot!

Arnie

David_Allen

If you just want to hide the view, you can change the group that has access see to view in the Navigation settings of the portal.

However, if you want to restrict them having access to the actual work items, you will need to update the user role or queue that the user is a member of, to ensure they only have access to the work items you need them to.  Also, make sure the user isn't a member of any other groups that may give more access than is required.

Access to portal views is all controlled in the portal, otherwise the portal gets all permissions from SCSM.

Hope that helps!

David_Allen

If you just want to hide the view, you can change the group that has access see to view in the Navigation settings of the portal.

However, if you want to restrict them having access to the actual work items, you will need to update the user role or queue that the user is a member of, to ensure they only have access to the work items you need them to.  Also, make sure the user isn't a member of any other groups that may give more access than is required.

Access to portal views is all controlled in the portal, otherwise the portal gets all permissions from SCSM.

Hope that helps!

Arnold_Tomašovský

Hi, many thanks for the feedback.

I have done all you stated, but it's not working anyway. It seems to me that there are some groups that interfere with each other. I will investigate.

Thanks a lot.

Conner_Wood

Security User Roles - Flaws exposed.

Arnold_Tomašovský

It was due to nested AD groups. Issue has been fixed and all is fine now. Thanks a ton for you help.