
Now of course that's going to be critical, when you want to do things like set up tables and fields and relationships. So that account will allow anybody full access to every aspect of the Database. And if you look under the File Options under the File menu, you'll see that each FileMaker file is already set to log in using the Admin and then blank password account. You'll notice that you have an account called Admin, that's already set up in your system, that's assigned to full access.


They're pretty self explanatory full access is the full access to the account. So every time you create a new FileMaker file and every time you convert something in FileMaker, you'll have these three available to you. That means that they are the default security Privilege Sets that are set up with every file. You'll also notice that they have brackets around their names. Now the first thing you'll notice in my file is that we have three different accounts already set up. And you'll see that it opens up to the Privilege Set tab. The way that you get there when you open up the Manage Security dialog is to go to Advanced Settings. Now, when you go into the FileMaker, manage and security, you're going to see that you open up to the Manage Accounts window, but I want to start first with Privilege Sets, and the reason for that is because you can't set up an account, until you have a Privilege Set. So once you actually have that in place you can go ahead and configure security in FileMaker which primarily is made up of Privilege Sets and Accounts. We like to call that, when you're ready to deploy, from a professional standpoint.

But really the real work that you're going to do in security and setting up Privilege Sets and accounts is going to come after, most of the development in your application is done.

So really the best practice here is to set up some test accounts, which are accounts and Privilege Sets, so that you can go through the whole process of user testing before you deploy. And actually here's some dynamic elements that are affected by Scripts, Layouts, and Fields. First of all, security in FileMaker really pertains to more than just providing gatekeeping like an account and password to limit access to your system. A quick note here about security in FileMaker.
