User security for ~120 organizations

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I have only ever toyed with user level security once. I have been asked to
make a database where each of about 120 organizations has their own password,
and only one person from that organization can be in the database at a time.

Also, they do not want each organization to see data from other
organizations. Should I try this with the user-level security wizard? My
experiences with this wizard have not been positive (i.e. the only one who
had to enter a password to get into the database was me).

Any help on this subject would be GREATLY appreciated.

Thanks,
~MATT
 
This is an appropriate use for User Level Security, but I would
proceed manually, rather than using the Security Wizard. See
http://www.geocities.com/jacksonmacd/ for my paper on user level
security plus links to other resources.

You will need to modify your database in order to filter the
information for each of the 120 organizations. The essential steps
will be to:
- add a field for holding the name of the appropriate user
- use the CurrentUser() function to determine the name of the current
user
- populate the field in the tables with the value of CurrentUser()
when you create records
- use CurrentUser() in your queries to restrict the records that are
displayed to the user.

In addition, you may want to explore Read With Owners Permission
(RWOP) queries that can be used to deny anybody the ability to read
the native tables, but to ONLY see the data by using your predefined
queries (which will use the CurrentUser() function). See the security
FAQ for additional information.
 
Thanks for the link. You rule!

Jack MacDonald said:
This is an appropriate use for User Level Security, but I would
proceed manually, rather than using the Security Wizard. See
http://www.geocities.com/jacksonmacd/ for my paper on user level
security plus links to other resources.

You will need to modify your database in order to filter the
information for each of the 120 organizations. The essential steps
will be to:
- add a field for holding the name of the appropriate user
- use the CurrentUser() function to determine the name of the current
user
- populate the field in the tables with the value of CurrentUser()
when you create records
- use CurrentUser() in your queries to restrict the records that are
displayed to the user.

In addition, you may want to explore Read With Owners Permission
(RWOP) queries that can be used to deny anybody the ability to read
the native tables, but to ONLY see the data by using your predefined
queries (which will use the CurrentUser() function). See the security
FAQ for additional information.
Click to expand...
 
Back
Top