I want to be able to share the User table between several Backendless apps, so the same user can be related to objects in all of the apps.
It's impossible to share anything between applications in Backendless.
The only thing you can do is to export and import the table from one app to another.
Related
Problem
I have two seperate apps, a "Manager" app and an "Employee" app which share a database, and I am using Firebase for auth. Currently I have two different projects in Firebase, one for each user type. I am now trying to develop a third "Admin" app that allows someone appointed by the organization to manage users on both the "Employee" and "Manager" apps. I have looked into using custom claims but in order for this to work across both apps would have to be on the same Firebase project.
Potential Solutions
Migrate all users to the same Firebase project
In this case, I migrate all of the users to one Firebase project and would assign a type to each user. Upon login, I would check if they are of the right type for that application and log them out if they are not - it's a bit hacky but workable
Switch auth providers
Obviously the most tedious and costly option that I would like to avoid if possible
Can anyone help me figure out the best approach here?
Since all three apps seems to work within the same domain, it'd be most common to set them up in a single project and use custom claims, security rules, or a combination of both to control access of the various user types.
Currently, on my cloud project, I have one database which contains kinds. My question is it possible to create another database that can have different kinds?
Illustration for current database
Currently, it is not possible to create another Datastore database in a single project. A workaround could be using separate projects and adding an authorized IAM user or service account to both projects in order to access both in their respective projects.
Also, maybe a multi tenancy strategy may allow you to customize data values for each tenant, while keeping the same data schema for all of them.
There are multiple companies using one application. So I want to have, or know if this is the best way, to create a project for each company, all this with the Firebase API, to create everything programmatically. But I think this is too difficult to do and get that structure. The truth is that the documentation about the Rest API to create projects is not very clear and I am getting lost. One of the things that I want to structure projects like this is to know how much use is made of each project, calculate requests and use of storage. But I don't know if there are other ways to do this.
It's not possible to create a new project for Firebase using the Firebase API, what is possible is to list projects, and create/list apps within an existing project using the Firebase Management API.
For monitoring usage, you can use Cloud Monitoring to assess the usage of each individual app, per service.
I am considering using FirebaseAuthentication for login authentication of my new web system.
It's like a recruitment site.
It has users seekers and companies.
The database is going to use MySQL.
When managing these two types of users, is it necessary to prepare two Firebase projects?
Or should I classify users in the database, so should Firebase projects be one?
Please let me hear your thoughts on design.
Thank you for reading.
I wanted to share with other users in my company a Google App Maker app I have been developing. When I develop the app and use Preview, my data is all kept.
But I know I can't use the preview url for other users to access the application. So I Published the app and got a deployment url I could give to other users. The problem I am having is that all documents created are gone for myself (and I assume the other users) each time I open a new window with the deployment url.
How can this be fixed. I am thinking there is something silly I am missing or doing.
I experience the same issue, but I think this is because when using Google Drive Tables, they are local to the app instance. So your development app tables are not the same as the published app tables. Also, if you Published your app twice, it would be 2 different sets of tables (I think). There is a way to import/export data, so you may want to export the data from your development tables and import to your published tables.
Google App Maker Import and export data