Navigate the dashboard
The dashboard keeps operational resources in the left navigation and the current workspace and project near the top of that navigation.
Main areas
| Area | What you do there |
|---|---|
| Dashboard | See the current project context and a summary of resources |
| Applications | Search applications, deploy a new app, and open application details |
| Resource Pools | Create capacity and inspect pool status and usage |
| cPanel | Manage the separate free legacy-hosting accounts, when available |
| Integrations | Connect the current workspace to GitHub |
| Members | Invite collaborators and review roles and invitation status |
| Billing | Check the workspace wallet and start a deposit |
| Settings | Update your profile and configure two-factor authentication |
Switch context safely
Before a create or change action, verify both the workspace and project. A workspace controls people, billing, and integrations. A project controls where applications and resource pools are organized.
Use names that reveal purpose without exposing sensitive information. production, staging, and payments are useful context; credentials and customer data are not.
Application details navigation
An application has these primary tabs:
- Overview — source, runtime, capacity, endpoint, and timestamps;
- Deployments — release history and status;
- Logs — live standard output and error output;
- Terminal — an interactive session for an active application;
- Settings — source, build, resource, and runtime configuration.
The Open application action appears when the application has a public endpoint. Otherwise, View logs is the quickest path for checking startup behavior.
Refreshing state
Provisioning and deployments are asynchronous. Use Refresh when a state has not updated, but avoid repeatedly submitting the original create or save action. A duplicate submission can create an unintended release or resource.
Permission-aware controls
Your role can affect what you can see or change. If an action is unavailable, confirm you are in the intended workspace and ask a workspace owner or administrator whether your role includes the required access. UI visibility is not a substitute for authorization; the platform validates actions when they are submitted.