>Hi,
>
>I am writing a quote to a large company that needs a multi-site license of my software. Basically, if this goes through, they will use the software at different facilities. There will just ONE server and ONE database. Each table of the database has a column SITE_NO so that users of each facility can add/edit/view only their records. I think in some of the technical speaks they use the term "sandboxed" indicating separation of the data by a site. The managers I am dealing with are not very computer technical. Can I still use the term "sandboxed" or is there a better way to describe how the data will be separated by a facility?

"Sandbox" is a term used in the security industry: https://en.wikipedia.org/wiki/Sandbox_%28computer_security%29

You might also run into terms such as "isolation" or even "firewalling" but in your situation I'd be reluctant to use any of them, because from a technical POV they aren't true.

The closest I can think of is "access control". Even with this you may need to be careful. For example, what if Site 2 gets a valid user name/password combination from Site 1? Should Site 2 be able to log on with those credentials and view Site 1's data? Or do they want to make it so no matter what credentials Site 2 uses, they can only ever see their own data?

If they're using terms like "sandbox" they may want greater isolation/security than you may be able to easily provide with your current scheme. I suggest asking them how much they actually need vs. what they think they want. Then, be upfront in your quote about what you're providing, and its limitations, if any.