How do I allow non Admin role users to add/edit related SLA's and Contract CI's within Service Contracts (Service Level Management Add-On)

[mark_leonard]

Hi

I'm sure this is a fairly simple one, but I can't for the life of me work it out...

We heavily use the Service Level Management functionality within our instance, however I would like non Admin role users to create/modify Service Contracts and associate the relevant SLA's and Contract CI's.

It's simple enough to grant users the ability to create Service Contracts as they just require the ITIL Admin role; however this role does not allow them to be able to select related SLA's or Contract CI's once the Service Contract has been created. Once created, the Related Lists section at the bottom of the Service Contract form for both SLA and Contract CI does not allow an ITIL Admin user to create/edit them.

I've established that this functionality is only available to users with the Admin role. There are a number of users in our environment that should be able to create new contracts, however I am not keen on granting them admin rights to the system.

Could anyone please advise if there is a simple solution, perhaps an ACL that might point me in the right direction?

Many thanks in advance.

Mark

[Mike Allen]

You would have to put write access to each of those tables for the appropriate role.

[mark_leonard]

Thanks for your response. If we take the CMDB table, the ITIL role already has write access to it, however they cannot select a related config item within the Service Contract. If we look up an existing Service Contract that has already had Config Items associated to it by an Admin, the related are also not visible, with error message:

Number of rows removed from this list by Security constraints: 1

[Michael Fry1]

There are an asset & contract_manager roles available for the contract part of your problem. However, I would recommend you limit those that can manage SLA's to admins.

[mark_leonard]

Thanks for getting back to me, however I have unfortunately assigned these roles to effect. I actually tested in our dev environment and assigned every role except Admin and Security Admin to a test user, and the issue was still there. It seems you need Admin role.