Permissions = Asset User
You then have to ensure the group they belong to has a "Supported By" relationship type on the CI under the "People Tab".
That combination will give them update permissions to the CI's in question.
Thanks for your response, so we have do as such granted a user the Asset User permission and aligned the "Supported By" between a series of CI's.
However when the user attempts to create a relationship between an Application CI & a Server CI. They appear to get an error message which states that "they do not have write access" repeated 3 times in the same window dialogue box that appears.
But it appears the issue is resolved when Asset Admin permissions are applied, but we do not wish to give this user this high level of access.
What kind of relationship? And I'm assuming they have support by role on both CI's in question?
2 of 2 people found this helpful
Based on the permission definition from BMC:
"If a user belongs to a support group that is related to a CI using one of the defined roles then the user will have access to modify that CI record with the exception of the CI to CI relationships"
So, you would have to give them asset admin or customize the workflow that is preventing the action from happening.
Thanks Ryan that been really helpful so only those with an Asset Admin permission level can create Impact / Dependency relationships between CI's ?