Developing Private Gadgets for Google SitesPrint

Google Apps provides powerful communication, collaboration, and productivity tools right from the browser. More than 1 million businesses are using Google Apps and 3,000 more sign up each day. With Google's developer tools, you can extend the functionality of Google Apps, integrate with other systems, or build new applications for your company and other businesses. For more information about business opportunities using these tools, visit our solution provider site.

With Google App Engine, you can use Google Apps to: restrict your application to members of your domain deploy your application to any domain you own. deploy your application to your Google Apps domain, click the 'Versions' link on the left hand navigation menu of your application's dashboard. Click the 'Add Domain...' button in the light blue box at the screen.

Developing Private Gadgets for Google SitesPrint
Gadgets are lightweight applications written in HTML and JavaScript. In Google Sites, gadgets let you embed rich media, retrieve feeds, and perform simple tasks like managing a to-do list.

Most gadgets that you use are hosted on the public internet and their source code could be read by anyone. However, Google Apps Premier customers can create private gadgets that are only visible to members of their Google Apps domain. You can find these gadgets in a directory with your company's domain name within the gadgets directory.


Management gadgets:
We've also made a couple beta gadgets to make this management process easier: the Private Gadget Editor and the Directory Manager gadgets. For now, Firefox is the only supported browser for these gadgets. You can use these gadgets by inserting them into a Sites page by clicking Insert -> Gadgets -> More and then adding each gadget by URL. You can find the Private Gadget Editor here and the Director Manager here.


Administering your App Engine Application:
With Google App Engine, you can administer your application using a Google Account or a Google Apps account. Your app's administration account should use the same authentication as the app's users. For instance, if you set your app's authentication to Google Apps, you should administer that account using a Google Apps email address. While it is possible to have an account that is both a valid Google Apps account and a valid Google Accounts account, you should avoid using such an account to administer your applications.


Source: http://code.google.com/appengine/articles/auth.html