Get API key

App Central

View as Markdown

Publish one app running in your workspace to the people you choose, without opening the workspace to them.

Note

PrivateMind turns App Central on per organisation. If your Workspaces page has no Apps tab, it isn't on for yours yet. Your organisation admin can ask your account team.

App Central lets you publish one port of a workspace under a name and choose who can open it. The workspace stays as private as it was, and publishing doesn't restart it or change anything inside it.

Use it when you want to show someone one app without handing over the workspace. A port preview opens only for people who can open the workspace itself, and they also get its terminal, its notebooks and its files.

Say you have a Streamlit dashboard running on port 8501. You publish port 8501 as Risk dashboard, choose your risk team as its audience, and send them the link from the Apps tab. They get the dashboard and nothing else.

Where it lives

Open Workspaces, then Ports… from the … menu at the end of your workspace's row. Each listening port has a share button that opens Publish port N, where you give the app a Name, an optional Description and an audience. The same button edits the app later.

The Apps tab of the Workspaces page lists every app you can open, with buttons to copy its link and open it. An organisation admin can list every app in the organisation there, with its owner, its port and a count of who it's shared with, such as "Shared with 2 people and 1 team".

Who can open it

The publish dialog offers three audiences:

Audience Who can open the app
Private You, and your organisation's admins. On a personal workspace, you alone.
Specific people and teams The people and teams you name.
Everyone in the organisation Anyone in your organisation.

Here, your organisation's admins are the people the Workspaces page calls compute admins. A personal workspace can only publish as Private, and admins can't open its apps either.

Whoever you choose gets that one port: not the workspace's terminal, notebooks, files or other ports. You can only name people and teams in your own organisation, and nobody outside it can open the app. It is never a public link.

Your visitors don't need compute access. Without it they have no Workspaces entry in their menu, so send them the link. They must be signed in to PrivateMind first, because the link doesn't take them through sign-in.

Only the workspace's owner and your organisation's admins can publish, edit or unpublish its apps. People the workspace itself is shared with can't. On a personal workspace only you can publish or edit, though an admin can still unpublish.

Every app has a link of this shape, and the Apps tab copies it for you:

Text
https://privatemind.com/apps/<org>/<link-name>

The link name is made from the name you type: lowercase letters, numbers and hyphens, up to 30 characters. Name an app Risk dashboard and its link ends in risk-dashboard, as the dialog shows while you type. The link holds only your organisation and the link name, so no two apps in the organisation can share a link name. Renaming the app later doesn't change the link, so links you've handed out keep working.

Opening the link takes your visitor to the app on the workspace address, ws.privatemind.com, and their browser signs them in there through privatemind.com without asking them anything. Apps open on this separate address so the code in your app's pages can't use the PrivateMind app or its API as your visitor.

An app is up while its workspace is running and your server is listening on the port. Otherwise the Apps tab says why: Stopped when the workspace isn't running, Not running when nothing is listening on the port, and Workspace deleted once the workspace is gone.

An app that stays down for seven days is unpublished automatically. Until then the Apps tab shows its owner and your admins the removal date, and serving again before then keeps it.

A published app belongs to the workspace's home volume, not to the workspace. If you delete the workspace, launch a new one on the same home volume and start your server again, the app is back at the same link. Its preview link changes, so if your server needs a root path, start it with the new preview link. If you don't launch another workspace on that volume within seven days, its apps are unpublished then. You can unpublish them sooner from the Apps tab.

Taking access back

When you unpublish an app or take someone out of its audience, anyone who has lost access is refused on a new visit within about half a minute. A page they already have open loses its live connection within about a minute. To cut everything off at once, stop the workspace.

Before you publish

Your server runs as you, inside your workspace, with your files, your network access and the secrets attached to the workspace. Your visitors get whatever it does with them. They never see a secret's value unless your app shows it to them, and an error page that prints a database connection string, password and all, is the usual way that happens. If secrets are attached, the publish dialog names them and asks you to confirm each time you widen who can open the app.

Your server isn't told who a visitor is: PrivateMind passes it no name, email or role, so an app that needs to know must ask for it itself.

A development server with its debugging console on can let visitors run code in your workspace, so turn the console off before you publish. A static file server started in your home directory serves your whole home directory, so start it in the folder you mean to share, as in python -m http.server 8000 -d site.

Limits

  • A workspace can publish up to eight apps, one per port.
  • An app's name can be up to 60 characters and its description up to 200.
  • Some ports are reserved for the workspace's own tools and can't be published. The Ports… list leaves them out.
  • An app is served exactly as a preview is, so a server that works in a preview works here. A server that builds absolute URLs, FastAPI's /docs page for one, needs its root-path setting, and Vite and Next dev servers aren't supported. See Port preview.

For organisation admins

An org admin can turn App Central off at any time from the Workspaces card in Organisation Settings (see Org settings), but can't turn it on. When it's off, new visits to every published app are refused within about half a minute, and the Apps tab disappears. Pages visitors already have open lose their live connection within about a minute. Nothing is deleted. Only PrivateMind can turn it back on, so ask your account team, and every app is published again with the audience it had.

In the audit log

Your organisation's audit log records each app being published and unpublished, and each time someone opens an app through its /apps/ link. A refused or failed attempt isn't recorded. The actions are workspace_app_published, workspace_app_unpublished and workspace_app_opened.

Troubleshooting

"an app called '…' is already published in your organisation; pick another name". Another workspace in your organisation already publishes an app with that link name. Choose a different name and the link follows it.

"an app called '…' is already published on port N of this workspace; pick another name, or unpublish it first". You already publish an app under that name on another port of this workspace. Give the new one a different name, or unpublish the first.

The app shows as Stopped. The owner needs to start the workspace and then the server again.

The app shows as Not running. Start the server again on the same port.

Where next

  • Port preview: opening a server for yourself, and which servers need a setting to work behind a preview or an app.
  • Workspaces: sharing a whole workspace, for when people need the terminal and the files too.
  • Secrets: what gets attached to a workspace, and who can read it there.
  • Audit logs: where publishing and opening apps are recorded.