- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2019 06:48 AM
Just upgraded a test instance to New York release (from London) and I notice the itil role now contain agent_workspace_user role.
Is there a reason why I can't remove the agent_workspace_user role from itil?
Every time I remove it form the slushbucket it get back there.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2019 07:21 AM
Hi,
This looks like a scope issue. I was able to remove the agent_workspace_user role form itil but had to go to the Contained Role record itself (went from related list of itil), change the scope to ITSM Workspace and use the Delete button on this form.
You will not do it on ITIL role related list because as soon as you will change the scope the New and Edit button will disappear due to a different scope.
Best regards,
Łukasz

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2019 07:47 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2019 07:48 AM
wouldn't this permanently delete the role not just remove it from ITIL.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2019 07:46 AM
Thanks for the info, this worked when deleting the actual contined role record.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2019 07:46 AM
I got it to work by doing the following.
1. Opened the ITIL Role.
2. Clicked edit under Contains Roles.
3. Switched to ITSM Workspace app.
4. Removed the role from she slush bucket.
5. Clicked save
6. set myself back to global application
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2019 07:47 AM
I assume this is a better approach than going to the sys_user_role_contains table and remove it from there.