Many companies use Data Visions, and none of them can see another's data. The separation is built into how Data Visions stores and reaches data, not left to good behaviour.
Your records have their own database
Every workspace's business records (time cards, work orders, customers, invoices and everything else your modules keep) are stored in a database of their own. Another company's modules work in theirs. No screen, report or search reaches across from one to another.
Data Visions itself keeps a small amount of shared information, such as logins, workspace names and billing, in a separate platform database. Each request to it is tied to the workspace you're signed in to.
Everything is tied to your workspace
When you sign in, you open one workspace. Everything you do from then on runs in that workspace only:
- Modules read and write only your workspace's database.
- AI agents work for one workspace for the whole conversation. They can't be pointed at another company, even if asked.
- The Bridge on your own computers answers only your workspace.
- Files and photos are stored in storage set aside for your workspace.
If you belong to more than one workspace, switching moves you completely to the other one. See Switch workspace.
Who can see your data
- Your people, as far as their roles allow. See Users and roles: roles and permissions.
- Data Visions support, only when your Workspace Admin allows it. See Data Visions support access.
- Other workspaces, only what your Workspace Admin chooses to share with them, such as a module. See Workspace connections.
- Connected AI apps such as Claude or ChatGPT, only what you allow them, acting as you. See Security: AI connectors.
Good to know
- Separate doesn't mean on separate hardware. Your database is your own, but it runs in Data Visions' cloud alongside others, like most online services.