Skip to main content
Visibility is what separates an app from a live app. By default, custom-built apps install with conservative visibility — internal users see them, clients don’t, until you change that.

​
The two visibility scopes

Every app has two visibility settings: Internal-only apps only have the internal scope. Client-facing apps have both.

​
Internal visibility

By default, every internal user sees every installed app in their Dashboard sidebar. You can scope this down two ways:
Show the app to admins only, or to admins and staff. Useful when the app exposes configuration or sensitive actions that staff shouldn’t see.

​
Client visibility

Client-facing apps default to hidden from clients. You make them visible explicitly. Three patterns:
Every client in your workspace sees the app in their Portal. Default once you turn it on for clients.

Custom visibility for apps

Full configuration in the Assembly Studio guide

​
Hiding without uninstalling

If you want to take an app offline temporarily — for maintenance, for a redesign, for a pause — set visibility to no one rather than uninstalling. Hiding preserves the app’s data, history, and configuration. Uninstalling removes it. Unhide when you’re ready and clients pick up where they left off.

​
Visibility during build vs after build

You can set visibility either way:
  • During the build: tell the app builder during the planning step. “This app should be visible only to admins” or “Only the Onboarding Cohort companies should see this.”
  • After the build: open the app’s settings and adjust visibility there.
The during-build path is faster when you know up front. The after-build path is more flexible when visibility evolves with the app.
When in doubt, launch narrower than you think you need. Expanding visibility later is one click. Shrinking it after clients have already started using the app is awkward — they’ll see it disappear from their Portal and ask why.