Multi-User security based on layout?

[agtjazz]

I am in the process of developing a database that will be used by 12 or so people via IWP. I have to lock down the pages so that everyone can read it, but only a department rep can update their department report.

So my departments are: Com, EFL , Mus, Phil, PS, KHP etc . All can review the other departments’ reports, but only COM can edit Com’s report.

Do I do different layouts ( based on department) or ?

What is the best way to handle the multi user environment in regards to security?

If anyone can direct me to examples to study, I would surely appreciate it.

Thanks in advance.

[Steven H. Blackwell]

You do not need separate layouts per se. But you do need a separate Privilege Set for each Group. Each Privilege Set can have as many accounts attached to it as required. Each record must also have a field that identifies its "owner" Group. That way, on;y members of a particular Privilege Set can edit the record, but all other can view it.

This concept known as record level access is well documented in a number of resources, including the FileMaker, Inc. Security White Paper, as well as in my book and videos:

White Paper and Book and Videos.

HTH