Skip to main content

Managing Google APIs Console Teams with Groups (including Apps for Business!)

As a Developer Advocate @ Google, I've worked with tons of individuals & companies who have multiple projects with Google. A key piece to all of their integrations is our Google APIs Console (and soon to be the Cloud Console) - the one-stop shop to create and manage Google API projects. One question that comes up often is, "how do we manage team access?" This is especially important for companies where employees come and go over time, possibly taking the keys to their projects with them.

The tl;dr is use Google Groups to manage Team members.

The console has a built-in system to manage project members via email addresses. It can be found under Team:

As you can see, you can add multiple emails to this list. A common practice among companies is to create a shared `` address and pass around that email password. WAT?!? DON'T DO THIS. Sharing passwords is insecure and generally bad for the universe.

Everyone working on your Google projects should have their own account. Instead of adding each user to the team, add them to a Google Group. Then add that group as a member (probably owner) of the project and manage ownership through the built-in management controls of Groups.

Protip: Did you know that anyone can create a Google account, even with a non-Gmail or Google Apps email? A smart move would be to have your developers create a new Google Account with your company email and not use their personal Google accounts for work-related development.

If you're looking at Google Groups, I would recommend naming your group as `` and setting the group as invite-only.

Note for Google Apps for Business: Your domain won't let you add members to a project that isn't in your domain, so a standard Google Group won't work (see how it is above?) Fortunately, we have a solution! Google Groups for Business works in the same way as a standard group but is created by admins and ends with ``

Note for Cloud Console: Projects created through the Cloud Console require at least one real user owner, so you can't try and delete yourself as the owner of the project if you've added a Group. You can have a sole Group owner if the project was created in the Google APIs Console.

Hope this tip helps you and your teams prevent future headaches!

P.S. if your company manages a Google+ Page and/or YouTube page, check out my post on how to manage your accounts.

Popular posts from this blog

My weekend project: an Arduino, Raspberry Pi & Node.js robot

Yes I know, I'll get more buzzwords when I my JavaScript creates Cloud Synergy - but after I Pivot.

I've been spending my wee few hours a week designing, tinkering and finally building my little robotics platform. I've had ideas brewing for a while but haven't had enough time outside of work to start hacking.

It all started when I first saw Rick Waldron's Johnny Five framework for Node.js.
Sensors are asynchronous, so, ya, a node.js robot framework makes sense. A few months later I started sketching designs, reading up on firmata and buying my arduino & Pi.

Before the what & why, here's the basic BOM:
1 Arduino Uno R3 running firmata1 original Raspberry Pi with Raspbian, Node.js & 4gb of storage1 Magicians chassis1 SN754410NE Quad Half H-Bridge to drive the motors1 dual-output mobile battery backA custom mount for the Pi & some custom USB cabling for power Why Raspberry Pi The main controller is a Rpi. It turns 2 small motors by delegating instru…

Easily switch between different versions of GCC ARM Embedded

I need to switch between different versions of GCC ARM Embedded somewhat often. I couldn't find a good solution online so I threw together a simple shell script to simplify the process I call switch-gcc-arm. Here's a screenshot:

The script is pretty simple, even for a bash n00b like me. It uses symlinks so that standard make files work:

For each version of gcc you want to support, you'll need to add it is as an elif statement and add it is as a new option. The script creates a "virtual" $BIN directory that points to whichever version of gcc you need. Make sure you add the path to the folder where you placed the script, as well as the $BIN path you set as the virtual bin directory. I add the paths to my .bash_profile and rely on the system keeping the last-used version of gcc.

Hope this helps someone. Any suggestions for improvements?


A Maker's Equipment List

I've been building up a nice supply of tools and components so I decided it is high-time to build a small workspace in my tiny SF apartment. There were things I knew I still needed but wrestled with some tough choices (like which Oscilloscope to buy.) I wanted either a nice Wishlist on Amazon or at least a great list to start my journey. I found a few decent starting points in the form of video & blogs:
How to set up an electronics lab/workshop at homeSo You Want to Build ElectronicsHow to equip your EE lab The first link is actually a transcription from +EEVblog /by +Dave Jones (EEVblog is an awesome blog and YouTube channel, you should subscribe.) The second blog /by +Kenneth Finnegan covers more of the components side.

What I couldn't find is a complete compiled list with links to purchase. So I made one! I put together a simple Amazon Affiliate store called Maker Workbench Equipment List. I merged what I thought made sense and added a bunch of items I think any good Mak…