You are here:
< Back

Creating Google application

  1. Open google developer console
  2. Create your new Project and select it
  3. Select Credentials -> Create credentials
    1. Select OAuth client ID
    2. Select Web application
    3. Click on the Configure Consent Screen
      1. Select External and click on Create
    4. Edit App registration
      1. App Information

        App name: You give a name for your application
        Support email:  You need to select an email address for it.  If you choose external Consent screen and do not have groups the only address you can choose is the main email address what you registered to the google developer.
        App logo: You can upload your own logo here
      2. App Domain

        You need to fill the Application home page and the Authorised domains
        Application home page:  You need to use your main domain address with https:// for example for us is https://wallboard.info
        The Application privacy policy link and the Application Terms of Service link have to be under the same domain!
        Authorised domains: click on the ‘+ Add domain’, and write down the main domain address without the https://.
      3. Developer contact information: You need to give an email address. You can choose the main email address what you registered to the google developer.
      4. Click Save & Continue
    5. Scopes
      1. Add these scopes with ‘add or remove scopes’ button
        https://www.googleapis.com/auth/userinfo.email – See your primary Google Account email address
        https://www.googleapis.com/auth/userinfo.profile – See your personal info, including any personal info you’ve made publicly available
        openid – Associate you with your personal info on Google
        https://www.googleapis.com/auth/calendar.readonly – See and download any calendar you can access using your Google Calendar
        https://www.googleapis.com/auth/calendar.events – View and edit events on all your calendars
        https://www.googleapis.com/auth/drive – See, edit, create, and delete all of your Google Drive files
        https://www.googleapis.com/auth/drive.metadata.readonly – See information about your Google Drive files
        https://www.googleapis.com/auth/drive.readonly – See and download all your Google Drive files
        https://www.googleapis.com/auth/spreadsheets – See, edit, create, and delete all your Google Sheets spreadsheets
    6. Test users
      1. You can add a test user email if you wish, but user cap prior to app verification is 100. You can click on save and continue
    7. Summary
      1. You can see all of the app registration. If you wish some minor changes you can click on the Edit, or scroll down and click on the ‘Back to Dashboard’ button.
  4.  In the left menu click on Credentials ->  + Create credentials
    1. Select OAuth client ID
    2. Select Web application
    3. Add and Fill Authorized JavaScript origins with https://{yourdomain} – this is not just the main domain name, you can ctrl+c and ctrl+v your site. For example, our domain name is https://editor.wallboard.info
    4. Add and Fill authorized redirect URIs with https://{yourdomain}/public-api/google/auth/exchangeCodeForToken
    5. Click on the ‘Create’ button to make it.
  5. Under Credentials -> Create credentials
    1. Select API key
    2. Choose Restrict Key – it will open your API key
    3. You need to choose the Application restrictions -> HTTP referrers (website)
    4. In the Website restriction, you need to click on the ‘Add an item’ button and add your domain name there
    5. Click on the ‘save’ button to make sure your changes are saved
  6. Also, you need to enable two API from the API Library. You can reach the API Library from the Navigation menu  -> APIs & Services -> Library.
    1. You need to search for the Google Sheet API and the Google Drive API. Both of them needed to be enabled for the Spreadsheet.
      For Calendar integrations you will need to enable the Google Calendar API as well.
      When you enabled these API’s you need to wait for a few minutes to get the API’s work properly.
    2. Click on the enable button.

Set up your Google application

  1. You will need Superadmin rights in wallboard
  2. You need to go to the Administrator-> System settings

For  Spreadsheets:

  1. Open google developer console
  2. Select the created Oauth 2.0 Clients IDs credentials, and copy the “Client ID” and “Client secret”
    1. Select the created credential and copy “Client ID” and “Client secret”
  3. Select your created API Key and copy your API Key
  4. Go to your Editor web site Administrator -> System settings search for Google API settings 
    1. Google API Oauth2 client-id – the “Client ID” what you have copied from the Oauth 2.0 Client IDs credential
    2. Google API Oauth2 client-secret – the “Client secret” what you have copied from the Oauth 2.0 Client IDs credential
    3. Google API key – the “API Key” what you have copied from the API keys
  5. After you finished with it, save and click on the ‘Restart application’ button. The server will restart itself. It needed a few minutes to started.

After you have done it needed a few minutes (at least 5)  for your Google Credentials to work properly.

 

Note: If you choose Internal, you may can have this:

How will the scopes be used?
We use it to sync the files and folders from your drive. We only sync folders that you have been choosen to sync, we don’t touch or try to access any other files/folders. You can cancel the sync process any time and delete your data from our server permanently.
We use the files to show them inside contents, which only you/your tenant can publish to the public.
Demo Video you can use either this one: https://www.youtube.com/watch?v=VqATUNFJePE,

Please note that it’s not necessary to have your application verified by Google

Our system can use your google application if it’s set up correctly, even if it’s not approved by Google.
Although it has some limitations and disadvantages, see the details here.

What if I don’t verify my app?

Your app will be limited to 100 authorized total users.
Your app will be identified to users by its redirect location or other client data.

Users of unverified apps or your test builds will see an unverified app warning based on the OAuth scopes in the authorization request.
This warning is to protect users and their data from deceptive applications.