Remove Schema Defaults documentation

Schema Defaults was a beta feature that was partiall rolled out and
is slated to be EOL-ed soon.  We are removing the docs now so that
we no longer get requests from customers to activate this feature.

PROT-2959

Author: Steve van Loben Sels

src/connections/destination-data-control.md

@@ -38,109 +38,3 @@ If you no longer want to track an event, you can either remove it from your code
 ![](/docs/protocols/images/event-filters.png)
 
 Once you block an event in Segment, we'll stop forwarding it to all of your Destinations, including your warehouses. You can remove it from your code at your leisure. In addition to blocking track calls, Business plan customers can block all Page and Screen calls, as well as Identify traits and Group properties. 
-
----
-
-
-
-## How do I prevent new data from being allowed by default?
-
-If you've solidified your tracking plan and don't want any rogue events finding their way to your warehouses and end tools, we recommend activating our new feature, **Schema Defaults**. When you lock your schema, or set your Schema Defaults to "Block," Segment will automatically prevent these calls from being sent downstream. You can activate this for new events—including `track`, `page`, and `screen` calls—or for new `identify` traits and `group` properties. 
-
-Locking your schema only takes a few seconds and will protect your data from un-spec'd events or tracking errors. To configure your Schema Defaults, go to your Schema page, and then select "General" from the left-hand navigation.
-
-![](images/schema-defaults.png)
-
-
-**Overview of Schema Default Settings**
-
-**Default**
-
-**Allow**
-
-**Block**
-
-**New Events**
-
-All new events will be allowed in Segment and sent to all Destinations.
-
-No new events will be allowed in Segment or sent to your Destinations. Any event that is already being tracked and part of your Schema will not be impacted.
-
-**New Group Properties**
-
-All new group properties will be allowed in Segment and sent to all Destinations.
-
-No new group properties will be allowed in Segment or sent to your Destinations.
-
-**New Identify Traits**
-
-All new identify traits will be allowed in Segment and sent to all Destinations.
-
-No new identify traits will be allowed in Segment or sent to your Destinations.
-
-**Example: Order Completed**
-
-For example, if you set your Schema Defaults for New Events to "Block," and a new event, `Order Completed`, is tracked, Segment will automatically block the event and it will not be sent to your warehouse or downstream tools. The event will continue to be blocked until you actively choose to allow it.
-
-You will need to upgrade to the latest [iOS](/docs/connections/sources/catalog/libraries/mobile/ios/#install-the-sdk) and/or [Android](/docs/connections/sources/catalog/libraries/mobile/android/#step-1-install-the-library) SDKs for Schema Defaults to apply to events sent from mobile sources. 
-
-## **What is considered a "new" event?**
-
-New events refer to events that have not previously been sent to a given Source. Let's say you've only sent the following events from your Javascript source:
-
-*   `Products Searched`
-
-*   `Product List Viewed`
-
-*   `Product List Filtered`
-
-
-Your Schema Default setting will not have any impact on these three events because they are not considered new. You can manually block them, but your Schema Default setting will not change the status of these events. 
-
-Here's what will happen the first time a new event, `Promotion Viewed`, is sent to this Source:
-
-*   **Schema Default Set to Allow:** `Promotion Viewed` will be "allowed," which means the event will be sent to all enabled Destinations.
-
-*   **Schema Default Set to Block:** `Promotion Viewed` will be "blocked," which means the event will not be sent to any Destinations.
-
-
-## **What happens to blocked events and properties? **
-
-When an event or property is blocked, the name of the event or property will be added to your Schema page, but no data will be tracked. By default, data from blocked events and properties is not recoverable. You can always re-enable the event or property if you want to begin tracking it going forward.
-
-If you're concerned about permanently discarding data from blocked events, you can use advanced settings to forward these events to a designated Source. From there, you can send your data to a separate S3 bucket or warehouse for further analysis. That way if you decide you _do_ want the data in your downstream tools, you can ask Segment to Replay the data into your server-side Destinations. If you choose to route blocked events, this will contribute to your MTU count. 
-
-**How do I forward blocked events?**
-
-First, you will want to create a new Source to receive data from blocked Events and Traits. This Source should only be configured to received blocked data, so make sure it isn't receiving data from anywhere else. We recommend creating a new "Javascript" source and naming it "Blocked Data from \[Source Name\]." 
-
-After you have created a new source, go to the Schema page for your primary Source and then select "General" from the left-hand navigation. Under "Advanced Settings," you will see two options:
-
-*   Block and discard: select this option if you want to permanently discard data from blocked Events and Traits.
-
-*   Forward: select this option if you would like to forward data from blocked Events and Traits to a separate source.
-
-
-Select "Forward," and then select the new Source you created to receive blocked data. **As a reminder, if you choose to route blocked events, this will contribute to your MTU count. **
-
-## **How am I charged for blocked events? **
-
-Your bill is based on the number of Monthly Tracked Users (MTU). MTUs are the number of identified and anonymous users that you track with Segment. We only count users once per month, even if they perform multiple actions across your site or app. In most cases, blocked events will have no impact on your MTU count. If you choose to route blocked events, this will contribute to your MTU count. 
-
-## **How do I configure notifications?**
-
-While protecting the integrity of your data is helpful, we also want to flag any blocked events for you, so you can make any needed changes in your code or approve a new event. Source notifications will alert you when a new event is blocked due to your Schema Defaults. You can view these notifications in the Activity Feed in the app or subscribe to email notifications. 
-
-You can view these notifications in the Activity Feed in the app or subscribe to email notifications. To subscribe to email notifications, go to your workspace settings, then click "Notification Settings," and subscribe to notifications for Sources by entering your email address and clicking "Save Changes." You can enter multiple email addresses separated by a comma.
-
-## **When should I lock my schema? **
-
-Whether you're just about to implement a new spec or you have been tracking the same events for years, Schema Defaults make it easy to protect your data and fix data quality issues.
-
-Here are a few signs you may be ready to lock your schema:
-
-*   You are concerned about developers implementing rogue events
-
-*   You want to actively approve which events are tracked and routed to your downstream Destinations
-
-*   You have created a tracking plan and want to use Segment to enforce it