Home > Designing and creating databases > Protecting databases

Protecting databases

You can restrict what users can see and do in a database file by defining accounts and privilege sets. For example, you can:

•	Password-protect a file

•	Allow data entry only

•	Allow browsing but prohibit database changes

•	Restrict access to specific tables, records, fields, and layouts

•	Give certain users full access to a file, which allows them to define tables, fields, relationships, data sources, and access privileges for other users

You can also control access to a file’s schema (including its tables, layouts, scripts, and value lists).

Although your operating system includes file security features, you should use FileMaker Pro access privileges as the fundamental way to control access to and protect the security of your database files.

It’s especially important to protect FileMaker Pro files that are shared with other FileMaker Pro users via the FileMaker Network, with web users via FileMaker WebDirect, and with ODBC/JDBC clients. These shared files are more vulnerable because they may be more widely available over your network.

Note  If you have FileMaker Pro Advanced, you can encrypt database files to protect them while they are being stored on disk. See Encrypting database files (FileMaker Pro Advanced).