#1 India's Top IT Training Institute

×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →
Jenkins · Topic 10 of 15

User Management in Jenkins

Why User Management?

Security in Jenkins is all about authentication and authorization. By default, Jenkins requires a username/password, and every new user gets full access. Jenkins stores user details in the local file system by default (real projects typically use LDAP or Active Directory instead).

Authorization Strategies

A. Role-Based Strategy

Typical roles: Developer (read-only, can view builds), Tester (read, cancel, testing permissions), DevOps (full permissions).

  1. Add a user: Manage Jenkins → Users → Create User.
  2. Install the plugin: Manage Plugins → search "Role-based Authorization Strategy" → Install.
  3. Configure it: Manage Jenkins → Security → Authentication → select Role-Based Strategy → Save. This unlocks a new "Manage and Assign Roles" section.
  4. Add roles: Manage and Assign Roles → Manage Roles → add roles like Dev, Tester, DevOps and tick the relevant permission checkboxes → Save.
  5. Assign roles: Manage and Assign Roles → Assign Roles → Add User → give the username and tick the matching role → Save.
  6. Login: Log out and log back in as that user to see the restricted dashboard reflecting their role.

B. Project-Based Matrix Authorization Strategy

This gives job-level permissions — a specific user can access only specific jobs.

  1. Install the Role-based Authorization plugin (if not already installed).
  2. Manage Jenkins → Add user → Save.
  3. Manage Jenkins → Security → Authorization → select Project-based Matrix Authorization Strategy → add the user → give minimal read/view permissions → Save.
  4. Open the specific job → Configure → check "Enable project-based security" → add the user → grant the needed permissions → Save.
  5. Log out and log in as that user — they will now see only that specific job in the dashboard, nothing else.

Master Jenkins & DevOps with Uncodemy

Hands-on live training, real projects, and placement support — become job-ready in DevOps.

Enroll in DevOps Training →