Extensions

Add extensions to your profiles

Keep the extensions your team uses in one library, add them from the Chrome Web Store or a package file, and choose which profiles run each one.

Guide · 2 min read

The extension library

The Extensions page is the workspace's library. An extension is added once and then assigned to the profiles that should run it, so a hundred profiles that need the same tool share one copy, and updating it in the library updates it for all of them. Each card shows the extension's version, how many profiles it is assigned to and enabled on, and the sites it may read and change.

Add one from the Chrome Web Store

Choose Add extension, keep Type on Chrome Web Store, and paste the extension's address from the store, the one that starts with https://chromewebstore.google.com/detail/. Choose Add from Web Store. PowerOps downloads the package, reads its name, version and permissions, and adds it to the library.

Add one from a file

For an extension that is not in the store, or a version you were given directly, choose Add extension, set Type to Upload file and choose the CRX or ZIP package. PowerOps reads the package before anything is installed and refuses a package that will not open. Extension name and Notes are optional: the name is taken from the package if you leave it empty.

Choose which profiles run it

When you add an extension, tick Also add it to my existing profiles to put it on every profile you already have. Without it, the extension goes into the library and onto profiles created from then on, and the ones you already have are left alone. To choose exactly, open the extension's card and use Assign profiles or Remove from profiles; Select profiles from group ticks every profile in one group at once.

Turn it off without removing it

The switch on an extension's card turns it on or off for every profile it is assigned to. Off keeps the assignments, so turning it back on needs no reassigning. A profile picks up a change the next time it opens.

Built-in extensions

Cards marked Built in are installed by PowerOps itself and say Managed by PowerOps. They come with the application and are updated with it, so there is nothing to add or update for them.