"You've set up Redmine, installed the Agile plugin, and you're ready to run Scrum. But when your team tries to access the boards, they get permission errors. Now you're stuck—either grant everyone admin rights (bad idea) or lock them out completely (worse idea)."
.
That's where Redmine Agile plugin's Access Management feature saves the day. In this guide, you'll learn exactly how to configure permissions so developers can move cards, Scrum masters can close sprints, and stakeholders can watch progress—all without compromising security."
Understanding the access management challenge
From an administrator’s perspective, the practical value of Agile board configuration is enabling each functional team to have a tailored workflow view that matches their unique processes. For example:
- Customer support teams use a Kanban board to track and manage incoming requests.
- HR teams configure a board to monitor candidates through hiring stages.
- Scrum teams set up boards to plan and track user stories across sprints.
Why access management matters in 2026
When you’re working in a fast-paced DevOps or Agile setting, permissions in Redmine start to mean something different. It’s less about locking people out and more about keeping things moving.
Good access management just makes life easier for everyone. It means:
- You’re not exposing sensitive stuff to the whole company. Only the people who actually need to see it, can.
- Nobody steps on anyone’s toes. For example, you don’t want someone accidentally closing a sprint just because they clicked the wrong button—that should probably be left to the Scrum master.
- People can actually get stuff done on their own. They’ve got their own space to work in, and they’re not going to mess things up for someone else down the line.
Administrators must manage the ability for teams to independently configure, customize, and share their boards while maintaining overall system governance and security.
By default in Redmine, only administrators typically have access to Agile boards and backlogs through the Redmine Agile plugin. This creates a practical problem: team members who need to work with Agile workflows can't access the tools required for their daily work without being granted full administrator privileges.
The Access Management feature solves this by extending Redmine's permission system to include specific Agile-related capabilities that can be assigned to any user role.
Step-by-step: configuring access control
1. Define your roles
Start by mapping your real-world Agile team to Redmine roles.
- Scrum Master: Needs Manage Sprints and potentially Manage Boards.
- Product Owner: Needs View Backlog and the ability to reorder (edit) issues.
- Developer: Needs to view the board, update issue statuses (drag & drop), and log time.
- Stakeholder: Needs read-only access to specific boards or charts.
2. Configure project modules
Navigate to your project settings and enable the Agile module. This makes the Agile tabs available.
3. Assign permissions via roles
Go to Administration > Roles & Permissions. Select the role you want to edit and scroll to the "Agile" section. Check the boxes that correspond to the responsibilities you defined. The following guide will reveal how to add a group as an assignee for an issue and filter it afterward on the Agile board.
4. Set up board visibility
When creating or editing a board, you can define if it is Public (visible to all users who can access the project) or Private (visible only to you). This is a powerful feature for creating personal task views versus team-wide process boards
Advanced permission options
Beyond basic viewing permissions, the Redmine Agile plugin offers several advanced controls:
- Manage public agile boards: Allows users to configure and modify shared Agile boards
- Add agile boards: Enables users to create new Agile boards
- Manage sprints: Grants permission to create and configure sprints
- Manage backlog: Allows users to organize and prioritize the backlog
These advanced permissions should be granted selectively based on team members' responsibilities. It brings structure and accountability to complex or routine processes, right inside the ticket.
Practical implementation scenarios
Scenario 1: Development Team Access
Grant "View agile boards," "View backlog," and "View agile charts" to developer roles so they can see work items, update task statuses, and track progress without gaining administrative capabilities.
Scenario 2: Stakeholder Visibility
Provide clients or stakeholders with "View agile boards" and "View agile charts" permissions to monitor progress without accessing sensitive project configuration or being able to modify workflows.
Scenario 3: Scrum Master Controls
For Scrum Masters or team leads, add "Manage sprints" and "Manage backlog" permissions alongside viewing permissions to enable full Agile workflow management.
Key permission updates in 2026
The RedmineUP team consistently updates the plugin to enhance security and usability. According to the latest Redmine Agile plugin updates, the version 1.6.13 (January 2026) introduced crucial changes to access control that every administrator should know.
Here are the highlights from the recent releases:
- Refined Sprint Permissions (v1.6.13): The most significant update is the modification of permissions for showing sprints in the backlog. Specifically, the view_backlog permission now also grants access to view sprints, simplifying the permission structure for team members who need visibility into the planning pipeline .
- Redmine 6.0 Compatibility (v1.5.10 - March 2025): With full support for Redmine 6.0, the plugin now utilizes SVG icons for a cleaner, more scalable interface, ensuring that permission icons and role indicators are crisp on high-resolution displays .
- Permission Check Fixes (v1.6.6 - Nov 2023): A critical fix was applied to the permission check for Agile card spent time, ensuring that time tracking data is only visible to those with the correct permissions, enhancing financial and resource data privacy .
From sprint management and multi-project portfolios to visualizing intricate workflows, the Redmine Agile plugin, is a proven game-changer. Using the plugin, you can define a unique workflow for any project and build a customized Scrum or Kanban board. The best part? You can save your perfect board setup and instantly share it with your team for weekly syncs, planning meetings, and more.
Manny Palachuk
Business Coach I love checklists, and CRM and Questions, but I'm an Agile guy. Our platform is a customized Redmine to use for Business Strategy Development. So my favorite plugin / function is the Agile plugin. It makes the strategy development come alive.
Manny Palachuk, Owner & Head of IT. Didn't just implement Redmine—he re-engineered it to become the central nervous system of his business, seamlessly connecting his team's productivity with his clients' success. Read the full story.
Frequently Asked Questions about Redmine Agile plugin access management
How do I give someone access to Agile boards in Redmine without making them admin?
To grant Redmine Agile board access without administrator privileges:
- Go to Administration > Roles & Permissions
- Select the role you want to modify (or create a new one)
- Scroll to the Agile section and check the specific permissions needed
- Save changes and assign this role to users in your project
This is the standard method for Redmine role-based access control that keeps your system secure while empowering team members.
Why can't my team members see sprints in the backlog?
If users have Redmine Agile plugin permissions but still can't see sprints, check these common issues:
- Missing permission: In Redmine Agile plugin v1.6.13+, the view_backlog permission now also controls sprint visibility. Ensure this is enabled.
- Project module disabled: Verify the Agile module is enabled in Project Settings > Modules
- Sprint visibility settings: Some sprints may be configured as private or restricted
- Plugin version: Update to the latest Redmine Agile plugin version (current: 1.6.13 as of January 2026)
If problems persist, check your Redmine permission settings for any role conflicts.
Can stakeholders view Agile boards without editing anything?
Yes, you can provide read-only Agile board access to stakeholders by configuring these Redmine Agile permissions:
Create or edit the stakeholder role in Administration > Roles & Permissions Under the Agile section, enable ONLY:
- View agile boards
- View agile charts
This setup gives stakeholders Redmine project visibility for progress tracking while preventing accidental changes to workflows or sprint data—perfect for client reporting and executive dashboards.
Conclusion
The Access Management feature in the Redmine Agile plugin transforms Redmine from a basic project management tool into a fully functional Agile platform accessible to entire teams. By strategically assigning Agile permissions to different roles, organizations can maintain security while empowering team members with the tools they need for effective Agile collaboration.
This granular permission system ensures that everyone—from developers to stakeholders—has appropriate access to Agile features without compromising system security or workflow integrity. As demonstrated in the RedmineUP video, configuration is straightforward and immediately effective, requiring just a few minutes to set up but providing lasting benefits to your Agile processes.
Ready to enhance your team's Agile capabilities? Start by mapping your team roles to the permission sets outlined above, then configure your Redmine instance accordingly.
Explore Redmine plugins today and see why thousands of teams choose RedmineUP to power their projects.
