At this moment, you can install your own add-ons and add-ons from other developer if your account and its account are of the same domain, but if the domain is not from an institution and they are standard gmail accounts.
In the other hand anyone with a gmail account can copy scripts and manifest from one add-on and create one to use, but it is not a good experience.
I know that Google plans to open the add-ons market but is there a workaround to do this now?
Thank you very much
Related
I have developed a Google Appscript gmail addon which users can report spam emails.
I followed the exact steps mentioned in here to publish the add-on.
Setup GCP project and linked it with App Script
Configure OAuth screen and submit it for verification.
I am using following scopes.
OAuth Scopes
Since I am using sensitive scopes, I have to submit it for OAuth
verifcation. I was asked to verify all domains and then I verified all
domains and now all are showing as verified in search console .
I communicated it with the OAuth verification team and still OAuth
verification status is showing as "Pending developer action". I tried
to get some advice from OAuth verification team and I did not get any
response from them.
OAuth verification status
Enable and configure the Google Workspace Marketplace SDK
Create a store listing.
Since Gmail add-on needs to be available for all domains, I have
submitted the GCP for store listing as well. Status is shown as "Under
Review".
I need to publish the Add-on to Google Workspace Marketplace ASAP.
Can some one advice me to continue the publish process?
I released a Google workspace add-on for Sheets a week ago.
Installing and accessing via the workspace side panel menu works fine on personal gmail accounts.
However, on G-Suite accounts, it is not accessible/viewable in the side panel menu in sheets, unless the G-Suite admin sets release preferences to 'Rapid Release' in the domain settings: https://admin.google.com/u/0/ac/accountsettings/preferences?
This causes a big issue with distribution to any accounts that are not personal gmail accounts! Here's a short video of the issue: https://youtu.be/lSIrF9OtrZA
Has anyone else seen this? Is there a fix so we don't have to ask everyone who installs to activate this setting?
I have published a Sheets Editor Add-on on Chrome Web Store and my colleagues on the same G Suite domain can install it just fine, via the Web Store link.
However, the G Suite account admin doesn't have the option to install it for the whole domain. Anyone have a clue on where to start investigating this?
Edit: I have read in other places that it sometimes takes 3-4 days from publishing in Chrome Web Store until it shows up in the Marketplace. However this doesnt seem to be the case for us since we now have waited for about a week.
The app has to be published on the G Suite Marketplace in order to enable a domain-wide installation.
If it is only published on the Chrome Web Store it has to be installed manually by each user.
Choosing where to publish: GSuite Marketplace or Chrome WebStore
If it is published on the G Suite Marketplace it can be installed for the whole domain by admin account following this steps:
Sign in to Google Admin console.
On the dashboard, click on the Apps icon:
Once there, go to 'Marketplace apps'
Add services to your domain
Search your App and choose to install it for the whole domain
And you are done, the app is installed for the whole domain.
Install Marketplace apps
So I have found a way to publish the app even if it's not discoverable in the Marketplace.
Go to https://console.cloud.google.com/
Go to G Suite Marketplace SDK
Under Publish in the left pane, Publish the add-on and get the App URL.
From the app URL, the domain admin can install the add-on for the whole domain.
Is it possible to authenticate to third-party service in G-Suite (Gmail) Add-ons, but without oAuth. The service I want to authenticate works on REST API and has no oAuth support.
The best for me would be to open a new window (as with oAuth), login there and return token to the Gmail add-on frame. If that won't be possible, I'd go with giving a username and password in dedicated Card in add-on, but I'm not sure it that solution will pass Google verification when publishing in Marketplace.
I'll be grateful for all the suggestions.
Unfortunately no. When connecting your add-on to third party services(ex. your application server), Gmail forces you to set up a separate authentication process for user to go through to use your services.
However, if the non-Google service does require authorization, you'll have to configure OAuth for that service. You can make this process easier by using the OAuth2 for Apps Script library (there is also an OAuth1 version).
Your service can still use Google OAuth to authenticate the user, you just need to set it up separately from your Gmail add-on.
You can read more on it here: https://developers.google.com/gmail/add-ons/how-tos/non-google-services
Also in my post I explain the process of connecting your non-google services to gmail add-on in more detail
I have followed all the steps here: https://developers.google.com/apps-script/add-ons/domain-wide
And then went through them a million times already.
I can install and use it if I click Test Installation Flow from under Google Apps Marketplace SDK Configuration.
When publishing, the check box for Publish in Google Apps Marketplace is always checked.
Still, when I log in as a domain administrator and go to Marketplace Apps - Add App, I can't find my app in the list.
If you're from Google support, here's the link to my app, maybe you can check something in the backend: https://chrome.google.com/webstore/detail/enabler4sheets/inpioilbljppoobbblcpbpjplkefmkep
Based from the Google Apps Script documentation, The add-on’s name must be the same as the name of the Apps Script project. The checkbox next to Publish in Google Apps Marketplace should be checked only if you are publishing the add-on for domain-wide install and you are not bundling the add-on with an existing Google Apps Marketplace app. See the style guide for more information on the other fields. Select the most recent version of your code and click Create web store draft. This will open a new page for you to configure the add-on for inclusion in the Chrome Web Store.
What I can suggest is to repeat the process based from the document. Please check the Complete application ad publish your add-on: https://developers.google.com/apps-script/add-ons/publish#complete_application_and_publish_your_add-on