Hi, I am on an account with collaborators. I had the app builder build an app. I want the collaborator to work on it internally, it’s saying that it has to be published for her to work on it with me…is this true? Am I missing something? I don’t want this app to be published - it’s for internal use only with sensitive data. I went round and round with cuppy trying to create a password protection page that kept crashing. Why can’t the collaborator just see what I am seeing internally inside of teable??? Note - I added her as an editor not a creator, but I could change that.
1 Like
Hi Devon,
Good question. Here’s what’s going on:
For internal collaboration (without publishing):
Change your collaborator’s role from Editor to Creator. Creators can access the app in the preview environment inside Teable, so she’ll be able to see and work on the app with you — no publishing needed.
About publishing:
Publishing is required for the app to actually run as a standalone application — it generates the live URL, activates routing, and enables the app runtime. The preview inside Teable is a design/build view, not the full app experience. So this isn’t an artificial restriction, it’s how the app gets “turned on.”
About password protection:
Sorry about the trouble with Cuppy on that. Here’s a cleaner approach:
-
Create a new table (e.g. “Credentials”) with two fields:
-
Username(Single Line Text) -
Password(Single Line Text)
-
-
Add the login credentials you want — one row per user.
-
Then in App Builder, prompt the AI with something like:
“Please help me set up a username and password login for this app. The username and password credentials are stored in the ‘Credentials’ table. Only users with a matching username and password should be allowed to log in to the app.”
This way the app checks against your credentials table and gates access through a login page — keeps your sensitive data protected.
Let me know if you run into anything else.
1 Like
It would be great if we could just add this as a feature to the app, the platform will be able to save Tokens, since a lot of us need this for our apps, we wouldn’t waste time implementing the exact same solution over and over (for every app, for every user, for every base…)
Plus it would be a nicer experience in terms of data safety, during development I’ve had to have sensitive data published 
1 Like
Hi @Synergetic , what you suggested is already on our roadmap. We’ve listened to your feedback, and this was included in our latest changelog: New App Builder Engine is now in beta.
1 Like
Thanks @Gary! I saw it, pretty happy about it! 
1 Like