It depends on what the component does.
Sometimes it’s better to extract the functionality as a manager to a separate actor and reference that through the characters.
Too many components hurts performance so it’s best to not go too crazy with them as a workflow.
If you do use them then stick to Actor Components as they don’t require extra information like transforms.
You can us get owner to check who is “wearing” the component and do specific actions based on this. You could also use a variable of type Enum set set specific types of behaviors.