I want to add my Google Workspace Marketplace Add-On to app launcher but it is only appearing in the sidebar. I have gone through the support documents but have not found anything in this regard. How do I make it appear on the application launcher as well?
The app launcher image is given below
The sidebar icon is shown below
Answer:
It's not possible to add Workspace add-ons to the App launcher.
Documentation update:
Since there's no explicit mention of this in the official documentation, I requested this to be added to the support document Customize Google Workspace Dashboard for your users (bottom section Using Dashboard or App launcher), and also reported in Google Issue Tracker:
Workspace add-ons cannot be added to App launcher; add explicit mention to documentation
Related
I have published a Google Apps Script as a web app. Because the URL is not so nice, I have included the script in an iframe on a site with a nicer URL. I have included the corresponding option so that it works at all. Now this web app should only be accessible within the Google Workspace (formerly known as GSuite) I am working in. This setting can be done when publishing the Web App. The problem is, however, that some users (by far not all users!) in our Google Workspace cannot access the Google Apps Script that way. There is a error message saying that Google prohibits the connection.
It seems like the authenticiation does not work "through the iframe". Interestingly, the problem only arises when
the script is embedded in an iframe (the direct script URL by Google works for the users)
the script is restricted to the Google workspace.
Chrome is used (the issue does not happen with Firefox)
It is remarkable that for most users in our Google Workspace the issue does not appear. We had similar problems when including the script on a Google site (which, in the end, is also just an iframe), but with less users experiencing the issue. I have already made sure that the users are only logged in with their Google Workspace account (no other account which has no permission). In Inkognito mode the same happens.
Can someone explain this behaviour? And how to fix that (without changing the framework)?
I have been in contact with the Google support. If I remember correctly, this kind of authentication will be deprecated and should now be done with other tools, for example Google's Firebase Auth.
First, I know there is a similar question but it is very old and that answer is not valid anymore.
I am working on a Google Apps Script web-app (either bounded to a Sheet, or a stand alone one that'll reference a Sheet). I am wondering if it is possible to publish it to the G-Suite Marketplace? All of the documentation I am finding talks about publishing add-ons and what not.
I saw this, and many articles/post link to it saying that is how, but it says publishing to the Chrome store is deprecated.
But I can't find anything on publishing a GAS web-app to the marketplace. Is it possible?
Answer: No
I know this hasn't been explicitly written anywhere but I'm taking my cues from the following docs -
Choosing where to publish - here they describe what can and cannot be published on G Suite Marketplace (albeit, Web Apps show-up nowhere)
G Suite Marketplace SDK > Configuring the Marketplace SDK > Extensions - here too, they haven't listed Web Apps as a form of accessibility
Hope this helps! Plus, I've built a fair amount of web apps myself and have always wanted to get it listed somewhere but haven't been able to do so - yet :)
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 ?
I have a Google Apps Scripts web app and I would like to publish it on the Google Apps Market Place. I followed this instruction (https://developers.google.com/apps-script/guides/domain-wide-web-app) to properly setup the Apps Market Place SDK but I have some troubles.
To test installation flow I use the button in the setup page of the API, so :
My issue is if a user install the app as I allow personal install
The user validate rights and after he is redirected to the application. There I have an issue because the apps script web app request a "Offline access" in a new pop up.
=> I don't know how to add this scope because I don't find any scope for this need to add in the market place SDK setup.
What I found on stackoverflow is I probably have this message because on scope request by apps script web app there is the approval_prompt parameter set to force.
My question is how to avoid that and allow user to connect to app after validating scope on the apps market place ?
Thank you,
Stéphane
You can follow the List of Best Practices
Before you publish your Google App Marketplace application, please review the following list of best practices. Adhering to these best practices will help your application make it through the Google Apps Marketplace review process smoothly without you needing to make additional changes.
This document explain:
3: Define your scopes properly
All OAuth2.0 scopes must be defined in the Google Developer's Console, in the Scopes section of the Google Apps Marketplace SDK. This is essential in order to achieve one-click or zero-click SSO, as described in the following section.
According to this previous question, in the Admin Conso
I'm trying to publish a Google Docs addon, visible only to my Google Apps domain, and then automatically install it for everyone in the domain
I have:
made a script in Google Drive, shared it with everyone on the domain
deployed it to the Developer Dashboard using Publish -> Deploy as Addon, with Publish in Google Apps Marketplace turned OFF
pushed it from the Developer Dashboard, making it visible just to users of my domain, giving it all the necessary fields and images
verified that others from the domain can install the addon by going to Addons -> Get addons in a Google Doc, toggling the filter to For mydomain.com. Also verified that it works when installed that way.
created a new project in Google Developers Console, added Google Marketplace SDK and created an OAuth2 client id
I'm stuck on the step of "configure Marketplace SDK", specifically the project key for the Docs add-on extension option in it, where I'm consistently getting a Project Key is not associated with current project. error.
I believe I need to finish this step, so that I could then re-do step 2 with Publish in Google Apps Marketplace turned ON, and then finally enable it for everyone.
Steps that shouldn't affect things, but might be worth noting:
I am not the owner/admin of the domain, but the admin is assisting in steps where I get stuck. (like creating the OAuth2 client id)
I have transferred ownership of the Developer Dashboard entry to a group that I'm owner of (on the desired domain)
I have transferred ownership of the Developer Console project to that same group
the problem was I manually created a project in Google Developers Console
instead, I should've used the Resources -> Advanced Google Services -> Google Developers Console link to access a HIDDEN PROJECT (?!) and enable Marketplace SDK there.
sigh.