Protecting databases with accounts and privilege sets

Contents > Protecting databases with accounts and privilege sets > Protecting databases with accounts and privilege sets

Protecting databases with accounts and privilege sets

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, file references, and access privileges for other users

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 Instant Web Publishing, and with ODBC/JDBC clients. These shared files are more vulnerable because they may be more widely available over your network.

More details about protecting databases with accounts and privilege sets

About protecting databases

Creating and managing accounts

Creating and managing privilege sets

Managing extended privileges

Opening protected files

Contents > Protecting databases with accounts and privilege sets > Protecting databases with accounts and privilege sets