Google Apps Platform

Google Apps Extensions Console

The Google Apps extensions console is a project control panel for developers writing in-house applications that extend Google Apps. The console also unlocks some features for use with Google Apps Marketplace applications (for example, custom extractors for Gmail contextual gadgets).

Console Screen

Contents

Overview

The Google Apps extensions console provides a direct way for developers writing applications for their own domain to take advantage of the integrations provided by the Google Apps APIs—such as OpenID SSO—without having to create a Google Apps Marketplace listing.

Additionally, the console provides Google Apps Marketplace developers the ability to create a custom extractor for Gmail contextual gadgets for applications that are deployed through the Google Apps Marketplace.

The Google Apps extensions console is a tool for configuring an application that is integrated with the Google Apps APIs. The console offers a way to do the following:

  • Store code files (the console validates the XML for you)
  • Share a single project configuration among multiple team members.
  • Generate and view the OAuth credentials for applications using 2-legged OAuth.
  • Upload an application manifest and one or more custom extractors for Gmail contextual gadgets.
  • Install an application onto the Google Apps domain (Requires developers to be domain administrators).

Using the Google Apps extensions console

The Google Apps extensions console allows you to manage several components of an application. The different actions you may wish to take on a project are described below.

Logging in

  1. Point your browser to http://code.google.com/googleapps/console/a/yourDomainName.
  2. Enter your user ID and password.

Creating a project

  1. Click Add Project.
  2. Give the project a name.
  3. Click Create Project.

Displaying the project overview

  • Existing project: select it in the Project dropdown.
  • New project: see Creating a project.

Uploading the application manifest

  1. Under Manifest, click Upload.
  2. Click Choose File and select the XML file that contains your application manifest. The console checks to be sure the manifest is valid.
  3. When the file passes validation, click Update Project. The Project Overview reappears with a success message.

Uploading extractors (optional)

If your application includes a Gmail contextual gadget:

  1. Under Extractor, click Upload.
  2. Click Choose File and select the XML file that contains your extractor. The console checks to be sure the extractor is valid.
  3. When the file passes validation, click Update Project. The Project Overview reappears with a success message.

Installing the application in your own domain

  • Click Deploy Application. This begins the process of installing the application described in the manifest to your domain. The Google Apps Control Panel guides you through a few setup steps, such as granting the application access to your domain's Apps data.
  • If the Deploy Application button is grayed out, you are not the domain administrator. Click Team, add your domain's administrator to the project, then go and ask the administrator to click Deploy.

Moving a finished application into the Google Apps Marketplace

You can move the application to the Google Apps Marketplace by creating a Marketplace listing (which includes your application manifest) and going through Google's listing approval process.

Frequently asked questions about the console

What kinds of files can the console handle?
For any application, you can upload the application manifest. If your application includes a Gmail contextual gadget and you have created one or more custom content extractors to trigger the gadget, you can upload the custom extractor files. Application manifests and Gmail contextual gadget extractors are XML files.
Why are my OAuth credentials in the console different from those in the Marketplace?
Once your application is listed in the Google Apps Marketplace, the Marketplace provides an OAuth security key and secret that is different from those provided by the Google Apps extensions console. Which credentials you use depends on how your application is being installed. If your application is installed in your own domain using the console, use the OAuth credentials shown in the console. If the application is installed through the Marketplace, use the credentials shown in the Marketplace.
How do changes uploaded to the console affect installed apps?
When you upload a new manifest or extractor to the console, the changes are propagated automatically as follows:
  • Changes to custom extractors are immediately deployed to every domain where your application is installed.
  • Changes to the application manifest are immediately deployed to your own domain, if the application was already installed there using the console's Deploy Application button. Manifest changes are not automatically deployed to any other domains.

To automatically deploy application manifest changes to other domains, edit the manifest directly in your Google Apps Marketplace listing. See Edit the Listing.

Note: If any newly uploaded files contain requirements for additional data scopes, the changes will not take effect until the domain administrator grants the additional data access permissions.

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.