Publisher Pro Admin

AppSheet AppSheet Q&A
1

I need to understand if my logic is wrong here and my expectations in Appsheet.

I understand the Publisher Pro approach to make the app public facing with non sensitive data, basically allow users to browse some products and get information as well as submit a quote request with some cool calculations and send them a PDF, all self service…

But then due to the account licensing now only locked to Per app licensing I was wondering, would it not make sense that the Owner/Admin of the app have a way to seperate public users and admin login just to control the edit buttons for example. Obviously only the owner can login using usually authentication. Or perhaps allow that owner can build one additional app to manage and edit the data used on that Public app inside an Appsheet app itself.

In some cases a team mat want to use appsheet to control invoicing and quotes based on orders placed from the Publisher Pro App. Again each user could be license using Core as minimum…

My client is happy that it all is accessible to public but wants to know why he needs to change things manually on sheets or create a Seperate account to that shared datasource and then there build an app to be able to edit what is seen on the public facing app..

I never thought of this and it is strange that for that price per month at least allow the license to build one more normal app to control his data in appsheet…

@MultiTech

Maybe you have a simple answer to approaching this thing logically …

excited-baby.gif

1 Like
2

There is technically no limit to the number of apps that can be connected to a single Google sheet or data source, which means you can create a separate admin app to manage things connected to the same data source as the public app.

This is actually how I have the Answer Portal set up. Here’s the breakdown:

  • The public Answer Portal is a publisher pro app, that’s slimmed down and only contains the necessary stuff for showing resources and allowing people to do basic functionalities.
  • The private Answer Portal is on a core license, and that’s the one that I use to manage everything. (This is also the one that I give access to for my apprentices, and we use it to manage meetings and everything.)

The real fun thing is that you can use automation to send something from the public app directly to the private app, like a manual automation trigger, literally triggering something in the private app from the public one. They are both connected to the same data source, so as soon as someone saves a record in the public app, when I refresh the private app that record is now visible.

This really does give you the best of both worlds; and aside from a little duplication of work (in the form of duplicating new columns when I add them, and other data restructuring activities), this is a very smooth running system.

==============================================

Your instincts were correct @Denzil_Snyman in that you need to create a secure app in order to actually manage things appropriately. :flexed_biceps:

1 Like
3

Thanks Matt, so I would imagine you are running them on seperate accounts. One for the publisher Pro and the other for the Core license…

May be I need to put feature request in and wait a few years, that’s if considered :joy: , to allow a Simple admin login button that gives the Publisher pro owner the the ability to login securely and use certain action conditions. I can visualize not using or needing the Useremail() which is disabled but rather allow a simple way to specify if an action is for guest or owner as I beleive they track this..