-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE REQUEST] Force security if device is not protected #4061
Labels
Branding / MDM
Estimation - 3 (M)
Feature request
p2-high
Escalation, on top of current planning, release blocker
Settings
Milestone
Comments
jesmrec
changed the title
[FEATURE REQUEST] Force passcode if device is not protected
[FEATURE REQUEST] Force security if device is not protected
Jun 6, 2023
jesmrec
added
the
p2-high
Escalation, on top of current planning, release blocker
label
Jun 12, 2023
3 tasks
3 tasks
The following scenarios to sum up
|
Other way:
i hope it's more clear now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Branding / MDM
Estimation - 3 (M)
Feature request
p2-high
Escalation, on top of current planning, release blocker
Settings
Passcode/Pattern are free to be enabled/disabled for users in
Settings
device_protection
(another name?).false
by default.false
status will have no effect on the apptrue
status will trigger new behaviourNew behaviour
lock_enforced
(check here how it works). This will have branding regards because0
value is forbidden.Add it to the MDM option set.
TASKS
PR
The text was updated successfully, but these errors were encountered: