PROBLEM STATEMENT

Current Behavior:

When new teams onboard to Harness, administrators must manually:

Create team in Harness (User Groups)

Add team members one by one

Assign roles/permissions manually for each resource (projects, pipelines, environments)

Repeat for every new project or org the team accesses

Business Impact at PayPal:

Onboarding a single team takes 1-2 hours of admin time

Human error leads to incorrect permissions (too permissive or too restrictive)

Teams wait days for access while admins work through backlog

No standardization—each team gets different permission sets based on who configured them

Compliance risk: overly permissive access granted by mistake

Scaling issue: PayPal has 400+ teams, manual provisioning doesn't scale

Who is Affected:

Platform administrators (DPP team) managing RBAC

New teams onboarding to Harness

Existing teams expanding to new projects/orgs

Security/compliance teams auditing access

REQUESTED SOLUTION

Automated Team Provisioning:

Define "team templates" with default role assignments

When new team is created (or synced from external system), automatically:

Provision the team as a Harness User Group

Assign default roles based on team type (Developer, DevOps, Admin, ReadOnly)

Grant access to appropriate projects/orgs based on rules

Set up default notification preferences