> For the complete documentation index, see [llms.txt](https://docs.secure-contacts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secure-contacts.com/enduser-guide/step-3-onboard-sca-on-your-device.md).
# Android Enterprise - Userguide
The following steps show you, how to onboard SCA on your device.\
We recommend using an Android with the latest OS version.
{% hint style="success" %}
SCA needs to be deployed via Intune and present on your device as discribed [here](/documentation/deployment-sca/android-app-installation.md)
{% endhint %}
3.1 - Open "SecContacts" with workprofile on your Android test-device
3.2 - Accept terms and conditions and ***Continue***\
3.3 - Next step to select ***Login***\
3.4 - Select your Account\
3.10 - SCA will login to Contacts
3.12 - At this screen, select **activate now**
\
\
3.14 - Select **ENABLE CALLER IDENTIFICATION**
3.14 - Choose *SecContacts* and confirm with **Set as default**
3.14 - Choose **Allow** for this prompt
3.15 - This indicated that Caller Identification is enabled
3.16 - Now SCA is fully onboarded!
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.secure-contacts.com/enduser-guide/step-3-onboard-sca-on-your-device.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.