title: OAuth2 Client authentication with multiple users
body: <p>I have built a Room Booking application in FileMaker that accesses Google Calendar via the Calendar API, authenticated with OAuth2.</p>
  
  <p>Everything works well except I am unsure as to the relationship between the OAuth2 Client token flow and the individual FileMaker/GCal users who will use the system.</p>
  
  <p>At the moment, I am both the owner of the project in the Google Developer Console, and the only beta tester, so naturally the system works with my calendar - I log in once, pass OAuth2 my ClientID and Secret, generate my Code, swap it for the Token and Refresh and I'm off.</p>
  
  <p>However, the whole system at the moment only has <em>one</em> Token and Refresh, held in a single row FileMaker table, thus, when I create a second test user, things still forward to my Calendar.</p>
  
  <p>This is where I am unclear. It sounds obvious, but it's hard to find a clear answer on this. </p>
  
  <p>Should I have it so each user uses the same ClientID and Secret (which I keep secret from them) to generate their own unique set of Tokens?</p>
  
  <p>Or is the single set enough, and I'm misunderstanding some other aspect of the system (and if so, what)?</p>
  
  <p>In short: are the Tokens per Application or per User of the Application?</p>