Problem
I can't find a way to publish a "private" google sheets addon and share it to testers with the new G Suite Marketplace process as it used to be possible with the Chrome Web Store publication.
Description
I used to publish google sheets addons "privately" (with no verification) via the Chrome Web Store. The process was to publish the addon selecting "Private" as Visibility and then checking "Only Trusted Testers from current publisher settings" adding those users to the list of allowed testers.
Since now new addons can be published only via G Suite Marketplace, I can't find a way to replicate the publishing method described above.
The only possibilities I see are two and none work in my case:
The first is to publish the addon publicly and select "unlisted". This method requires a verification process that I don't need since I just what to share the addon with a handful of users. The second is to publish it privately, but this is only possible if the users are within the same organization. This will also not work since I want to share it with testers outside the organization.
I've been also considering publishing the addon with the testers accounts but linking it to a script owned by myself but I assume this won't be possible.
Question
Is there a way to replicate the "Private" publishing to testers of the Chrome Web Store (or any way to selected users not necessarily belonging to the same organization) with the new G Suite Marketplace?
Answer:
Unfortunately your assertion is correct and this isn't possible.
More Information:
Since G Suite add-ons now get published via the G Suite Marketplace rather than the Chrome Web Store, they now have to go through the G Suite Marketplace publication process. According to the documentation for the G Suite Marketplace:
You can publish your add-on publicly, so that any user can find and install it. You can also publish add-ons privately, for users in a specific domain only. If you are a G Suite domain administrator, you can install published add-ons—whether public or private—for your domain users.
So the only available methods of publishing are either for a G Suite domain, or public.
References:
Publishing G Suite add-ons | Google Developers
Related
Problem
I can't find a way to publish a "private" google sheets addon and share it to testers with the new G Suite Marketplace process as it used to be possible with the Chrome Web Store publication.
Description
I used to publish google sheets addons "privately" (with no verification) via the Chrome Web Store. The process was to publish the addon selecting "Private" as Visibility and then checking "Only Trusted Testers from current publisher settings" adding those users to the list of allowed testers.
Since now new addons can be published only via G Suite Marketplace, I can't find a way to replicate the publishing method described above.
The only possibilities I see are two and none work in my case:
The first is to publish the addon publicly and select "unlisted". This method requires a verification process that I don't need since I just what to share the addon with a handful of users. The second is to publish it privately, but this is only possible if the users are within the same organization. This will also not work since I want to share it with testers outside the organization.
I've been also considering publishing the addon with the testers accounts but linking it to a script owned by myself but I assume this won't be possible.
Question
Is there a way to replicate the "Private" publishing to testers of the Chrome Web Store (or any way to selected users not necessarily belonging to the same organization) with the new G Suite Marketplace?
Answer:
Unfortunately your assertion is correct and this isn't possible.
More Information:
Since G Suite add-ons now get published via the G Suite Marketplace rather than the Chrome Web Store, they now have to go through the G Suite Marketplace publication process. According to the documentation for the G Suite Marketplace:
You can publish your add-on publicly, so that any user can find and install it. You can also publish add-ons privately, for users in a specific domain only. If you are a G Suite domain administrator, you can install published add-ons—whether public or private—for your domain users.
So the only available methods of publishing are either for a G Suite domain, or public.
References:
Publishing G Suite add-ons | Google Developers
I have an existing Google Docs add-on (with a G Suite Marketplace listing) with thousands of users, and I've made a development version of it for Google Slides that I'm ready to publish. I realized now I can bundle them together (which makes a lot of sense).
However, the instructions on how to bundle multiple add-ons seem to imply that neither one exists with a GCP project:
It is possible to bundle add-ons of different types together. This requires them to share a GCP project and G Suite Marketplace listing, as described above. Choose a standard GCP project to use for the bundled add-ons, and switch each add-on to use that GCP project.
Since I already have the Docs add-on in a standard GCP project (at least I think I do since it's available in G Suite Marketplace), can I just switch the new Slides add-on to point to it?
My goal is to minimize re-authorization of existing users as much as possible.
Also, would this approach simplify having to get my add-on re-approved? It took 6 months the first time, but that was years ago...
You can link your new Slides add-on to your existing GCP project and resubmit it for approval.
Having your users reauthorize your application will happen only if you are accessing different scopes than the last time they authorized.
In regards to the time taken for approving an add-on, there is no guarantees on time.
Currently, I'm working on a project that will be sharing a written in Apps-Script framework Google Slides extensions. One of the first tasks I've had to do was how to publish an example add-on to a whole private domain? To accomplish this I've used the instruction from official Google documentation:
Publishing an editor add-on
I've gone through these steps without any bigger problems, but it looks like not everything has gone as expected. My extension now is visible in a Chrome Web Store, but unfortunately not in G Suite Marketplace. In result, I cannot see it in a list of add-ons in Google Slides editor that are available for my private domain.
I've published script to Chrome Web Store and also enabled and configured G Suite Marketplace SDK in my project. And even the state of publishing looks fine:
My manifest.json file
It even looks like my extension is installed for a whole domain(I've clicked 'Integrate with Google' button)
But still I cannot see my add-on in Google Slides as well as in G Suite Marketplace:
Did somebody ever faced a similar situation? Did I skipped something important or am I doing something in a wrong way?
#AlanWells I've did what you said and saved configuration, but still I can't see my addon in domain-wide addons in Google Slides editor as well as in G Suite Marketplace.
Required scopes
Scopes in project settings
Scopes in Marketplace configuration
Can I do anything else in this situation ?
My Google App Script (an add-on for Google Docs) has passed the OAuth verification and has also been verified by the Google team. The application is both "Published" and "GAM: Published", yet Domain Admins are unable to locate the add-on when searching for it, and therefore cannot install it to their domain users.
I have read the following two articles many times:
https://developers.google.com/gsuite/add-ons/how-tos/publish-addons
https://developers.google.com/gsuite/add-ons/how-tos/publish-for-domains
I've been liaising with the docs-addon-advisor, who has approved the add-on again and again, but nothing seems to impact the Marketplace Apps search results. It is however availble in the Web Store search results. They have directed me back to this forum for advice.
I've followed the articles above and see no error messages in the publication, yet still the add-on remains invisible to the Domain Admin world.
You can see that DocuSign is happily installed in my domain, I can search for it, and it has been pushed down onto my domain users. So what I'm trying to achieve is possible. My add-on is simply absent from this marketplace search for some reason.
Any ideas?
Your add-on is published at https://gsuite.google.com/marketplace/app/seal_atn/820114923602. It does not have "Enable individual install" checked so it's installable and searchable only by domain admins.
I am able to setup an Apps Scripts project to create a gmail add-on and can test it out using an #gmail.com account but the option to install developer add-ons does not show up in my G Suite account.
Alternatively, how do you deploy a gmail add-on to a private domain? i tried following this https://developers.google.com/apps-script/add-ons/domain-wide but it would not let me save the configuration if all I had selected was the 'Gmail add-on extension' checkbox.
Thank you.
Domain users are now able to publish a Gmail add-on private to their own domain. Furthermore, domain private add-ons do not require a Google review, you are free to build them and publish them at your leisure.
See the documentation here:
https://developers.google.com/gmail/add-ons/how-tos/publish
AFAIK the deployment of Gmail add-ons is restricted to selected developers.
Source: https://gsuite-developers.googleblog.com/2017/10/gmail-add-ons-framework-now-available.html
While you can't publish your add-on just yet, you can fill out this form to get notified when publishing is opened. We can’t wait to see what Gmail Add-ons you build!
Recently (January 2018) on the G Suite Update Alert blog it was announced new Gmail add-on features for G Suite accounts.
From https://gsuiteupdates.googleblog.com/2018/01/install-gmail-add-ons-for-your-domain.html
In addition, we’re making it easier for developers to design Gmail
Add-ons specifically for their organizations. In the coming weeks,
developers in your domain will notice two changes:
They’ll be able to install Gmail Add-ons for their own G Suite accounts before they’re published, to aid in the development process.
Previously, this was limited to their personal Gmail accounts.
They’ll be able to publish Gmail Add-ons to users in their own G Suite domains. In addition, they'll be able to publish to the general
public, after requesting and receiving publication permission.
Stay tuned to the G Suite Developers Blog to learn more about these
two developer capabilities and when they’ve launched.