You can't prevent a copy of the whole file.
You should also read the popup message when you add the password security.
You cannot stop a file from being forwarded, copied to memory stick, uploaded or otherwise shared. But if the file is protected with DRM the shared copy is useless. This is a big ticket item requiring a 24/7 server to check privileges, and an administrator, the cost of these two small compared to the cost of the DRM itself. See Adobe LiveCycle Rights Management. This can also protect other kinds of file, but its adoption within a company would be a high level decision; I recommend getting expert consultancy to advice on an overall strategy. If it's a question of just protecting one file from sharing, not viable. (And indeed be sure to read, and believe, the warning message).
Use self-signed "Certificate Security" instead of "Password Security".
1.a. You will need to create your own self-signed certificate (From the Menu: Edit/Preferences/Signatures/Identities & Trusted Certificate/More/Add ID).
1.b. For each person you want to have the ability to read/print/etc... have them use Reader to similarly create a Self-Signed Certificate. They will need to export their public key and forward to you ( in the same window where they created their ID's, select ID, Click "Certificate Details" from the menu bar, - Certificate Viewer appears; in the Summary tab, click the "Export" button). FDF exchange formats are easy to work with.
2.a. Open your document, and change security settings to "Certificate Security". Don't need to do anything in the "General settings" of the Certificate Security Settings window, except select next to get to the "select recipients" page. Browse to and then open each FDF file you have received and saved. This will add permission for each certificate holder to the document.
2.b. MAKE SURE YOU ADD YOUR CERTIFICATE - or you will not be able to open the document yourself here after.
2.c. For each recipient you have added, use the permissions button to change the user's rights (read only / print, etc...) by changing the restrictions and permissions.
2.d. MAKE SURE YOU DO NOT ADD ANY RESTRICTIONS for your certificate - or you will not be able to edit the document here after.
3. Save the document, and circulate it.
Anyone for whom you have included their certificate (as above); they will be able to open the document. Everyone else - will get a message stating the document is encrypted and they have no rights to access.
Downside in doing this: You have to manage all the certificates manually.
Live Cycle does this behind the scenes (+more) but with great co$t.
If I have my document on my server, with all this security on it- can they still email it and open elsewhere? Or is there a way to prevent copy/paste or emailing to other locations. I just want them to be able to view it and not email it, print, or copy the document.
I'm looking into LiveCycle, but want to know if there is a way to do it without that.
You can't prevent copy/paste or emailing like any other file.
A note on LiveCycle: it is a family of different products, you need to be thinking of the full product name or you will end up looking at the wrong features/product.