Agency agreements

Relevant issues:

#265

Background information

Agents

Agents are users who have been delegated by agreement holders to sign RUPs for them.

• Agents are able to be agreement holders for their own RANs, and agents for others at the same time. ??LM: what about agents that don’t have RANs therefore don’t have their own CLIENT# (ex. a ranch manager for a corporation)?

• Users can be both an agreement holder and agent for another AH on the same RAN.

• Agents can represent multiple users.

• either the agent OR the agreement holder can sign (having an agent doesn’t take away the legal right of the AH)

Ideas

• Add a new role for users that can only sign. We don't need another role; we can just look up if the user is the client or agent and differentiate from there. (We also don't want another role because agents can be agreement holders as well).
• Maybe add a agent_id column to the client_agreement table?
• Would want to show in the UI that an agent has been delegated to be the signatory
• Add a UI component to let agreement holders choose (or remove) an agent to act for themselves.
• Because agents can represent more than one AH, we could get a list of all rows in client_agreement with the same agent_id values as the ID of current user and the agreement_id of the RAN needing to be signed.
• We could show both buttons/options that would be shown to agents and agreement holders, if a user is both an AH and agent for an RUP. Alternatively, if agents need to do more than just sign, we can add a role switcher dropdown that would let the user act as either an agreement holder or agent

Questions

• Which actions do delegated users need to be able to do? Is it just signing the RUP? LM: in its most basic form anything that the AH can do (ex. provide RUP content, create amendments etc.)