We've also been talking in the office recently about how to manage tool standardization for our developers, to make sure that we're using the same things for specific tasks. Of course, it's easy enough to just give developers a list of things and let them download them themselves, but what happens when you switch computers? You have to download them all over again, and you might not remember which ones you need or what they're called.
Fortunately, we use Google Apps, which has the ability to manage Chrome browsers within your organization. There are a variety of ways that Chrome browsers can be managed: you can customize the Chrome installer, you can set device policies that will automatically apply to Chrome on those devices, and you can set user policies that will automatically apply to users who sign into Chrome.
I decided to go for the last approach for several reasons. First, everybody here at Fig Leaf Software has already installed Chrome! Second, I don't want the apps installed for everyone whether they need them or not - I just want to make it easy for the developers who need them to find them in one place and install them themselves. User policies provide the ability to customize the Chrome Web Store by adding a domain-specific category.
To do this, I logged into the Google Apps admin console.
|Admin console showing additional control icons at the bottom|
|Where's Chrome Management?|
|Chrome Management settings link|
|User settings is what we're looking for|
Once we go there, we'll see a big list of items that can be changed on a per-organization basis. You can create settings for the root organization, and they'll be inherited by its children. Here's a short list of what you can change:
- apps and extensions: which types can be installed, which ones will be pinned to the Chrome launcher,
- network settings: proxy servers, Kerberos, SSL record splitting, DNS prefetching,
- printing: including Google Cloud Print,
- user experience: Omnibox behavior, desktop notifications, Drive syncing, bookmarks, Google Translate, form autofill,
- hardware: audio input/output, video input
Of course, today I'm interested in Chrome Web Store settings, so I scroll to that portion of the screen. Here, I can customize whether the default home page or our private collection should be seen by default, what apps are included in the private collection, and the name of the private collection.
|Chrome Web Store settings|
To customize the list of apps, click on the "Manage private and public apps" link. This will open a dialog that lists different app categories, and which apps are currently listed in your category.
|Recommended apps and extensions dialog|
To add existing Web Store apps, click on the "Chrome Web Store" button, then start typing the app name you're looking for. Once you find it, click "Add".
|Type the name of the app you want to add|
Once you've saved your changes, users will be able to see your list of Chrome Web Store apps when they visit the Web Store, as long as they're logged into Chrome. Note: being logged into Apps does not mean you're also logged into Chrome - you have to do that separately.
|New custom category for Fig Leaf Software users in the Chrome Web Store!|
[Note: cross-posted on the Fig Leaf Software blog]