User manual

Protecting databases | 177
You may want to create an account for every individual who accesses a file, or
you may want to create a small number of accounts that are shared among
many individuals, such as a “Marketing” account and a “Sales” account.
1 Create accounts for individuals when it is necessary to verify the identities
of particular users and you want to manage access at an individual level.
1 Create shared accounts when you want fewer accounts to maintain and you
are less concerned about managing individual access to the database file.
If you host files on FileMaker Server, you can create External Server accounts
that obtain authentication information from an authentication server such as an
Apple OpenDirectory or Windows Domain. For more information, see
“Creating accounts that authenticate via an external server” on page 188.
A privilege set specifies a level of access to a database file. Each database file
contains three predefined privilege sets for common types of access levels: Full
Access, Data Entry Only, and Read-Only Access. When you create a privilege
set, there are many options available that you can use to limit database access,
such as which layouts are viewable, which menus are available, and whether
printing is permitted. Privilege sets can also restrict access to records or fields
from particular tables within a file. Each account is assigned a privilege set,
which determines the level of access when someone opens a file using that
account.
You can create as many privilege sets as you need to define the types of access
you want to permit to a file. For more information about privilege sets, see
“About the predefined privilege sets” on page 180.
Extended privileges determine the data sharing options that are permitted by a
privilege set, such as whether a privilege set permits users to open a shared file
or view a database in a web browser.
φμπ10_υσερσ_γυιδε.βοοκ Παγε 177 Μονδαψ, Αυγυστ 25, 2008 3:59 ΠΜ