Bind an identity
Assign a dedicated or employee-linked Redmine account to the AI Employee.
Bunny Redmine by Appar
Redmine AI Permissions and Access Control
Bind every AI Employee to a Redmine account so it can only see and change the projects, issues, and knowledge that account is allowed to access.
Redmine remains the permission boundary
If the account cannot see it, the AI cannot see it
Each AI Employee maps to a Redmine identity. Project visibility, issue permissions, and authorized actions follow that identity instead of relying on one unrestricted administrator token.
Apply an exact scope
Use existing Redmine roles, projects, trackers, and permissions to limit access.
Control write behavior
Define direct actions and human-confirmation points through tools and prompts.
Layered permission control
Combine identity, tools, and approval rules
Administrators control the AI surface centrally while each Employee receives an independent configuration.
Illustrative product walkthroughThe AI has the account's access—not more.
Administrator settings
Example configuration
Read the portal issues using the project assistant's bound account.
Review the configuration
Prepared result
The authorized work is available; the restricted project remains inaccessible.
Permissions and approval rules still apply. · Illustrative data
Illustrative product walkthrough
Each AI Employee maps to a Redmine account.Use the projects and actions this account already has permission to access.Requests for restricted work remain denied.Keep the execution outcome available for administrator review.
Account-bound visibility
The AI only reads projects and issues visible to its mapped Redmine account.
Tool allowlists
Expose only the tools required for that Employee instead of every available capability.
Prompt confirmation rules
Require a human decision for sensitive actions while routine work proceeds directly.
Administrator-only control
Only system administrators change models, tools, permissions, and company-wide settings.
FAQ
Frequently asked questions about Redmine AI Permissions and Access Control
Does this replace Redmine?
No. Bunny operates through existing Redmine accounts, projects, permissions, and workflows. Redmine remains the system of record for enterprise work.
What can AI execute without asking a person?
Only actions inside administrator-approved account permissions, tools, models, budgets, and prompt boundaries. Defined approval points stop and return the decision to a person.
How should we start?
Contact Appar and choose one workflow with a clear input, outcome, and owner. Start with a controlled pilot, inspect the records and results, then expand deliberately.
Define a safe scope
Give AI the minimum access required to complete real work
Appar can map your Redmine roles, projects, tools, accounts, and approval points before deployment.