Workspace
Workspaces allow your team to work in a shared set of projects, with shared API keys and integrations.
Workspaces allow your team to work in a shared set of projects, with shared API keys and integrations.
Switching workspaces
You can select what workspace you would like to be working in or create a new workspace by clicking on the current workspace name.
On mobile, tap the workspaces icon.
Setting up a workspace
See Workspace setup in our Quick start guide.
Once you've created a workspace, select its name or click Workspace Settings to add Members and Integrations.
Inviting members
To add someone to your workspace, go to Workspace Settings → Add/Manage Members and click Invite. Enter their email address and choose a role.
You can invite multiple people at once by entering several email addresses separated by commas or new lines (up to 50 at a time). Duplicate emails are automatically removed.
The invited person receives an email with a link to join. If they're new to Superconductor, they'll create an account first. Once they accept the invitation, they automatically see the workspace and can contribute based on their assigned role.
Members can also use the workspace's linked GitHub and Slack integrations without further authentication, as long as their Superconductor account email matches their GitHub or Slack email.
Invitations expire after 30 days. Workspace owners and admins can resend or revoke pending invitations from the Members page. Resending an invitation sends a fresh email to the invitee and resets the 30-day expiration.
Member roles
- Owner
- All privileges. Workspace must have at least one owner.
- Admin
- All privileges except creating an Owner.
- Developer
- Creating and editing all Projects, Tickets, and Implementations.
- Viewer
- Can view all Projects, Tickets, and Implementations, but cannot edit anything.
Branch naming
You can customize how Superconductor names the Git branches it creates for implementations. Go to Workspace Settings and find the Branch Naming section.
The branch template supports these variables:
| Variable | Description |
|---|---|
{username} | Your GitHub username (or app username if GitHub isn't connected) |
{ticket_number} | The ticket number in the project |
{branch_title} | A branch-safe slug of the ticket title |
{implementation_number} | The implementation number on the ticket |
The default pattern is:
{username}/{ticket_number}-{branch_title}/{implementation_number}This produces branches like jane/42-fix-mobile-login/1.
Rearrange or remove variables to match your team's conventions. The template must always include {ticket_number} and {implementation_number}.
Branch naming applies to all new implementations in the workspace. Existing branches are not renamed.
API keys
See Agent credentials for details.
Integrations
See Workspace integrations for details.
Recent activity
You can track all the implementations you're following from the Recent Activity sidebar, which is visible across your workspace. See Recent activity sidebar for details.