Connected Tables across Realms

Yes. You can make a Sync table connect to a different Realm.

Hi Mark,

I'm writing to this topic, as I would like to implement same solution for our Customer. Customer is holding its own app, we would like to create connected table to our app.
As per your previous reply I understand that is possible to create connected app between two different companies.
Each time we try, same error occurs - Invalid token.
We are trying this the same way we are connecting tables within same company (that works perfectly), but in this case simply does not work.
Are there any additional permissions/setup steps needed or different levels of QB subscriptions could be behind - in short, is there anything that could prevent connected tables to work between two companies? 

Does the user token have access to the source app?

I'm sorry, I don't understand the question. Can you please explain a bit? Are there different types of tokens?

When you set up a Connected table in Quick Base, like all things Quick Base security comes first.  So the connection will be running under the security credentials of a Userid.  Those can be supplied in the Sync setup screen by a userid and password, but then if the password is changed on that userid the Sync will fail.

So a better practice is to go to the Source App in the userid that owns the connection and then at the top right of the screen and click on the name and then My Preferences and Manage User Tokens, and set up a user Token or add to one that exists to authorize that token (a long string of characters) to access that source app.

That is the token that would be used in the Connection.

I understand. this is another way to setup the token, but token related to particular user - correct?
Would that mean that I must have access to the customer's APP too, to be able to see data in my QB?
Cant we setup connection that will work to all the users of my app without having access to the customer app?

 Here is how we setup token and tried to create a connection using authorization type "User Token" only.

The single userid which owns the Connection must have access to the Source app in order to access that data and load it into the target app.  

Once the Sync runs and the data is in your own app, then regular permissions apply and regular users do not need to access the Source App.

Many thanks Mark!
Will have another session with the Customer tomorrow and chance to test it.

Will make sure to let you know if worked.

Hi Mark,

Just to let you know, it worked!

Many many thanks for your help!