Managed distribution

[chrmod]

Organisations of various character wish to distribute Ghostery for their users in an automated (managed) process. That means, extension will be installed on the user behalf, without their direct action. To avoid the confusion the onboarding should not trigger for such installation and users should be presented with no choices to make - extension will be automatically enabled.

Requirements are:

• no onboarding - user consent is acquired by the distributor
• Never-Consent enabled for all websites

Question is how to provide such setup. One way would be to alter the manifest for example it's name or description and based on this information make decisions in the runtime. Another approach would be to introduce the change during the build. Lets find a solution that is simple to maintain.

Tasks

Beta Give feedback

1. https://github.com/ghostery/journal/issues/388

[chrmod]

We run a pilot deployment for cfa.vic.gov.au