Publically share an unpublished Add-on

[Andrew Roberts]

Back in the Chrome web store days, before an Add-on was published (available in the web store) you could share a link to the Add-on, I think publically but at least to a select group of testers.

Is this possible with editor Add-ons nowadays. I know you can share an Add-on privately to a single domain without going through verification, and you can share a "public" Add-on via a link, without it appearing in searches. But what I am wondering is can you avoid a security assessment, and get past the 100 install limit, by just sharing with a select (100+) users without it going on the Marketplace?

But then where would you get the link to share it if it wasn't in the Marketplace??

[Alan Wells]

I have successfully published an editor add-on in the GSuite Marketplace as "unlisted".

There is a checkbox in the "Publish" page of the GSuite Marketplace SDK to Unlist Application.

But I don't think that will allow you to get past the 100 install limit, without going through the verification/security assessment.  If you don't need a security assessment, then the verification won't cost you anything.  The only way to get restricted access to the users data is to use a restricted scope, unless your app could somehow run code owned by the user, and get a return.  The user would need to set up a Web App on their account and give your app the published link.