Producer code security and policies

Producer code roles allow you to create groups of permissions and attach them to producer codes. You can then assign the producer codes to users, to policies, or accounts. Users who have producer code security can only use their role permissions against policies that have a producer code matching one of their own producer codes. Only the permissions assigned to the producer code that matches can be used against that policy, even if the user has a larger set of permissions available through user roles. A permission must exist on both the user role and the matching producer code role in order for it to be used with the policy.

You can turn producer code security on or off for any given user. This security is typically turned on for a producer. This security might not be turned on for underwriters or auditors, thus allowing them to work on any policy. For instructions on how to change this setting, see Turn on producer code security.

In the following illustration, the producer of service is Armstrong (Premier) for the Ray Newton policy. Andy Armstrong has that producer code and has producer code security turned on. Therefore, he can use the permissions provided with the Armstrong (Premier) producer code on the Ray Newton policy.

Peyton Armstrong has producer code security turned on. He can use the permissions provided with the Armstrong - Los Angeles producer code to work on the Cheryl Jones policy. Peyton Armstrong cannot work on the Mark Black policy because the producer of service is Armstrong - San Diego.

The Supervisor has producer code security turned off. Therefore, she can work on any policy.

For more information about the producer of service and producer of record, see Producer of record and producer of service.