Review Process for unlisted/private

[Mason Curry]

Hello,

I am working on an internal extension for our development team/admins for helping us navigate through a web app we are developing (ID olgkngclodaanhobjiknebocnmdlbcoi)

I originally set this to unlisted, but it is stuck in review. If I set it to private, can that expedite/cancel the review process? We may need to make quite a few changes to it and update it across the team quickly. Worst case scenario we can just run it in dev mode, but some of the users in the project that use the system are not developers and would not know how to do that.

Please advise

-Mason C

[Mason Curry]

For future readers:

Hello,

Thank you for reaching out to us.

The visibility of your extension has no effect on the review time. Private or public, all updates will be treated the same by the review team.

Please note that both new item submissions as well as updates to existing items (*including unlisted/private) are subject to automated system checks and may be flagged for manual review. For the reason of being flagged to the additional compliance review is not shareable with you due to security purposes. Please also note that you cannot modify/update your item or cancel the review while it is in progress. 

[Simeon Vincent]

Hey Mason,

Is your team working in an enterprise environment where devices are joined to a domain or controlled by an administrator? If so, you may be better off setting up a "private web store" (hosting your extension on your own web server) and using enterprise policies to install the extension on your team's devices. This solution isn't a great fit for all teams or use cases, but it would allow you to sidestep CWS review & distribution. The Chrome Enterprise team put together a white paper called Managing Extensions in Your Enterprise that I'd recommend checking out, especially the section called "Create your own on-premises web store".

Cheers,

Simeon - @dotproto

Chrome Extensions Developer Advocate