Builder settings
The workspace-level Builder settings — terminal preferences, AI assistant, GitHub, billing and usage, the nine team permissions, and the danger zone.
Builder settings are workspace-level, not per project. They cover how the terminal behaves, the AI assistant, where GitHub is configured, usage, who on your team may do what, and the destructive actions.
Open them from BuilderSettings, then use the left navigation.
Before you start
GitHub and the danger zone need owner rights. Non-owners see GitHub as read-only, with a line saying the account owner configures it.
The sections
| Section | What is there |
|---|---|
| Terminal | Terminal preferences for the workspace |
| AI Assistant | Assistant configuration for Builder |
| GitHub | A pointer to the real place — the GitHub tile in Settings → Integrations |
| Billing & Usage | Builder usage for the workspace |
| Team & Access | What the current member may do, as a read-only list |
| Danger Zone | Destructive workspace-level actions |
GitHub is not configured here
The app install, repository access and secrets all live on SettingsIntegrationsGitHub. This section exists to point you there so two places can never disagree about which installation is current.
Team and access
Nine permissions decide what a Builder member may do. The list here is read-only — it reports what you hold, and an owner changes them where team permissions are managed.
| Permission | Allows |
|---|---|
| Terminal | Opening and using terminal sessions |
| Git push | Pushing commits |
| Create branches | Creating branches |
| Pull requests | Opening pull requests |
| Deploy | Triggering deployments |
| Manage env | Managing environment configuration |
| Manage backups | Creating and restoring backups |
| Components | The Components panel in a workspace |
| Local SEO runs | Letting a machine execute tenant blog drafts when one is assigned |
Local SEO runs is the one people forget
It is not about viewing SEO. It is the permission that lets an assigned machine run tenant blog drafts. If drafts keep waiting even with a bound desktop open, check this before you check anything else.
A missing permission is shown honestly rather than hidden — Components (no access) appears in the workspace rather than the panel quietly disappearing.
Billing and usage
Billing & Usage reports Builder usage for the workspace. Note that spend on research and AI runs is metered in two other places: the SEO Command Center's own monthly budget per website, and each research target's monthly ceiling. Neither is managed from here.
The Costs dashboard is not yours
Automations → Costs, reached from /builder/costs, is platform-operator
only. Non-operators are redirected to Activity. Use
Settings reference for the budget controls you
actually own.
Danger zone
Destructive workspace actions live at the bottom of the navigation, behind owner rights. The roster has its own destructive action — Delete projects in the bulk toolbar — which is separate and equally permanent.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| GitHub is read-only here | You are not the account owner | Ask the account owner to install or repair it in Integrations |
| A permission row reads as unavailable | You do not hold that permission | Ask an owner to grant it |
| Blog drafts wait despite a bound desktop | The machine lacks Local SEO runs | Grant that permission to the assigned machine's account |
| Usage here does not match your research spend | Research is metered per website and per research target | Check the monthly SEO budget and the target's ceiling |
| Danger Zone actions are unavailable | They need owner rights | Ask the account owner |