Snap for 6676900 from ce91126d6b57ac7e24e14cae9161ec7cb8b50275 to rvc-release
Change-Id: I1ef8d3bd76c12251fb27f51381df78d28f0ed677
diff --git a/3_software/3_9_device-administration.md b/3_software/3_9_device-administration.md
index 714005f..983b125 100644
--- a/3_software/3_9_device-administration.md
+++ b/3_software/3_9_device-administration.md
@@ -120,9 +120,13 @@
applicable for a device with multiple users enabled
(see [section 9.5](#9_5_multi-user_support)), even though the managed profile
is not counted as another user in addition to the primary user.
-* [C-1-10] MUST support the ability to specify a separate lock screen meeting
+
+If device implementations declare `android.software.managed_users` and
+`android.software.secure_lock_screen`, they:
+
+* [C-2-1] MUST support the ability to specify a separate lock screen meeting
the following requirements to grant access to apps running in a managed
- profile.
+ profile only.
* Device implementations MUST honor the
[`DevicePolicyManager.ACTION_SET_NEW_PASSWORD`](https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_SET_NEW_PASSWORD)
intent and show an interface to configure a separate lock screen
