reasonablility about having a bridge table between three or more tables for roles, more efficient alternatives

One security officer can work at many offices. Depending on the office that the security officer is working on that day, the officer can have a different role. I modeled entities Officers, Offices, and Roles. I modeled the requirement with bridge table Officers_Offices_Roles_Bridge that has composite key (officer_id, office_id, role_idj). For example, an officer working in the Manhattan office on Mondays has junior security specialist role, and working in the Bronx office on Tuesdays has dispatcher role. What is reasonable and unreasonable about a bridge table between three or more tables? What are more efficient alternatives?