Re: Fine Grained Access

A simple-minded solution would be to create a two column User_Campus table
- User, Campus (could be ID or Name, whatever works for your situation).
Most folks would have one row in that table. The multi-Campus folks would
have two or more. Your security predicate would be "Where Campus In
(Select Campus from User_Campus Where User = <UserCapturedAt Logon>)".

The key to successful FGAC use is a flexible, table-driven security
meta-data model. No hard-coding should ever be needed.

I am running 10.1.0.4 on Unix. I work with a university system
involving 28 campuses. I am starting to use Fine Grained Access on my db.

I currently use the Predicate to inspect the login name in order to
determine what records they see. I limit them to only see their own
campus records. Works great. Well, now I have the situation where
certain users will be required to administer records from multiple
campuses. I could create group and add the users to the group. But
that would mean hard coding the username in the functions. Not ideal.
Any ideas or workarounds???