Skip to main content
Setting Up Your Account Managing User Access with Teams

Managing User Access with Teams

Introduction

Aikido lets you create teams, connect multiple repositories and clouds, and manage access using RBAC (Role-Based Access Control) for better security. This article focuses on Managing of User Access. If you are looking to use Teams to group your resources into Projects or Apps, please click here.

Use Cases

  • Selective Access Control: Assign repository access exclusively to designated team members.

  • Filter Repositories Quickly: In companies with multiple teams, each team may have access to the entire codebase, but their primary responsibilities are often limited to specific repositories or projects. By creating teams in Aikido, team members can have a focused overview of only the repositories relevant to their tasks.
    ​

  • Better overview when using a monorepo split. You can assign team members to specific directories of your monorepo, improving their overview. More information on splitting monorepositories can be found here.

How To Create Teams

Step 1: Navigate to Settings -> Teams
​

Step 2: Click Create Team and give your team a name
​


Step 3: Add team members to the newly created team.

Step 4: Define the team's responsibilities by adding resources via the responsibility tab. You can add different resources such as clouds, repositories and containers.

If you want to link specific domains to a team, you can set this up by linking your domains to a repo or container. It will automatically inherit access permissions.

Step 5. Go back to your feed and filter on a specific team. You should only see issues that are related to those repositories and clouds that were attached to the team.

Syncing with GitHub, Bitbucket or Azure DevOps

If you have existing teams set up in GitHub,Bitbucket or Azure DevOps, Aikido can import them and maintain synchronization on a nightly basis. This ensures that any changes in team structures or access rights managed in GitHub/Bitbucket are accurately reflected in Aikido. Any new teams that are created in GitHub will appear in Aikido. The same applies to when you remove a team in GitHub: Aikido will pick this up and remove the team too. Any repos that are part of the team, will be synced too.

It's important to note that in this scenario, GitHub/Bitbucket/Azure DevOps acts as the source of truth for access rights, and all management should be conducted within those platforms.

Aikido makes it clear which teams have been imported from your SCM.

Syncing with Backstage.io

Aikido integrates seamlessly with repositories containing catalog-info.yaml files for Backstage.io. This allows for the automatic importing of teams, taking into account the path of where the file is located.

How It Works

  1. Aikido scans repositories for catalog-info.yaml files.

  2. Aikido looks for the spec->owner field in the file and imports this as team.

  3. Aikido records the exact path of each catalog-info.yaml file, ensuring the team is responsible for those specific paths (and repositories).

How to select your team in UI

Aikido's Feed features a team filter at the top of the page. This filter allows users to tailor the feed to display only the issues relevant to selected teams. This filter can be used on basically every page in Aikido (feed, reports, settings etc).