Introducing AppSheet User Pass

It’s not working. If the domain already belongs to another workspace account or if it’s not possible to take control of the domain, we can’t assign that domain in the cloud identity. A lot of them already got workspace, some are using regular gmail account or other services to login, like microsoft, apple or others. I’m not able to assign these users.

Would be great to assign external users to other custom user we could create with cloud identity :

ex.:
let’s say a user connect with : userA@gmail.com
we need to assigne to : userA@ourdomainwemanage.com

Is there something I am missing?

You cannot assign licenses to external users in the Workspace Admin Console. The procedure I described above is to create an internal account for the user of another organization. You can then assign an AppSheet license to that internal account so they can build and share apps in your environment. You could also follow this procedure from the opposite direction, with the external user creating an account for you in their organization, assigning a license, etc.

1 Like

Thank you for your reply, and sorry for the confusion. :slightly_smiling_face:

To make it simple, how do I create an internal account for the user of another organization that we don’t manage. This is the part I am missing because I see only my domain from the dropdown and we can’t add a domain we don’t own or has another Google workspce but I might be at the wrong place…

You are creating a new account for that user with your own domain. Lets say that you own acme.com and the external user is from cymbal.com. You are creating a new account under your own domain (e.g., external-user-123@acme.com). They can then login to that new account and use your apps. This account is separate from their cymbal.com AppSheet account. It is not possible to link AppSheet accounts from across Workspace organizations. Please review the documentation for more information.

2 Likes

I understand, Thank you!

If organization A have a paid Workspace license , and organization B also have a paid workspace licence,

Can Org B use appsheet app created by Org A without being cosidered an external user? Both orgs being appsheet core licenced

3 Likes

Thank you for your reply!

Let me confirm your explanation meaning.

Scenario:
We have two organizations, A and B, each with their own Google Workspace (GWS) accounts, including AppSheet Core licenses. Their domains are @companyA.com and @companyB.com, respectively.

What happen: (please correct if I am wrong)
If companyA want to use their appsheet app with companyB, you need to pay another license fee or user pass for company B even though they both are already paying GWS account fee including Appsheet core.

Your Suggestion :

  1. Make new companyB user account inside companyA GWS via Cloud Identity Free; companyBuser@companyA.com
  2. And you can’t assign them GWS license or appsheet license to let companyBuser@companyA.com use the app without paying another GWS or license fee for companyBuser.
  3. At the end, companyA should pay double GWS fee for companyBuser even though companyB is already paying GWS fee only for use appsheet app together.

This licensing model creates a significant barrier to collaboration between organizations using AppSheet.

It’s analogous to requiring an additional Google Workspace fee to share a Google Doc between two organizations – which is not the case. The ability to share Google Docs, Sheets, and Slides seamlessly across organizational boundaries is a key benefit of GWS.

Requiring duplicate licensing for AppSheet significantly hinders its adoption and usefulness for inter-organizational workflows. The Public sample is good system, but it’s not suitable for using app together.

I’m a strong advocate for AppSheet and believe it has immense potential. Its inclusion in Google Workspace was a fantastic step. However, I believe that removing the requirement for duplicate licensing when sharing apps between GWS organizations would dramatically increase its adoption and value, both in Japan and globally.

I respectfully request that you reconsider the current licensing model for inter-organizational AppSheet app sharing and explore options for making this process free of charge, similar to other GWS applications.

Thank you for your time and consideration.

5 Likes

@alafontant , @zito

I fully support @Kawano164 's opinion regarding the new AppSheet User Pass licensing model. In the scenario he described, doesn’t the AppSheet User Pass effectively amount to double charging for licenses?

There’s definitely a legitimate need for sharing AppSheet apps between organizations for business purposes. For example, when Company A outsources work to Company B, Company A would naturally want to share their AppSheet app with Company B for progress tracking and management.

From practical experience, I know that Cloud Identity is not a viable solution in these cases for several reasons:

First, many Google Workspace administrators are unfamiliar with Cloud Identity. Even if they are aware of it, do they truly understand the differences between Google Workspace and Cloud Identity? When we suggest implementing Cloud Identity to these administrators, they’re likely to resist or be hesitant.

Second, if the use of Cloud Identity is rejected, it’s unreasonable to expect organizations to accept additional charges through AppSheet User Pass. For companies A and B working closely together with multiple apps and users, these costs could quickly become substantial.

In conclusion, shouldn’t AppSheet User Pass be limited to users who:

  1. Do not have a paid Google Workspace subscription (and therefore don’t have the bundled AppSheet Core license)
  2. AND do not have an AppSheet Core license purchased directly from AppSheet with a free Gmail account

Such users clearly don’t have any AppSheet Core license, so everyone can understand why they would need to pay to use Company A’s AppSheet applications. But charging organizations that already pay for AppSheet Core seems inequitable and creates unnecessary barriers to collaboration.

