- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2015 02:50 PM
Hi All,
How can i give a user access to only Incidents(Create,Read,Update) and no permissions for Changes,Problems. and also he should not delete any incidents.
I have tried by creating a new role and a new ACL "Incident* write" but its not giving the permissions for all the fields, still the user is able to see only few fields9assignment_group,summary,description). How to create ACL's to give access only to Incidents instead of giving ITIL role.
Thanks,
Sry
Solved! Go to Solution.
- Labels:
-
Incident Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2015 04:39 PM
"I have only one issue, when the user "create new" incident he is not able to view all the fields on incident table".-- If ACL set correctly and updated the incident query BR..next may be to check is the view . Please check the view.[self service view.. Default ] etc.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2015 10:40 PM
Hi Sry,
You should not remove the existing "ITIL" role from the application menu/ACL's. The reason being this will break the existing functionality.
In your case please create a custom role and then adjust the create/read/write/delete ACL's on incident table as per your req. Once done then you have to assign the custom role to the application menu/modules too.
Please let me know if you have any questions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2015 09:45 AM
Hi Pradeep,
thank you very much for prompt reply. i did create a custom role and incident* create/read/write ACLs for this role on Incident table. and added this custom role at application level, but still the user is able to view only few fields while creating incidents like assignment group,short_description,description. I am guessing there are other ACLs conflicting with this thats why the user not able to view all the fields. Does creating create/read/write acls on incident for all fields(*) allow the user to write on all fields?
thanks,
sry

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2015 09:49 AM
Hi,
Thanks for the update. There is also a OOB BR "incident query" which you have to adjust as per your req.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2015 12:54 PM
hi pradeep,
i have already changed this business rule by adding custom role. I have only one issue, when the user "create new" incident he is not able to view all the fields on incident table. ACL(incident *) of operation CREATE is not working. i tried debugging too, there it says the role is TRUE. there are no other CREATE acls on this table. i even tried to create an acl on TASK* table, still not working. I want the users who have the custom role to be able to see all the fields on incident table while they create a new incident.
thanks,
sry