> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/customizations/updating-company-compatibility.md).

# Updating Company Compatibility

Why some features stay off until your company is updated, what to do before you update, and how to run the update from Settings → Advanced.

Some new features change how your company's data is stored, and an older version of ScribeWare can't work with that data. Those features stay off until your **company** is updated, so nobody on an old version is left unable to open a report.

This is one setting for the whole company, not one per device. Updating the app gets a device ready. Updating your company's compatibility is what turns the features on.

## What the 7.2 Update Turns On

Everything marked **(beta)** in the [Smart Tags](https://docs.scribeware.com/customizations/smart-tags.md), [Smart Summaries](https://docs.scribeware.com/customizations/smart-summaries.md) and [Tables](https://docs.scribeware.com/customizations/tables.md) pages stays off until your company has taken the 7.2 update. It's a beta: the features work, but expect names and layouts to keep changing.

The same update also moves agents and alt text option lists to a new form of storage. Settings → Advanced lists what your company will get.

## Before You Update

{% hint style="danger" %}
**This can't be undone.** Once your company is updated, every device in it must run a compatible version of ScribeWare, including your team's phones and tablets. A device that's behind shows *An update is required before continuing!* and can't open anything until it has been updated.
{% endhint %}

1. **Update ScribeWare on every device**, desktop and mobile.
2. **Check the device list.** Settings → Advanced names each device that will need updating, under *The following devices will need to be updated*, with the version it's on. It lists devices used in the last 30 days, so a laptop that's been in a drawer won't appear.
3. **Tell your team.** The Advanced page isn't limited to the account owner, so agree who presses the button and when.

## How to Update

Do this on the desktop app. The mobile app doesn't have this setting.

1. Open **Settings → Advanced**, under *System*.
2. Read the list under *There are updates available on your account*.
3. Click **Update account compatibility**.
4. Read the warning and confirm.

When there's nothing left to update, the page says *Your account is compatible the newest versions of ScribeWare!*

## If the Features Don't Appear

If Settings → Advanced says your account is compatible but the (beta) features aren't there, your desktop app is probably behind. The page only offers updates that the app you're running knows about, so update ScribeWare, then open Settings → Advanced again.

## Updates ScribeWare Runs for You

You may never need the button. Every night ScribeWare checks whether a company can move forward, and updates it automatically when both of these are true:

* ScribeWare has made the new version the minimum for everyone.
* Every device your company has used in the last two weeks is already on a compatible version.

Pressing the button is how you get a new feature before then.

## Installing and Sharing Templates

A template that uses (beta) smart tag features can't be installed or copied into a company that hasn't taken the update. ScribeWare names the features the template uses, and it can be installed once your company is updated.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scribeware.com/customizations/updating-company-compatibility.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
