Workspace Roles

​

Understanding PR Licenses

PR licenses are automatically detected from your Git repositories based on developers who opened PRs in recent months. Why isn’t a developer showing up? If a developer isn’t appearing in your PR license count, it means Kody isn’t installed in a repository where that developer has opened PRs. Example: You can have 1 workspace admin managing settings, while 20 developers get automated reviews. All plans include unlimited PRs—your plan only determines which developers get review access.

​

Overview

Kodus workspaces supports Role-Based Access Control (RBAC), allowing you to manage user permissions and access levels within your organization. Each workspace member can be assigned one of four distinct roles, each with specific permissions and capabilities.

​

Available Roles

Each role provides different levels of access and capabilities within the workspace:

​

Owner

Full administrative access to the workspace and all its resources. Can view, edit, and delete all configurations across all repositories.

​

Billing Manager

Financial and billing management access with access to billing/subscription management and view access to most configurations, but no edit access to code review settings.

​

Repository Admin

Repository management access. Sees all configurations, pull requests, issues, cockpit, and plugins across the whole organization (read-only), and can edit code review configurations and Kody Rules for the repositories assigned to them.

​

Contributor

Read-only access to the whole organization. Contributors can view configurations, Kody Rules, pull requests, and issues across all repositories — no repository assignment needed — but cannot edit anything. Cockpit, token usage, billing, and user management stay admin-only.

​

Role Permissions Matrix

Here’s a detailed breakdown of what each role can do, based on the actual permissions matrix: _{Legend — V view · E edit (create/update) · D delete · — no access. Scope: all = whole organization · own = repositories assigned to the user · own+global = assigned repos plus the org-wide/global config.}

​

Managing Workspace Members

Workspace members are managed on the Workspace members tab of Organization → Subscription — there is no separate members page. Only Owners can invite members, change roles, or remove members.

​

Adding New Members

1. In the sidebar, open Organization → Subscription and pick the Workspace members tab
2. Click Invite member
3. In Workspace member invitation, type the member’s email and click Add to invite list (repeat for more people)
4. Click Send invites
5. Invited members join as Contributor; change their role afterwards (see below)

​

Auto-Join for Workspace Members

Enable auto-join to allow users with matching email domains to join your workspace automatically. How to enable:

1. Go to Organization → General (app.kodus.io/organization/general)
2. Under Auto Join, turn on Enable Auto Join, enter your domain, and save
3. Currently works with your registered account email domain only
4. Need a different domain? Contact us in the community

How it works:

• Users who sign up with your email domain can choose to join your organization
• They must confirm their email after choosing to join
• All auto-join users enter as Contributor role (read-only access to the whole organization)
• As Owner, adjust their role if they need edit rights

​

Changing Member Roles

1. Go to Organization → Subscription → Workspace members
2. Find the member whose role you want to change
3. Open the select in their Role column
4. Select the new role (Owner, Billing Manager, Repo Admin, or Contributor)
5. The change takes effect immediately

For a Repository Admin, assign the repositories they can edit with the + button next to their role, which opens Assign repositories.

​

Removing Members

1. In Organization → Subscription → Workspace members, locate the member to remove
2. Open the Actions menu (three dots) in their row
3. Select Delete
4. Confirm with Remove in the dialog

The same menu has Approve for members marked Needs approval and Copy invite link to share a member’s invite link again.

​

Security Considerations

1. Principle of Least Privilege: Always assign the role with the minimum necessary permissions
2. Regular Audits: Periodically review member roles and adjust as needed
3. Access Reviews: Conduct quarterly reviews of workspace access and permissions
4. Immediate Revocation: Remove access immediately when a member leaves the organization

​

Troubleshooting