Team Management
Invite team members and manage permissions for your organization.
Organization Members
Your workspace's members are the people you invite, by email. Each person has one profile, with their GitHub activity as a section of it once your workspace has GitHub connected.
Roles & Permissions
Jasper provides five built-in system roles with comprehensive permissions. Organization owners and admins can also create custom roles for granular access control.
System Roles
| Role | Permissions | Typical Use |
|---|---|---|
| Owner | Full access (99 permissions) | Organization administrators, billing contacts |
| Admin | All except billing & danger zone (95 permissions) | Team leads, senior developers |
| Stakeholder | Extended read access with settings (46 permissions) | Project managers, product owners, QA leads |
| Member | Standard contributor access (36 permissions) | Developers, contributors |
| Viewer | Read-only access (14 permissions) | External stakeholders, observers |
Permission Groups
Permissions are organized into logical groups with 99 total permissions:
| Group | Permissions | Viewer | Member | Stakeholder | Admin | Owner |
|---|---|---|---|---|---|---|
| Dashboard | view, export | view | all | all | all | all |
| Code Reviews | view, trigger, apply-fixes, retry, comment, delete, export | view | all except delete | all except delete | all | all |
| Comments | create, edit-own, edit-any, delete | — | create, edit-own | create, edit-own | all | all |
| AI Conversations | view, reply, delete, export | view | view, reply | view, reply, export | all | all |
| Project Assistant | view, chat | — | all | all | all | all |
| Analytics | view, team-view, export | — | all | all | all | all |
| Repositories | view, admin-view, manage, sync, branch-protection, rulesets | view | view | view | all | all |
| Team Members | view, invite, remove, change-role | view | view | view | all | all |
| Integrations | view, clickup.manage, github.manage | view | view | view | all | all |
| Quality Gates | view, edit, override | view | view | view | all | all |
| Webhooks | view, manage, retry | view | view | view | all | all |
| API Access | access, keys.view, keys.manage, logs.view | — | access | access | all | all |
| Notifications | preferences, history | history | all | all | all | all |
| Organization Settings | view, edit, audit-logs, roles.manage | — | — | view | all | all |
| Billing | view, manage | — | — | — | — | all |
| Danger Zone | transfer-ownership | — | — | — | — | all |
Custom Roles
Organization owners and admins can create custom roles for specific team needs:
- Clone from system roles — Start with a built-in role's permissions and customize
- Create from scratch — Build a role with only the permissions you need
- Per-organization scoping — Custom roles are specific to your organization
- Color-coded badges — Assign colors to easily identify roles
Creating Custom Roles
- Navigate to Settings → Roles & Permissions
- Click Create Role or Clone an existing system role
- Set the role name, description, and color
- Select permissions from the expandable permission groups
- Save the role
Tip: Use the "Clone" feature to create a variation of an existing role. For example, clone "Member" to create a "Contractor" role with limited API access.
Inviting Members
Invite people from Settings › Team Members: enter their email address and choose a role. They get an email with a link to join, and sign in with their email address (or GitHub, if they prefer).
If you use GitHub
With GitHub connected, the Team page also lists the people in your GitHub organization who aren't on Jasper yet, so you can invite them, and Sync brings in changes. A workspace can also let people in its GitHub organization join by themselves when they sign in with GitHub: turn it on in Settings › Workspace (it's off for new workspaces). Otherwise people join only by invitation.
Managing Access
What each person can see and change comes from their role (above). With GitHub connected, code review access also follows GitHub:
- Members see reviews for repos they can access on GitHub
- Removing GitHub access automatically revokes Jasper access
- Adding GitHub access grants Jasper access on next sync
Billing & AI Credits
AI credits are shared at the organization level:
- All team members share the organization's AI credits: 250 free a month
- Any member's reviews and AI answers use them
- Owners and people with billing access see the balance on the Billing page; for more, talk to us
Organization Quality Gates
Set organization-wide quality gate thresholds that apply as defaults to all your repositories. This ensures consistent code quality standards across your entire organization.
Accessing Organization Quality Gates
- Navigate to Settings in the sidebar
- Select Quality Gates
- Configure your organization-wide thresholds
Available Settings
| Setting | Description | Default |
|---|---|---|
| Minimum Score | Overall review score (0-100) required to pass | 70 |
| Max Critical Issues | Maximum critical issues before failing | 0 |
| Max High Issues | Maximum high-severity issues before failing | 2 |
| Max Medium Issues | Maximum medium-severity issues before failing | 5 |
How Inheritance Works
When you configure organization quality gates:
- New repositories automatically use organization defaults
- Existing repositories can opt-in to use organization defaults
- Individual overrides are preserved when enabled
Applying to All Repositories
Use the "Apply to All Repositories" button to:
- Set all repositories to use organization defaults
- Reset any custom per-repository overrides
- Ensure consistent standards across the organization
Per-Repository Customization
Individual repositories can still have custom thresholds. In the repository settings, you can:
- Toggle "Use organization defaults" on or off
- Override specific thresholds while inheriting others
- Set stricter or more lenient standards for specific projects