docs(permutive): update consent section

Author: AntonioGargaro

dev-docs/modules/permutiveRtdProvider.md

@@ -69,39 +69,11 @@ as well as enabling settings for specific use cases mentioned above (e.g. acbidd
 | params.acBidders       | String[]             | An array of bidder codes to share cohorts with in certain versions of Prebid, see below                         | `[]`               |
 | params.maxSegs         | Integer              | Maximum number of cohorts to be included in either the `permutive` or `p_standard` key-value. | `500`              |
 
-### Context
+### Consent
 
-While Permutive is listed as a TCF vendor (ID: 361), Permutive does not obtain consent directly from the TCF. As we act as a processor on behalf of our publishers consent is given to the Permutive SDK by the publisher, not by the [GDPR Consent Management Module](/dev-docs/modules/consentManagement.html).
+If you are also using the [TCF Control Module](/dev-docs/modules/tcfControl.html), by default Permutive will not be blocked as it will rely on the publisher's consent signals to read from storage. If you choose to gate Permutive on their vendor id, 361, should add their vendor ID to your CMP and pass `enforceVendorConsent` to the module's configuration.
 
-This means that if GDPR enforcement is configured within the Permutive SDK _and_ the user consent isn’t given for Permutive to fire, no cohorts will populate.
-
-If you are also using the [TCF Control Module](/dev-docs/modules/tcfControl.html), in order to prevent Permutive from being blocked, it needs to be labeled within the Vendor Exceptions.
-
-### Instructions
-
-{% include dev-docs/vendor-exception.md gvlId="361" %}
-
-1. Publisher enables rules within Prebid.js configuration. 
-2. Label Permutive as an exception, as shown below.
-
-```javascript
-[
-  {
-    purpose: 'storage',
-    enforcePurpose: true,
-    enforceVendor: true,
-    vendorExceptions: ["permutive"]
-  },
-  {
-    purpose: 'basicAds',
-    enforcePurpose: true,
-    enforceVendor: true,
-    vendorExceptions: []
-  }
-]
-```
-
-Before making any updates to this configuration, please ensure that this approach aligns with internal policies and current regulations regarding consent.
+Before making any updates to your consent configuration, please ensure that your approach aligns with internal policies and current regulations regarding consent.
 
 ## Cohort Activation with Permutive RTD Module
 

dev-docs/modules/userid-submodules/permutiveIdentityManagerIdSystem.md

@@ -63,3 +63,10 @@ identities from the SDK directly if/when this happens.
 
 This value should be set to a value smaller than the `auctionDelay` set on the `userSync` configuration object, since
 there is no point waiting longer than this as the auction will already have been triggered.
+
+### Consent
+
+If you are also using the [TCF Control Module](/dev-docs/modules/tcfControl.html), by default Permutive will not be blocked as it will rely on the publisher's consent signals to read from storage. If you choose to gate Permutive on their vendor id, 361, should add their vendor ID to your CMP and pass `enforceVendorConsent` to the module's configuration.
+
+Before making any updates to your consent configuration, please ensure that your approach aligns with internal policies and current regulations regarding consent.
+