Choose the audience
Decide whether the application is for workspace members, a specified audience, or public visitors. Use the access controls offered by the hosted-app surface. Test with a visitor who should be denied as well as one who should be allowed.
Use the current hosted address
Spinrun's hosted applications use the supported Spinrun application domains. Copy the address from the product rather than inventing it from an application name.
Custom domains require confirmation
Customer-owned domains are not enabled for the current hosted-app pilot. If your project depends on a custom domain, contact the team about availability before promising that address to users.
Review links and collected data
Check that public links do not reveal private records and that any sign-in requirement is applied to direct routes too. Keep a clear owner for access changes and for removal when the application is no longer needed.
Open the relevant screen
Use Space access and domains 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.