Hey Mike, A Google Spreadsheet will not allow you to specify "only user U1 can see row R3". You don't want to setup those rules for each user anyhow - it's better that it's data driven.
What would work for you is to put the access-control layer into a web-application of your own. Your application authenticates itself to the Spreadsheet and has full access to all rows. No user has access to the Spreadsheet themselves. Your application brokers requests from clients, ensuring that a logged-in user is only ever shown information from the row associated with their account. Yes, if your users all have Google accounts, then a GAE app might be an easy way forward to write that application. Although you might decide that since you're already writing code, you can put your data in a system designed for data storage. It depends whether you want to make a user-interface for yourself to manage the customer table, or whether you'd rather leverage a spreadsheet to accomplish this. cheers, David. On Fri, Apr 15, 2011 at 11:29 PM, Mike <[email protected]> wrote: > HI > I'd like to know if Google Spreadsheet can fulfill my below > requirement, if Yes, then i'll dive into it, if not i'll refer to other > technique such as GAE instead. > > i need a spreadsheet as customer table, the client is a desktop > application, by using this application the user can query if his/her email > is in the table, if yes it return the line's data, if not, the table can add > one line for this customer. BUT the customer can NOT query all data in the > table, also he can not edit or delete any/all data in table, because the > customer data table are private. > > I think the key is fine-grained control of the spreadsheet. surely it > can not be public, but if make it private i have to store my authentication > credential in each client, that's NOT security too. > > Thanks very much for your help. >
