User Dashboard Only Access
Is there a way to give a single user access so that when they login they only see information and projects that are associated with them, without them being the record owner? For example, we have ...
Forum Discussion
Do not go that route, it will make you crazy.
A better way is to set up a table of users where the key field is the user. Then have a field on that record which associated that user with a field that identifies which records are theirs. e.g. say these are Branches and you assign the userid for John Smith to be handling Chicago Branch code CHI.
Then make a relationship from that user table to the AWS transactions table and for the reference field in the relationship use a formula user field called [Current User] with a formula of User(). Look up that CHI branch code field.
Then using Permissions or report filters have the user see only transactions where the branch code = the lookup of that user's assigned branch code.
So the net is just one Dashboard, just one Role and a table with 25 users.
.. and you will retain your current level of sanity, whatever that may be.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
A better way is to set up a table of users where the key field is the user. Then have a field on that record which associated that user with a field that identifies which records are theirs. e.g. say these are Branches and you assign the userid for John Smith to be handling Chicago Branch code CHI.
Then make a relationship from that user table to the AWS transactions table and for the reference field in the relationship use a formula user field called [Current User] with a formula of User(). Look up that CHI branch code field.
Then using Permissions or report filters have the user see only transactions where the branch code = the lookup of that user's assigned branch code.
So the net is just one Dashboard, just one Role and a table with 25 users.
.. and you will retain your current level of sanity, whatever that may be.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
Thanks for the response.
To help clarify on our end, the current user is the client and the client can have many projects (AWS data).
Thanks again.
------------------------------
BW
------------------------------
To help clarify on our end, the current user is the client and the client can have many projects (AWS data).
Thanks again.
------------------------------
BW
------------------------------
- Perfect, so the AWS data will have the client name on the record. So you associate a client name wth each user and then use Permissions to have a single Role Custom Rule that says that the role can see AWS records where the Client Name = the lookup of the current user restricted to client name. You will probably need to make that a checkbox formula field for the rule to use.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
