After the policy has been refreshed it will take another few minutes for the extension to automatically install, which you can check has installed by going to chrome://extensions. If the user in the status box is an email that is not your domain, they are not signed into chrome using your domain. However, if you're like me and want to see it happen instantly, browse to chrome://policy and click Reload policies. That's all you have to do! If you wait long enough, the policy settings will update on all users accounts after a few hours and the extension will automatically install and appear in their Chrome browser.Click Domain Apps, and once the app has been published it will show in the list. Goto Apps -> Additional Google services -> Chrome Management -> Apps and Extensions -> then under Force-installed Apps and Extensions click Manage force-installed apps.Once its published, if you want to force install this extension to all users in your domain, log in to your Google Admin account.It lists its current status (Draft, Publishing in progress or Published). You will be able to confirm when the extension has been published by returning to the Chrome Developer Dashboard.Upload the ZIP file, confirm details and select the Visibility option 'Private -> Everyone at, then click publish (if you don't see this option you might not be logged in with your Google Admin account).Click 'Add new item', you do not need to pay the developer fee if you are only deploying the extension to your domain.

Sign in to the Chrome Developer Dashboard using your Google Admin account.Minify code etc) and then Zip up the extension folder. Prepare your extension code to be published (eg.

Ok now to the how to, below I have listed out the steps required to upload your Chrome Extension to the Chrome Web Store for a specified Google Apps Domain.

Publishing to google chrome app store