#Chrome plugin how to#
#Chrome plugin install#

#Chrome plugin install#

Public: Everyone can see and install your extension.Įvery extension needs to be reviewed by the Chrome Web Store. Just note that anyone with the link will be able to install the extension.ģ. This is a good option when you want an extension to be only used by users in your enterprise but who might need access on BYOD machines. Unlisted: Only users with whom you share the extension link or who already have the app will be able to see it. Even with a direct link, if a user is not on your domain, they’ll get a 404 error.Ģ. Here’s what your users will see via the Chrome Web Store, notifying them that this is a restricted extension only users on your domain:Īny other users will not see the extension and will not be able to search for it. To make private extensions available to users outside of your domain, you would need to set up a “trusted tester” group and add them manually via email addresses within the Chrome Developer Dashboard. Private: Only users in your domain can see the extension and install it. There are three ways you can publish an extension to the Chrome Web Store:ġ. Check out this link for more information. You can do this by creating a collection that users can browse and install. You might want to recommend a group of extensions to users in your organization. Create a collection of extensions (optional) Then verify your information (check for the correct the app ID and version number, for example). In Chrome, click More>More tools>Developer tools. You can troubleshoot the extension using Chrome logs. Running the extension and ensuring that it functions correctly.Clicking “load unpacked” and browse to your extension folder.Signing into Chrome and browsing to chrome://extensions/ (Make sure you have developer mode on it’s located at the top right).You might also need a screenshot if you publish it as unlisted or public.) (Depending on your extension, you might have other files, but this is the minimum needed to add an extension to the Chrome Web Store. To do so, you’ll need at least the following:Ī manifest file saved as manifest.json (This is a JSON file that describes what the extension does).Ī 128-pixel by 128-pixel logo, saved as 128.png. Once you’ve created your extension (if you need to, check out this tutorial on writing extensions), it’s time to package it up to add it to the Chrome Web Store. Note that you’ll need to request a developer account (if you don’t have one already) and pay a small, one-time fee to publish extensions.

#Chrome plugin how to#

In this post, I’ll provide some guidance on how to get this done. But to use these methods, the extension needs to be present in the Chrome Web Store. Once the extension is created, the question becomes: How do you deploy it to your users? Most administrators use the Extension Install Forcelist policy, either via Chrome Browser Cloud Management or Microsoft Group Policy Object (GPO), to remotely install extensions to their users. I’ve written about the different methods of managing third-party extensions, but sometimes enterprises want to create their own custom extensions, so they can meet the exact needs of their users. IT administrators often need to manage extensions to protect and enable their employees who use Chrome.