Define the application's job
Describe who will use the application, what data it stores, and the actions users need. Begin with the smallest useful version. Hosted-app availability depends on your workspace's enabled features.
Review before publishing
Ask for a proposal of the fields, access rules, and screens before the build is published. Use sample data for the first review. A working screen does not prove its access policy is correct.
Manage the hosted result
Open the product's Apps or Spaces surface to inspect the result and its current status. Keep the application's owner and update process explicit. Use the current supported hosting and sign-in options.
Keep external actions controlled
An application that reads or changes connected systems needs the appropriate permissions. A visitor-facing form should not gain the workspace's unrestricted credentials. Review data collection and sharing before opening access.
Open the relevant screen
Use Spaces and hosted apps in the active workspace. Sign in if needed. Check the workspace name before changing shared settings, connections, or billing.
If a control is unavailable, ask the workspace administrator or contact support. Include the screen, the action you tried, and the approximate time. Keep credentials and private customer material out of the request.