Tell us what you know about Manage Security. This is the starting point for setting up accounts, passwords, privilege sets and extended privileges in order to control what users can or cannot do with your solution.
One thing that got me on the right track:
set up the "privileges" for what you want to do in each table, each record, each field, each layout, and/or each script, etc.
You can make more than one set with different access.
Users can view only if desired.
Open Security under the File menu, Manage.
Click on Privilege Sets.
If desired, create a new dummy database to play around with these settings. But once you get the 'rights/access' done, then you assign accounts to them. Accounts (the users) also have passwords.
These may also help (start here and all the linked pages):
See, that's the thing. In Privilege Sets I can define access to tables, layouts, value lists, etc. But what I'm trying to figure out is how to hide a certain object (or, alternatively, make it read-only) for a specific user. Manage Security section does not seem to allow manipulating individual object accessibility, unless I missed it somehow.
Try hiding the field and showing a different field that has the browse privilege. Are you are familiar with the hide feature?
If you're talking about "Hide object when" in the Inspector, then yes, I tried it but couldn't figure out how to tie it to UserName.
Yes, you can define down to the field level!
Could you please point me to the right direction. Even if I drill down to Custom Layout Privileges, I can only see privileges associated to Layouts, Records and Associated Table, but not to individual fields or objects. What am I missing?
Records: (choose 'Custom privileges...')
Custom Record Privileges dialog
Click on a Table Name
View = Yes
Edit = ?
Create = ?
Delete = ?
Field Access = Limited
You will see a new dialog "Custom Field Privileges"
Click on a Field Name
Privilege (no access, view only, modifiable)
Great, that's exactly what I was looking for. Thank you very much!
There are, in decreasing order of security: security level controls, data level controls and user interface controls that you can use.
User interface controls--such as hide object when and script triggers are more user friendly but less secure. Thus, it is often a good idea to back up UI methods with a data level (field validation) or access privileges (if possible).
But it it is possible to designate specific fields as modifiable or editable for a given privilege set in manage Security.