Hey,

I have an employee database and users. The records are in one table and contain all details of an employee.

The users can be simple users or staffmembers.

The simple users have only read access to some lay-outs that show some fields. They have access to all records of current employees.

There are also staff users that should have access to all details of their employees (all fields) and read access to the employees of other teams.

What is the best way to set this up?

Make several privilege sets and combine them into one complex privilege? What would be the best check to see if a user has full or limited access?

tia,

Michel

... your not making yourself very clear... but... anyway, just generate seperate privelege sets for staff, employees and employers... that way you can restrict access around the database both through filemaker security and custom scripts such as

if(get(privalegesetname) = "x"

do Y

end if

Edited January 27, 200619 yr by Guest

Thank you for your answer.

I have already have a lot of schemas for privileges. But, what I run into is the fact that, depending on the value of a field, I want to give access to part of that record to some staff members.

It's a shame I am not very clear, so let me try to explain:

table personnel

id

works at department number ...

name

street

date of birth

health status

criminal record

Now, there are staff members. Say, the head of department x

When a person works at department x, his supervisor can see all fields of the records. And even get's edit access to fields via some lay-outs.

But, when the person doesn't work at the department x, the staffmember of department x should only see the name and address field, but not his crimimal record...

So, my question is how to set this up? I have the feeling I should be able to combine some privileges, but will those combine well? How to prevent all those long listings of in the lay-outs?

To solve the "showing fields you don't want to be shown" issue, you may want to consider layouts that are specific to a privilege set when necessary. In other words, If [ Get (PrivilegeSetName) = "Staff", then go to Layout_ForStaffMember, If [Get (PrivilegeSetName) = "Simple", got to the layout designed for that privilege set, etc.

For just controlling the user's editing, not viewing, I believe that's best controlled in the privilege sets.