Sinatra Docs
Configuration

Workspaces and access

Join a workspace, invite teammates, and understand shared settings, personal credentials, and billing.

A workspace connects at most one GitHub organization or personal account to Sinatra, and optionally a Linear organization and a Slack workspace. Members share its enabled repositories, task views, API keys, and billing. Personal subscription connections and repository agent preferences belong to the member who sets them.

Joining a workspace

Sign in with GitHub, or with a one-time link sent to your email. For an existing workspace, accept an invitation or request access and wait for its owner to approve it. Installing or reinstalling the GitHub App does not automatically grant access to an existing workspace.

The owner can invite teammates by email and select an admin or member role. Invitations expire after seven days. To accept one, sign in to an account that has the invited address verified: use an email sign-in link sent to that address, or sign in with (or link) a GitHub account that lists it as a verified email. An invited address that belongs to an account made with GitHub gets no email link, so sign in with GitHub instead. Adding people doesn't change the bill: each plan is one price for the whole workspace.

Creating a workspace without GitHub

Installing the GitHub App creates a workspace for that GitHub account. You can also choose Start without GitHub during setup or from Add a workspace, name the workspace, and connect GitHub and Linear later from its settings. You become its owner. Each person can own up to five workspaces made this way. Names can use letters, numbers, spaces and basic punctuation, up to 120 characters, and can't contain a web address.

Linking GitHub to an email account

An account made by email has no GitHub identity until you link one. Use Link GitHub in a workspace's Settings, or Link your GitHub account on the setup page. You need it linked to install the GitHub App on your personal GitHub account, and so that Sinatra recognizes the labels, comments and pull requests you write on GitHub as yours.

  • After linking, you can sign in with GitHub or with an email link. The email link only ever goes to the address you signed up with, not to other addresses GitHub lists.
  • Sinatra won't link a GitHub account that already belongs to another Sinatra account, and it never merges two accounts. If you signed in once with GitHub and once with email, they stay separate accounts.
  • An account made with GitHub keeps signing in with GitHub only.

Roles

RoleShared configurationPersonal settingsAccess and billing
OwnerManage connected tools, enabled repos, API keys, and repository secretsManage their own identities, subscriptions, and repository preferencesInvite/remove members, approve access, transfer ownership, manage billing, and delete the workspace
AdminManage connected tools, enabled repos, API keys, and repository secretsManage their own identities, subscriptions, and repository preferencesCannot manage workspace access or billing
MemberView the workspace, repositories, and tasksManage their own identities, subscriptions, and repository preferencesCan leave the workspace; cannot manage shared settings or billing

There is one owner. The owner must transfer ownership to another member before leaving. Plans are priced per workspace, not per member, so invite as many people as you like. See Billing.

Before delegating work

  • GitHub: the app must have access to the repository and the repository must be enabled in Sinatra. Start with the sinatraai issue label. The person who adds the label or comments must be a member of the Sinatra workspace, and their Sinatra account must use that GitHub account, by signing in with it or linking it.
  • Linear: join the Sinatra workspace and link your Linear identity in Settings. The linked organization must match the workspace connection.
  • Slack: join the Sinatra workspace. Sinatra matches your Slack account by email, or use Sign in with Slack in Settings. Then mention @Sinatra in a channel it has been invited to. See Slack.
  • Personal model access: connect your own subscription in that workspace's Settings. A teammate's personal subscription does not cover your tasks. See Models.

Personal repository preferences

Open Repos → repository to choose your engine, model, effort, and CI-fix limit (ci.max_rework). They override the committed .sinatrarc.json for iterations you trigger. You can inspect which values came from defaults, the repo file, or your override, and remove the override to return to the repository configuration.

Setup commands, environment variables, and hooks stay in the committed file; personal preferences cannot override them. See the .sinatrarc.json reference.