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.
Visibility controls which clients see an app in their Portal. Client-facing apps default to hidden, and you make them visible explicitly by choosing one of three options:
Visible to all people
Hidden from all people
Custom visibility
Every client in your workspace sees the app in their Portal.
No client sees it, while the app keeps working for your team. Use this while testing, and to take an app offline temporarily — hiding preserves the app’s data, history, and configuration. Unhide and clients pick up where they left off. See Organizing your apps for disabling and deleting.
Pick specific clients or companies, or build rules from tag-type custom fields. Good for pilots and for apps that only apply to certain segments.
This works identically for Classic apps, apps you build, and embeds.
Visibility settings only affect clients. Hiding an app or folder from your team’s Dashboard sidebar is a separate thing, covered in Organizing your apps.
During the build: tell the app builder during the planning step. “Only the Onboarding Cohort companies should see this” or “Keep this hidden from clients until I say otherwise.”
After the build: set it in the Publish popover before publishing, or change it any time from the App Library. See Launching apps.
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.
⌘I
Assistant
Responses are generated using AI and may contain mistakes.
