Jim Posted September 17 Posted September 17 I have a service where we auto log service requests from a script to replace our end of life assets, we also have an incident catalog item within this service in case an incident occurs with the new asset that we give a limited time of access to the users affected until normal support resumes, This works well in the flows and auto adds the groups etc that give this access, I am just going through a test and I'm not at the point of having access to these support items, but I can still see the service in portal. see below it shows no catalog items but will show a request when one is logged, My issue with this is that I don't want this exposed at all until they have a certain group, but the service request to replace the assets does need to allow all users to be selected as the customer, so obviously they have a hidden access to this item This does not seem to be the right behaviour at all, and without creating separate services I think we are just going to have to put up with it for now
Steve Giller Posted September 17 Posted September 17 Have you remember to turn this off in the Service Portfolio?
Jim Posted September 17 Author Posted September 17 ah but this needs to be on so they can access the asset replacement request, they just don't get to log it, only the script logs them, but they will need portal access to update it
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now