Hi @nembee! After discussing more with the engineering team, one workaround would be to add the mc_admin role if your user needs access all areas of Mission Control Preview. We found that Mission Control Preview does not handle the admin_all_objects capability consistently, resulting in the ability to create an incident but not list or view it. A workaround to allow both creation and viewing is to assign the mc_admin role, or as I mentioned previously, the mc_analyst_all_edit role (as appropriate) to the user. We will fix this issue in a future release. Thank you for your patience! ... View more

Thank you for the screenshot! My hypothesis is that your AD group does not contain the correct permissions to create or view a Mission Control incident. Here's the link to our permissions documentation: https://docs.splunk.com/Documentation/MC/Preview/Detect/Permissions   If you have access to the AD group (for example LDAP), could you try adding the correct permission to your user?  Here's more documentation for managing groups in LDAP: https://docs.splunk.com/Documentation/Splunk/9.0.1/Security/MapLDAPgroupstoSplunkroles    If you want to create and view an incident with the incident type "Default" the user would at least need the role permission "mc_analyst_edit_default."   Please let me know if that helps to solve anything! Thank you. ... View more

Thanks for the update! @nembee  If there's any more user config or AD information you could send, screenshots are helpful, please mention here or email us at: missioncontrol-preview@splunk.com Edit: I'm curious, does the incident creation work if you leave the "Owner" field unassigned?  We are looking into this right now!  ... View more

Hi @nembee  We haven't heard back from you in a week. Please let us know if you can answer the above questions. We would love to know more details so we can investigate on our end. Thanks! ... View more