> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/mobile-app/general-mobile-app/synchronise-the-mobile-app.md).

# Synchronise the mobile app

Synchronising updates the app with the latest data from the **BackOffice**.

Use it when new work orders, changed settings, or updated customer data should appear on the device.

### When to synchronise

Synchronise the app when:

* a planner has assigned or changed work orders
* an administrator changed app settings
* forms, items, customers, or objects were updated
* the employee does not see the expected data

{% hint style="warning" %}
After app settings change, employees must synchronise before the new setup takes effect.
{% endhint %}

### Synchronise the app

{% stepper %}
{% step %}

### Open the app

Open the OutSmart app on the device.
{% endstep %}

{% step %}

### Start synchronisation

Use the available sync action in the app.

Wait until the refresh is complete.
{% endstep %}

{% step %}

### Check the updated data

Open the work order overview, customer data, or other updated sections.
{% endstep %}

{% step %}

### Restart the app if needed

If settings were changed, close and reopen the app after synchronising.
{% endstep %}
{% endstepper %}

### What synchronisation updates

Depending on your app settings, synchronisation can update:

* work orders and planning changes
* customers, objects, and items
* forms and related app content
* app permissions and feature settings

### If synchronisation does not solve it

Check these points:

* the device has an internet connection
* the employee is signed in with the correct account
* the data is allowed by **Device policies and settings**
* the app has been closed and reopened after the sync

### FAQ

<details>

<summary>Do employees need internet to synchronise?</summary>

Yes. Synchronisation requires an internet connection.

</details>

<details>

<summary>Does synchronising send completed work orders too?</summary>

Yes, if the device has a connection and the employee sends the work order.

</details>

<details>

<summary>Why do settings still not appear after a sync?</summary>

The employee may need to close and reopen the app.

The app settings may also be different for that employee.

</details>

### Related topics

* [What is the OutSmart mobile app?](/mobile-app/general-mobile-app/what-is-the-outsmart-mobile-app.md)
* [Complete a work order in the mobile app](/mobile-app/general-mobile-app/complete-a-work-order.md)
* [Use the mobile app offline](/mobile-app/general-mobile-app/use-the-mobile-app-offline.md)
* [Replace or reconnect a mobile device](/mobile-app/general-mobile-app/replace-or-reconnect-a-mobile-device.md)
* [Device policies and settings](/mobile-app/general-mobile-app/device-policies-and-settings.md)
* [Paired devices](/mobile-app/general-mobile-app/paired-devices.md)


---

# 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://knowledge.out-smart.com/mobile-app/general-mobile-app/synchronise-the-mobile-app.md?ask=<question>&goal=<endgoal>
```

`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.