Gsuite Add-on: can a user also (individually) remove an add-on when individual install is enabled? - gsuite-addons

We have enabled individual install for a newly developed Google Forms add-on.
An individual user can install the addon, but cannot uninstall/delete this add-on once they decide they no longer need this add-on. Is this common behaviour?
When the user searches for this Marketplace app they will see the 'delete' button, but this button is not active
Extra info:
the add-on (marketplace app) is whitelisted in our Google domain

Enabling individual install allows a user to remove an Add-on he previously installed himself.
Enabling individual install does NOT allow the user to unistall an Add-on that has been installed domain-wide by the admin.
If you want the user to decide himself either he wants an Add-on or not, you as an Admin should not install an Add-on domain-wide - be it your own or a commercial Add-on.

Related

Can't create GitHub account

I want to create a GitHub account, but something is blocking me from doing that
As you see, it's asking me to do captcha test over and over again.
Should I report this as a bug? is this also happening to you?
I suggest to wait some minutes and try it later. Or you can just try to do the following steps:
Ensure JavaScript is enabled on your browser.
Ensure your browser is supported. If your browser isn't supported, upgrade your browser or install a supported browser. For a list of supported browsers, see "Supported browsers".
Ensure your network configuration is not blocking https://octocaptcha.com/ or https://arkoselabs.com/. If you're behind a corporate firewall, contact your IT administrator to allow those domains. To verify access to these domains, visit https://octocaptcha.com/test and ensure the text "Connection successfully made!" is displayed, then visit https://client-demo.arkoselabs.com/github and ensure you are able to load the captcha.
Ensure your browser does not have plug-ins or extensions that may be interfering with GitHub. If so, temporarily disable the plug-ins or extensions during captcha verification.
Otherwise everything works according to the status page.
In Debian: apt install epiphany-browser
It just bypassed github's signup "barriers" in a way that fresh installations of Firefox ESR / Firefox latest / Chromium... in Debian, Windows, Android... could not!
I tried many times, but I couldn't create an account on Github. After that, I tried to create an account on GitHub using my mobile google chrome, then I successfully created an account in Github. Thanks.

What is the correct way to share gsuite add-on with external users without publishing to Marketplace?

Using a company domain gsuite account, I have successfully deployed a gsuite Google Docs add-on for my company domain using the G Suite Marketplace SDK, but I have some users that are outside of the domain e.g. part-timers, contractors etc. who are using their personal name#gmail.com accounts. How can I share the add-on with them to install?
In G Suite Marketplace SDK > Publish, I have this App URL, but it gives error 400 so I don't know where to go next.
https://gsuite.google.com/marketplace/app/appname/<project number>
Unfortunately, you will need to publish it to the Public for anyone outside your domain to install it.
Here is some more info:
https://developers.google.com/gsuite/add-ons/how-tos/publishing-gsuite-addons#step_4_configure_the_marketplace_sdk

Why does our g-suite marketplace installed app not get the appropriate scopes?

We published our app via the G-Suite marketplace.
Admins can install the app domain-wide for users to access and they are asked at that time to approve all the scopes our application needs.
When users in an domain where the app is installed try to use features that integrate with Google - specifically fetching classroom data - they are not prompted to give us access to the data we request and yet the scopes are not requested from that user.
If the user does NOT have the marketplace app installed on their domain, they are simply prompted to grant access to the data and can continue.
To workaround this we removed all the requested scopes from the marketplace listing, and now users in a domain with the app installed are asked to approve scopes individually when we request them.
However, the G-Suite marketplace documentation specifically says that we are supposed to avoid having to ask users individually to grant scopes, so this seems wrong.
Has anyone else run into this issue and found a solution?

Email control panel

Most of my small customers started to ask me if I can host the websites I'm building for them. Setting up virtual hosts, configuring mysql, DNS, etc is not really a problem. One thing stops me from hosting their websites is the fact that I've never been able to do configure an email server to accept multiple domains with SPF&DKIM. There must be some sort of an evil spirit which stops me from achieving this.
So, I was wondering if anyone knows a piece of opensource (or not, I'm willing to pay a decent license price ) software ( cpanel like but limited to email ) which would allow me to:
Manage only email related things via a control panel.
The control panel should let me add multiple domains.
The control panel should let customers login and manage their mailbox accounts
The software should offer webmail and SMTP & IMAP/POP3 access.
P.S.: I work mostly with ubuntu but I can handle centos also.
I don't have an answer to your question, but I have an alternative : Google Apps.
You can do the web hosting and tell your customers to get a Google Apps account for their email.
Also since Google Apps is no longer free, you can try Google Domains, they do not offer email hosting but they can redirect up to 100 domain email to gmail accounts.
I think you should go with CentOS Web panel. It is a free and open-source web hosting control panel for CentOS Servers. It provides a powerful web interface through which you can manage your CentOS server and its services. With Centos web panel, you can manage User accounts, Apache virtual hosts, DNS entries, MySQL databases, Email accounts, and much more. Apart from it, CentOS web panel is also used to create and manage shared hosting servers.
Below are the steps on how to install CentOS web panel on CentOS Server.
1. Preparing Server
Let’s install the required packages for CWP installation:
# yum -y groupinstall 'Development Tools'
# yum -y install epel-release
2. Server Update
Now we need to update your server to the latest version
# yum -y update
3) Reboot Server
Reboot your server so that all updates can take effect.
# reboot
4) Download and install CentOS Web panel:
# cd /usr/local/src
# wget http://centos-webpanel.com/cwp-latest
# sh cwp-latest
Note: The installation process may take 30 - 40 minutes because it needs to compile apache and PHP from source.
Once the installation is completed, a list of credentials will be appeared to access the panel. Make sure to copy or write down the MySQL password and press enter to reboot your server.
Please let me know if you face any error. I will happy to help you.

How create an installer of chrome packaged app?

I need to demonstrate a test version of my app. I DON'T want to load it to the store yet. I want create an installer of my app, so the user can go to my site and install the application by clicking.
First of all, have you read the documentation including developer installation, enterprise installation, publishing on the Web Store only to test accounts, and recent announcements of changes? Assuming you have, then with the exceptions listed in those sources, all apps/extensions must be published in CWS. They don't have to be listed publicly, but they do have to be published there.
Your best bet is to use the test-account feature of CWS for your demonstration.
This is very easy, yo can create the installer vía chrome://extensions > Developer Mode > Package extension.
Then you got the .crx file, you can upload it anywhere and share it. To install it, user must open chrome//extensions and drop the file in the page.
The option to install from webpage by clicking was disabled in Chrome for security reasons.