Forum Discussion
QuickBaseCoachD
8 years agoQrew Captain
Here are some ideas.
1. Use field level permissions to block access to certain fields.
2.Hide the Table to certain Roles so that these users will not know the Table ID# to append &a=q&qid=1 to
3. Move the table into a separate app and block access to that app for that Role. But you can still have a cross app relationship to pull the data into child tables on lookups. The permissions for a cross app relationships are set at the Advanced Properties tab for the source app and if the user does not have permission then these permission levels will apply - so that really is your more secure method. I believe actually it is bullet proof as then those roles simply cannot guess their way to the table or receive a link from a co-worker and gain access.
1. Use field level permissions to block access to certain fields.
2.Hide the Table to certain Roles so that these users will not know the Table ID# to append &a=q&qid=1 to
3. Move the table into a separate app and block access to that app for that Role. But you can still have a cross app relationship to pull the data into child tables on lookups. The permissions for a cross app relationships are set at the Advanced Properties tab for the source app and if the user does not have permission then these permission levels will apply - so that really is your more secure method. I believe actually it is bullet proof as then those roles simply cannot guess their way to the table or receive a link from a co-worker and gain access.