Credentials sit in a spreadsheet on a drive, in a chat history or in an issue comment. Whoever leaves takes their knowledge with them. Whoever joins gets the data sent by email.
The Passwords plugin stores credentials encrypted in Redmine, where the matching project lives. Who has access is controlled by roles and permissions.
How it works day to day
- Store by project. A credential belongs to a project. The same permission structure applies as for issues.
- Share deliberately. Entries can be shared with individual users or with groups, instead of being open to everyone.
- Link it. A credential can sit on an entry in the DB plugin, for example on the server or the supplier contract it belongs to.
- Clean up. When someone leaves the project, the role removes the access. No list has to be reviewed.
What changes
- Credentials no longer sit in files that nobody maintains.
- New team members get access through their role instead of through an email.
- When someone leaves, access ends with the role and not with a reminder.
Which functions the Redmine Passwords plugin brings along and what it costs is described on the product page.