Working as a member
What an invited member sees, who dispatches runs, and how to follow the work live.
You joined an organization as a member — accepting the invitation is the only setup you do. The setup chapters in this guide — CLI and runner, projects, blueprints, credentials — are owner and admin work; none of it is required to follow along. You see the organization's work live: every project, run, and agent session. Owners and admins make the changes — they dispatch runs, drive sessions, and hold every credential. Roles & access is the exact permission table.
Your screens
Accepting the invitation lands you in the dashboard, which opens on the Control plane. The navigation gives you:
| Screen | What it shows |
|---|---|
| Control plane | The organization at a glance: active runs, projects, live sessions, recent outcomes |
| Queue | Work in flight ordered by urgency — attention first, active below, settled last |
| Runs | Every dispatched run, its status, and its detail |
| Devboxes | The containers agent sessions run in |
| Agent sessions | The live console for each run |
| Pull requests | Open pull requests, plus those reported by runs during the last 90 days |
| Projects / Blueprints / Runners | What the organization can run, and the machines that run it |
| Members | Who is in the organization and their roles |
Credentials does not appear in your navigation: repository tokens, provider API keys, environment variables, and secrets are visible only to owners and admins.
Runs start with an owner or admin
An owner or admin dispatches runs — from the dashboard, the CLI, or Slack. When you need work dispatched, hand the task to one of them; the Members screen shows who holds those roles. From the moment it is dispatched you follow it live: the run appears in Runs and Queue, its container in Devboxes, and its console in Agent sessions.
Follow a run and its session
A run's detail shows its status, project, blueprint, who dispatched it and when, its duration, its pull request link once one is reported, and its token and estimated-cost usage.
The live view is the agent session console: the Transcript tab streams the agent's messages and tool calls as they happen, Terminal shows command output, and Review shows every file the agent has changed. You open the console read-only — the session controls and the composer are disabled, and the decisions the agent asks for are answered by an owner or admin.
Feedback and support
Feedback / Support sits at the bottom of the navigation on every screen. Your message goes to the Devboxes support team with the current page included automatically, and replies reach your account's email address. If the notification fails, your message is still saved and the dialog offers Retry notification. Contact support lists what to include.
Next: Configuration — the unified CLI, runner environment, and config reference.