### Problem to solve > As a User of Confidential Issues, > > I need to organize them into an Epic that is also confidential, > > So that I can easily organize shared work and provide the proper context and information at the Epic level ### Intended users * [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager) * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) * [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst) ### Further details Currently we provide confidential issues, but not epics. For scenarios where multiple confidential issues need to be tracked together, or are closely related, we should allow them to be grouped in a confidential epic. ### Solution New epic popup will include a checkbox for making the epic confidential. A Help icon will include a tooltip with the verbiage: This epic and its child elements will only be visible to team members with at minimum Reporter access.  Right sidebar will include the same Confidentiality toggle as issues.  For this first iteration, Confidential Epics will only be able to contain confidential Issues and other confidential children Epics. Attempting to add a public issue or epic to a Confidential should provide an error along the lines of : > *Confidential Epics can only contain Confidential Issues and Epics* <details> ### Proposal Provide a confidential Epic, just like we currently do with Issues. * Ask During Epic Creation if the new Epic should be confidential, similar to:  </details>