diff --git a/docs/html/preview/behavior-changes.jd b/docs/html/preview/behavior-changes.jd
index cd4d27e9067f3..245fa883b05c7 100644
--- a/docs/html/preview/behavior-changes.jd
+++ b/docs/html/preview/behavior-changes.jd
@@ -18,7 +18,11 @@ page.image=images/cards/card-n-changes_2x.png
Background Optimizations
- Permissions Changes
+ Permissions Changes
+
+ - File System Permission Changes
+
+
Accessibility Improvements
- Screen Zoom
@@ -200,7 +204,52 @@ page.image=images/cards/card-n-changes_2x.png
+File system permission changes
+
+ In order to improve the security of private files, the private directory of
+ apps targeting Android N or higher has restricted access (0700). This prevents
+ leakage of metadata of private files, such as their size or existence. This
+ has multiple side effects:
+
+
+
+ -
+ Private files’ file permissions can no longer be relaxed by the owner, and
+ an attempt to do so using
+ {@link android.content.Context#MODE_WORLD_READABLE} and/or
+ {@link android.content.Context#MODE_WORLD_WRITEABLE}, will trigger a
+ {@link java.lang.SecurityException}.
+
+ -
+ Passing
file:// URIs outside the package domain may leave the
+ receiver with an unaccessible path. Therefore, attempts to pass a
+ file:// URI trigger a
+ FileUriExposedException. The recommended way to share the
+ content of a private file is using the {@link
+ android.support.v4.content.FileProvider}.
+
+ -
+ The {@link android.app.DownloadManager} can no longer share privately
+ stored files by filename. Legacy applications may end up with an
+ unaccessible path when accessing {@link
+ android.app.DownloadManager#COLUMN_LOCAL_FILENAME}. Apps targeting
+ Android N or higher trigger a {@link java.lang.SecurityException} when
+ attempting to access
+ {@link android.app.DownloadManager#COLUMN_LOCAL_FILENAME}.
+ Legacy applications that set the download location to a public location by
+ using
+ {@link
+ android.app.DownloadManager.Request#setDestinationInExternalFilesDir} or
+ {@link
+ android.app.DownloadManager.Request#setDestinationInExternalPublicDir}
+ can still access the path in
+ {@link android.app.DownloadManager#COLUMN_LOCAL_FILENAME}, however, this
+ method is strongly discouraged. The preferred way of accessing a file
+ exposed by the {@link android.app.DownloadManager} is using
+ {@link android.content.ContentResolver#openFileDescriptor}.
+
+
Accessibility Improvements