I signed in and ShareBase says I have no access
Signing in with Google proves who you are; it does not put you in a workspace. Until an admin adds your email, there is nothing for you to open, and the no-access screen is where you ask for that. Use the request button there, or send your admin the email address you signed in with — it has to be the same one.
How do I get somebody into my workspace?
Invite them by email from the workspace. They can be invited before they have ever opened ShareBase; the invitation is waiting when they first sign in with that address.
Do the apps I deploy need their own login screen?
No — and asking for one is the most common mistake. Whoever opens your app has already signed in to the workspace, and the app is told who they are. There is nothing to build: no login screen, no sessions, no list of users to keep, and each person still sees only their own things. Your agent is given the details it needs for that when it connects.
Who can open an app I deployed?
You, and whoever you shared it with — a named person, or a whole email domain. Access is enforced before a request ever reaches the app, so an unshared URL is not a secret URL: it is a closed door.
Sharing and unsharing take effect immediately. Nothing is rebuilt and nothing is redeployed; the next request is simply decided the new way.
How do I share with a group instead of one person at a time?
Put the apps in a folder and share the folder. Everyone it is shared with can open everything inside it, including apps you add later and apps in folders beneath it. That is what folders are for.
A colleague wants to change my app
Have them make their own copy rather than granting edit rights. The copy gets a new URL and none of what you saved in yours, and your original keeps everything it had. Secrets and data-access grants are never copied — the new app asks for its own, which is the point: two people end up with two tools instead of one tool with two owners.
Where do API keys go?
In the vault, one set per app. Store a key there and the app can use it; once stored, nobody can read it back out — not you, not anyone you shared the app with — and it never turns up in the code or in a build log. This is self-service: no approval, no ticket.
I deployed something broken. Can I undo it?
Yes. Ask for the deploy history and pick the version to go back to; it is live again in seconds. Anything deployed since ShareBase began keeping version history comes back exactly as it was. A few very old deploys are from before that and can only be rebuilt, so they may not come back quite identical.
Can an app read company data?
If an admin has written a rule for that data domain, yes. Ask for the list of connectable domains first, then request the one you need: the answer is decided by policy the moment you ask, and it is either approved or denied. Nothing is queued and nobody is waiting to review it — a domain no rule covers stays denied however many times it is asked for.
Once a domain is approved, deploy the app one more time. Until you do, it will still see nothing.
My agent cannot connect
The MCP guide has a section for that: connection troubleshooting. The three usual causes are a URL that does not end in /mcp, a revoked API token, and a client still showing the tool list it cached when it first connected.
None of this is my problem
Write to [email protected] and tell us what you were doing and what happened instead. If it involves a specific app, include its name — it makes the answer far quicker.