Question: What is the procedure to assign Firefighter Id’s to developers, Do most of the developers have their own firefighter Id’s or do they share a common Firefighter ID (for example: a single Firefighter to a small group of developers or people).
Answer: Single Firefighter ID can be assigned to multiple developers or other users but once a particular user is logged on using the same firefighter ID, another user can not logon to the system with the same firefighter ID. Also there might be numerous situations when developers’, basis or support teams needs to work collaboratively, therefore having separate firefighter IDs for separate groups/users would make sense. Another way to do this is to assign a particular Firefighter role with required authorizations to the considered users. But this is not a recommended approach.
Should we provide production system access to developers?
Generally we don’t do that but in exceptional cases a developer may need to fix something on the production box, it may be a bug in a client customization that wasn’t detected during quality assurance or any such case. The best way to do so is to assign a developer firefighter ID to that user for a particular period of time. This way each and every activity by a developer can be logged and you can have an audit trail in form of web reports for auditing purposes later.
Tip: The firefighter user credentials which include password as well is not required to be known by the user. Any user who is assigned a firefighter ID doesn’t require to enter user or password or any other credentials apart from his/her own user name and password to logon to system. So Firefighter user credentials are never shared among different users.
Recent Comments