Subtitles of the Movie

Accounts or who you are, privilege sets or what you can do and FileMaker7 comes with three privilege sets already defined. Full access is defined by default to the admin account and it is exactly what it says total access to everything. I have also in this case assigned to the account that I have created called *********** . There is a second privilege set called read only access which is defined by default as being the privilege set for the guest account, the guest account or member is not active unless you turn it on. A third privilege set data entry only is exactly what it says and that's not assigned by default to any active accounts. Now I can create my new privilege set if I want to and I am going to call this as supervisor row. A privilege sets sometimes are called row as in row base security its what you can do and this is for data entry supervisor. It's someone who has more access than a data entry clerk but less access than a system administrator. Now over here I have four categories in which I can define access. For records I can allow all access, creating and editing but not deleting, read only, and view only access or no access. For layouts I can make all of them modifiable or view only or no access. I have similar controls over value lists and over scripts. If you notice that in each of these categories I have at the bottom a custom privilege s option and custom privilege s work in the following way. When I access them in here I am looking at custom record privilege. You will see the tables that are in this database and for any of those tables I can set the view and create and delete options. Down here I can view I can say yes, you cannot edit yes you can create and no you cannot delete. I also can come along here to individual fields, I can say all or none or I can comedown to a specific field and make it modifiable or view only or no access. So for example the event name might be modifiable. This gives me control absolutely down to the field level of a record in an individual table. I can also come along here to the table name any new table at the privilege s that I set here will be applied to any new table until such time as I might come along and change the custom record privileges. So I can say yes and I won't let people to delete them, and I am going to allow all field access. So I can say custom privilege s for records, for layouts and it's a similar approach here, every layout is listed at the bottom of the list. I have the ability to set privilege s for new layouts for value lists similar approach, and for scripts similar approach. So that handles the data access and design part of the privilege set. I am going to just modify this, I am going to just say all are view only. I am going to make value lists modifiable and I am going to make scripts executable only for my data entry supervisor. Over here I will allow printing I will allow exporting, I will not allow management of extend privileges. The supervisor can over write data validation warnings for every one I want to disconnect them automatically ideal and I will let the data entry supervisor and infact, I will let most users for systems that I build modify their own password and I do try and have them changed. I found that once a month is ********* for some peoples so I am going with six months its not particularly secure but you have to strike a balance between what is secure and what people will, and here too without writing the password down on little piece of paper that may tape to the monitor which is very insecure. And I like an eight character minimum password. For the supervisor I will allow menu commands and I will allow access. Here is the important part of the file unified security model I am going to say supervisor can have access over the network and through instant web publishing and long the whole what you see here is I have now created privilege s in the form privilege set. For the supervisor row I can come here create a new account and this account name is going to be George and I will sign a password to it, require the user to change the password on next login. And I am assigning the supervisor row privilege set to George and now George have those privilege s that I have defined in that privilege set. I can assign a separate account for every supervisor or I could have a shared account for all supervisors and individual accounts for each data entry clerk. In this model what I did here I made ********* someone who has full access just to make a little more life like I would make ********* someone who a data entry clerk. So she has data entry access only, George has supervisor access. You will notice the brackets here read only access, full access and data entry only are FileMaker defines privilege sets. This one which I just defined does not have square brackets around it.