4 Likes

We understand and appreciate the feedback. The intention is not to charge users multiple times when they have an AppSheet Core or AppSheet Enterprise Plus license. We will investigate the prevalence of “inter-organizational AppSheet app sharing”.

9 Likes

Thank you @alafontant

I think this is all we wanted to know, We are not asking for something exceptional, just something that is fair.

3 Likes

@alafontant

Thank you for your response and for taking our feedback seriously. It’s reassuring to hear that the intention is not to charge users multiple times when they already have AppSheet licenses. I’m looking forward to hearing the results of your investigation into inter-organizational app sharing.

I’d like to share some practical perspectives that might help with your investigation:

In the past, I was consulted by a company with paid Google Workspace subscriptions about implementing AppSheet, specifically with the requirement to share apps with external users. Ultimately, they decided against adoption because sharing with free Gmail accounts was problematic.

For certain scenarios, AppSheet User Pass is indeed valuable. Google Workspace administrators typically resist creating new user accounts or adding part-timers and student workers to Cloud Identity, finding it cumbersome and inconvenient. However, since these temporary workers typically already have free Gmail accounts, purchasing User Passes as needed eliminates the hassle of account management and learning unfamiliar systems like Cloud Identity. Under these conditions, Workspace administrators might welcome the User Pass option.

The problem arises when organizations that already pay for Google Workspace (with bundled AppSheet Core) are asked to bear additional User Pass costs—either themselves or requesting their collaboration partners to pay. They believe they already “own the licenses,” making this concept difficult to explain or justify to them.

Construction companies and content creation studios frequently use subcontractors. There are many industries that have regular customer/vendor relationships. In these sectors, it’s natural to want shared apps for data exchange, project progress tracking, logistics, quotes, deliveries, invoicing, and more across organizational boundaries.

However, User Pass is valuable for scenarios like event management, where you temporarily need many part-timers or student workers without AppSheet Core licenses. Purchasing only the necessary User Passes and having them sign in with free Gmail accounts provides adequate security, making it attractive to event managers. Similarly, in convenience stores, restaurants, cafes, and fast-food establishments where many employees are part-timers, creating Google Workspace accounts or adding them to Cloud Identity is impractical, making User Pass a potentially useful solution.

I believe the distinction should be: if both organizations already have AppSheet Core licenses (whether through Google Workspace or direct purchase), they should be able to share apps without additional licensing costs. This would better support inter-organizational collaboration while still maintaining the value of User Pass for the scenarios where it’s truly needed.

@zito

3 Likes

I have a question here @alafontant @zito

Lets say I have on of these apps that are used annually or quarterly but I want the employees to be able to access the app whenever they want.

I have 300 employees, so I buy 300 user passes:

  • January: 35 user accessed the app
  • Feabruary: 300 users accessed
  • March: No one accessed

¿How much will I be charged on each month?

It would be great the following:

  • 31st Dec: I pay 1500$ as a deposit
  • 31st Jan: I pay 175$
  • 28th Feb: I pay 1500$
  • 31st Mar: I pay 0
  • 1st Apr: I cancel the user pasess license method and I receive the 1500$ deposit

This will give us all the flexibility we need

1 Like

Billing for AppSheet User Pass is not based on usage - it is a subscription like all other Workspace licenses. You can work with your Workspace sales representative for custom pricing arrangements.

2 Likes

Thank you for your answer @alafontant know this is not interesting for Google.

But it also means that if you have users that only access the app sometimes, if has been more than 30 days from the last time you need to buy a User Pass repeatedly.

In the way the 3rd ponit of this post you mention:

The pool of User Pass licenses resets at the end of the calendar month and unused licenses do not rollover.

That is kind of pay per usage, ¿What happen if rollover from on month to other 100 User passes and 101 users access the app?

1 Like

The payment plan is for an annual commitment though so it doesn’t matter if employees access it annually or quarterly. It’s still the same cost.

1 Like

Bear in mind the user pass licenses are pooled, so if you have 100 employees, and an app where only 20 employees a month will use it, you only need 20 licenses instead of 100.

Hi @alafontant @zito

Is this still working? Now is not on the Admin Console to buy

AppSheet User Pass is still available for purchase through the Workspace Admin Console for customers that have verified ownership of their domain. It will not be shown if you signed up for Workspace with only email-verification.

Hi @alafontant

Last time I checked, the UI was like you show on your image, but now it looks like this (image below) and doesn’t include the user pass. Even if I look “AppSheet user pass” on the search bar doesn’t show any results

1 Like

I’m a user from Japan and I actually experienced the same issue. I contacted support and they helped me resolve it.

The solution was to access the admin console using Chrome’s incognito mode. It seems like there might be a caching issue or something similar that prevents the correct UI from loading in a regular Browse session.

I hope this post helps someone else who might be encountering the same problem!

1 Like