Orbit sends changes to open app screens without a manual refresh.

## Open screens receive changes

[Orbit's product overview](https://orbitapps.io/) describes real-time updates as changes that appear on every open screen. A reader does not need to reload the page to see an update.

For example, two dispatchers can keep the same repair request list open. When one dispatcher changes a request's status, the other needs to see the new status. The repair list and status are example app content, not built-in fields.

The useful result is that both dispatchers see the current request state. A successful edit in one window alone does not show whether another window received the change.

## Access rules still apply

Access checks matter for live updates as well as the initial page load. A customer who cannot read a request must not receive its details through an update.

In the repair example, dispatchers may need a shared request list. Customers may need access to only their own requests. These are different access rules for the same app.

[Authentication](/features/authentication) explains the difference between signing in and having permission to read a record. A private record must remain private both when a page opens and when data changes.

## Live updates and saved data are different checks

An update on another screen shows that the screen received a change. It does not, by itself, show that the record survives a later visit.

[Isolated Postgres database](/features/isolated-postgres-database) explains app storage. A saved-value check confirms that the status remains after the app reopens. A live-update check confirms that another open screen receives the change without a refresh.

## What a complete check covers

For the repair example, a complete check covers three results:

- Another dispatcher sees the changed status without refreshing.
- An excluded customer sees neither the request nor its changed details.
- The saved status remains after reopening the app.

[Review an app before launch](/guides/review-an-app-before-launch) covers app testing.