SkieWhat does a device model that has not been reviewed get?
A model that has not been reviewed can still be provisioned and managed with Skie's core protections, but its built-in apps are left alone. Without a profile, Skie does not hide or suspend the maker's own apps. Reviewing and publishing the model gives it the full app control.
Skie does not block you from using a model because nobody has looked at it yet. A device of an unreviewed model is provisioned, becomes managed, receives signed policy, reports compliance and enforces the hardening switches that do not depend on the model's app set.
What is different is the treatment of built-in apps. Without a profile Skie does not know which of the maker's apps are safe to hide, so it leaves them alone. This is the cautious choice, because hiding an essential system app by mistake could break the dialler or the settings screen. The install guard still removes apps that are installed after enrolment and not allowed, and the baseline snapshot of what was present at setup is still taken.
So the visible effect is that built-in extras from the maker, such as a theme store or an extra browser from that brand, may remain visible. Skie's always-blocked list of alternative browsers, VPN apps and proxy apps applies regardless, along with the Chrome rules.
The readiness gate tells you the model is unreviewed and links to the add a model wizard. If you are provisioning a single test device, you can go ahead. If you are about to do a class, review the model first so every device gets the full treatment.
Practical tip: provision the unreviewed model as your master device, test it, then run the wizard and publish. See the wizard and what a model profile contains.
- Can still be provisioned and managed
- Built-in maker apps are left alone
- Install guard and baseline still work
- Review and publish for full app control