arvumiDocs
Open dashboard
Browse documentation

Your workflow

Teams & repository access

Work together with explicit team membership and GitHub repository permissions.

On this page

Projects belong to teams

A team organizes people, projects, and repository access. Choose or create a team during onboarding. Team invitations let another Arvumi user join your workspace.

Owners and admins manage repository grants and database administration. Members can create and deploy projects using repositories already granted to the team. Viewers can browse but cannot deploy. Ask an owner or admin when an action requires a higher role.

During beta, each GitHub identity can own at most three teams and create at most three teams in a rolling 30-day period, across Free and Pro. Existing teams above the limit remain usable. Deletion and account recreation do not reset the creation allowance; invitations do not mint another allowance. If creation is blocked, use an existing team, accept an invitation, or wait for the rolling window to allow another creation. Contact support if you need help.

Grant a GitHub repository

  1. As an owner or admin, open Teams → your team → GitHub repositories.
  2. Choose Authorize GitHub using the same GitHub account you use for Arvumi.
  3. Select or install the GitHub App for the appropriate account or organization, and choose its repository access.
  4. Return to Arvumi, choose the repository, and click Grant to team.
  5. Create a project from that repository, or connect the granted source in an existing project’s Settings → Deploy Config.

Authorization grants one repository to the team at a time. Installing the App alone does not grant repositories to every team. An installation can be connected to only one Arvumi team at a time.

Private repository access

Arvumi uses GitHub App access for checkouts and push events. You do not need to paste a personal access token into the repository URL or configure a separate webhook for an App-connected project.

Source privacy and site privacy are separate.

A private GitHub repository can produce a public website. Add application authentication or configure preview protection for content that needs restricted access.

The current repository flow supports GitHub.com HTTPS repositories. GitHub Enterprise, SSH URLs, submodules, Git LFS, other Git providers, and pull-request/fork deployment flows are not supported by this connection flow.

If a repository is missing

  • Confirm you authorized the same GitHub account used to sign into Arvumi.
  • Check the GitHub App installation includes the repository.
  • Complete organization approval or SSO if required. If your authorization expires while waiting for approval, authorize again in Arvumi.
  • Confirm an owner or admin clicked Grant to team after selecting the repository.
  • If the installation belongs to another team, have an owner or admin resolve that connection before trying again.

When access changes

Revoking repository access or disconnecting a source stops new checkouts. Existing deployed sites remain available. Reconnect or reauthorize the repository before deploying new changes.

Use teams from the terminal

arvumi teams list
arvumi teams switch TEAM_SLUG
arvumi teams members
arvumi github-repos --team TEAM_UUID

Replace the placeholders with your team’s slug and UUID. See CLI reference for sign-in and project linking.