Growthub Apps

Use your connected accounts

Connect GitHub and configure Profile Settings → Hosting once, then review Growthub Apps → Manage and its tool permissions on your selected Claude or Codex account. Apps and Sites use the same saved hosting connection.

Choose Apps for work such as a client portal or CRM with signed-in users and protected records. Tell the Character which authorized database or backend connection to use. Hosting alone does not provide user authentication, a database or row-level access rules.

Create the application

Describe the users, the actions they need and which records each user may access. Ask for a new Project, private repository and working preview. Each distinct app stays with its own Project and repository.

Review the initial preview before connecting real customer data. For a signed-in app, test allowed and denied access with separate test users and check that one user cannot read another user’s protected records.

Build a client portal in a new Project using Growthub Apps, my connected GitHub and hosting. Use the backend connection I selected. Clients should sign in and see only their own records. Return the preview and show what I should review before inviting clients.

Continue the same work

Open the preview in the existing Browser surface beside the conversation. Use Files for the bound repository and Diff for recorded edits. Request revisions in the same Project and verify them at the saved preview URL.

Registered applications and their configured capabilities can be read through Growthub Apps. That inventory does not grant access to their customer records; each connected service remains responsible for its data and permissions.

Use a saved custom domain

Verify a hostname in Profile Settings → Domains. In the app Project’s deployment settings, choose that hostname and confirm the connection once. Reuse the current preview rather than rebuilding just to attach the domain.

After HTTPS is ready, test sign-in, sign-out and any backend callback URLs on that exact hostname. Keep service credentials in their secure connection settings and review the destination before sharing it with customers.

Keep going