Jump to content
Sign in to follow this  

Multi-User security based on layout?

Recommended Posts

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.

Share this post

Link to post
Share on other sites

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.


Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.