After changing some more permissions and also changing the status transitions permissions (which took me forever to figure out I needed to do), everything seems to be working when inheriting the ess_user role, which is fine by me. I'm still not sure why this is necessary, but I can live with it for now. ... View more

Hello @PrewinThomas, I went ahead and set the inheritance for ess_user, and now I can see the notables on Mission Control with a user with the custom role. Unfortunately, this doesn't fix the root issue, which I think is more in-line with what @livehybrid mentioned, because even granting additional permission to own notables I still get errors when assigning the notables. I would rather not inherit ess_analyst because it has permissions that I do not want to grant to this role. ... View more

Hey @livehybrid,  Thank you for the quick response! As far as I can see the permissions on lookups and knowledge objects owned by ES are shared globally with Read all, so I assume at least being able to get the notables populated in Mission Control should be happening, as I mentioned, searching in the notable index does return data (the role also has access to index=*). Anything specific I could check here? I am not sure if anything shows up in the internal indexes, regarding errors or whatnot. EDIT: I would also add that I attempt to clone ess_user, but that did not change the result. ... View more