add consent mgmt to sidenav, redirects

Author: forstisabella

src/_data/sidenav/main.yml

@@ -499,6 +499,16 @@ sections:
       title: Complying With GDPR
     - path: /privacy/user-deletion-and-suppression
       title: User Deletion and Suppression
+  - section_title: Consent Management
+    slug: privacy/consent-management
+    expanded: true
+    section:
+    - path: /privacy/consent-management
+      title: Consent Management Overview
+    - path: /privacy/consent-management/consent-in-segment-connections
+      title: Consent in Segment Connections
+    - path: /privacy/consent-management/configure-consent-management
+      title: Configure Consent Management
   - path: /privacy/account-deletion
     title: Account & Data Deletion
   - path: /privacy/hipaa-eligible-segment

src/privacy/configure-consent-management.md renamed to src/privacy/consent-management/configure-consent-management.md

@@ -3,7 +3,7 @@ title: Configure Consent Management
 related:
   - "/privacy/consent-management/"
   - "/privacy/consent-in-segment-connections/"
-  - "/privacy/consent-in-unify/"
+redirect_from: "/privacy/configure-consent-management"
 ---
 
 After setting up your consent management platform (CMP), you can enforce the consent collected from your users by adding the [consent object](/docs/privacy/consent-in-segment-connections/#consent-object) to your events. 

src/privacy/consent-in-segment-connections.md renamed to src/privacy/consent-management/consent-in-segment-connections.md

@@ -3,6 +3,7 @@ title: Consent in Segment Connections
 related:
   - "/privacy/consent-management/"
   - "/privacy/configure-consent-management/"
+redirect_from: "/privacy/consent-in-segment-connections"
 ---
 
 Segment Connections users can add the [consent object](#consent-object) to their sources to stamp events with the end user consent preferences captured by your consent management platform (CMP) and send them downstream to destinations in categories that an end user consented to share data with. Events without the consent object continue to flow to destinations without consent enforcement. 

src/privacy/consent-in-unify.md renamed to src/privacy/consent-management/consent-in-unify.md

@@ -5,14 +5,12 @@ related:
   - "/privacy/consent-in-segment-connections/"
   - "/privacy/consent-in-unify/"
 ---
-> info "Consent Management is in public beta"
-> This means that Consent Management features are in active development, and some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
 
 When an end user visits your web or mobile app, they set **consent preferences**, or make decisions about the types of data they want you to collect, use, and share. These consent preferences are typically presented as a set list of categories that describe how your company intends to use that data. Some common categories include personalization, advertising, and site performance.
 
 Segment integrates with your commercial third-party or bespoke consent management platform (CMP) that captures an end user's consent preferences and enforces those preferences by only routing events to the categories consented to by an end user.
 
-![Diagram outlining information flowing from an end user to Segment destinations](/docs/privacy/images/consent-overview.png)
+![Diagram outlining information flowing from an end user to Segment destinations](/../images/consent-overview.png)
 
 After a user sets their consent preferences on your web or mobile app, Segment requires you to add the [consent object](/docs/privacy/consent-in-segment-connections/#consent-object) to all events. If you are using OneTrust, Segment provides a wrapper for your web and mobile libraries that can add the consent object to your events. If you are using another CMP, you are required to add the consent object to your events by either creating your own wrapper or using another mechanism. For more information, see the [Configure Consent Management documentation](/docs/privacy/configure-consent-management/#step-2-integrating-your-cmp-with-segment).