Connect Collabora Online to ownCloud Infinite Scale
Set up the WOPI connection between Collabora Online and ownCloud Infinite Scale, configure the right service URLs, and verify document edits save.
Windows applications often store their data and settings in an AppData folder, and each Windows user account has its own folder. It is a hidden folder so you will only see it if you display the files in the File Manager. So what is the AppData folder and how does it play the role? Let's find out through the following article.

Each user account has an AppData folder with its own content. This allows Windows programs to store multiple installation packages if one computer is used by more than one person. The AppData folder was introduced on Windows Vista and it is still used on Windows 10 , 8 and 7.
You will find the AppData folder of each user account in that user's catalog. For example, if the user is named An, you will find the application data folder at C: \ Users \ An \ AppData by default. You can enter this address into the address bar to view it or display hidden folders and browse the list of user accounts at C: \ Users \ NAME . (You can also type % APPDATA% in the address bar of File Explorer to go directly to the AppData \ Roaming folder ).
They are actually three directories in AppData and are different programs that store different types of settings. Open the AppData folder and you will see three folders: Local, LocalLow and Roanming .
The Roaming folder contains data that "follows" a user account from one computer to another if your computer is connected to a domain name with a roaming profile , often for important settings. For example, Firefox stores its user profile here, allowing bookmarks and other browsing data to "follow" you from one computer to another.
The Local folder contains data specified for a separate computer. It is never synchronized from one computer to another, even when you log into a domain. This data is usually assigned to a computer or contains too large files. Data can include either downloaded cache files or other large files or just settings that developers don't think they need to sync between computers.
If you are not connected to a domain, there is no difference between the Roaming and Local folders . They are all stored on your computer. However, application developers still divide different types of data between different directories.
The LocalLow folder is similar to the Local folder , but it is designed for "low integrity" applications to run with more restrictive security settings. For example, Internet Explorer when running in Protected Mode only has access to the LocalLow folder . The difference is not really important for your personal use, but some applications only need a folder to write because they do not have access to the Local folder.
If a program wants to have separate installation packages or files used by many people, it should use the ProgramData folder . ProgramData is known as the "all users" AppData folder in previous versions of Windows. For example, an antivirus application can keep scan logs and settings in ProgramData and share them with all users on the PC.
Most Windows users do not need to know the existence of this directory. That is why it is hidden by default. You don't need to back up an entire folder, though you might want to include it in a backup just so you have everything in case you need to restore it.
However, if you want to back up specific program settings or computer game archive files, you can do this by digging into the AppData folder, finding the program's directory, and copying Copy it to another location. You can then copy that folder to the same place on a new computer and the program will use the same settings.
Many programs provide a way to synchronize their data between computers, or at least export it. Very rarely do you have to dig into the AppData folder, but sometimes you can do that too.
Set up the WOPI connection between Collabora Online and ownCloud Infinite Scale, configure the right service URLs, and verify document edits save.
Prevent document exports in Collabora Online CODE by setting the WOPI DisableExport permission, then verify the host and editor enforce it.
Configure Nginx TLS termination, Collabora routes, and WebSocket headers, then test the public endpoints before opening real documents.
Trace a 10-minute CODE disconnect to its proxy, load balancer, or WebSocket path, then correct the timeout and verify the session stays connected.
Install the official Collabora Helm chart, configure WOPI access and ingress affinity, and verify the deployment without common setup mistakes.
Use browser requests, WOPI logs, and targeted proxy checks to find why Collabora opens a blank document—and choose a fix that fits the evidence.
Configure CODE Docker dictionaries and tag document passages correctly so English, French, and other supported languages receive the right spell-checking.
Adjust the per-view inactivity threshold in coolwsd and distinguish it from background-tab dimming, document unloading, autosave, and login expiration.
Stop scheduled CODE update checks, review optional remote services, and use outbound network controls without breaking document editing.
Enable secure document editing in Seafile by configuring Collabora’s discovery URL, HTTPS, and WOPI access for your deployment.