Workspaces & projects

A workspace is your team’s home in Trevize. It’s the boundary that owns everything else: the GitHub repositories you connect, your members and their roles, your billing, and the settings that govern how agents behave. Sessions, automations, briefs, knowledge, and insights are all scoped to a single workspace.

What a workspace owns

• Repositories — GitHub repos connected through the Trevize GitHub App installation. Agents check these out, branch, push, and open pull requests.
• Members — the people who can access the workspace, each with a role and a status (invited or active).
• Billing — the plan for the workspace, which sets limits such as member seats and how many agent runs can execute concurrently.
• Settings — workspace-wide configuration (below).

Identity

Each workspace has a name and a URL slug (its address). You choose both when you create the workspace; the slug is checked for availability and can be updated later in workspace settings, along with a logo.

Members & roles

Members are managed on the Members page. You invite people by email and assign a role (for example, Admin or Member); invited users appear with an invited tag until they accept. From a member’s menu you can change their role, resend or cancel an invitation, or remove them. Invites are gated by your plan’s seat limit — when it’s reached, Trevize prompts you to upgrade.

Workspace settings

• Commit attribution — choose whether commits agents make are attributed to Trevize or to the user who started the work.
• CI auto-fix — when enabled, a failing CI run on a branch from a completed implementation automatically starts a follow-up that fixes the CI issue and pushes the fix (it stops after a few attempts to avoid loops).

Related