In Vaugh Vernon's book "Implementing Domain Driven Design", the team separated the Identity and Access from Collaboration context because the team realized they are being stuck on the "role-based" mindset and what they needed was simply just Author, Moderator, Creator, etc and those can be fetched from Identity And Access context which contains infos like roles, credentials, and Person info which then will be translated by a Translator into the right "role" (Author, Moderator, Creator, etc.)
So my problem is different, I will be having no roles at all (or maybe I am not just seeing it yet. HR currently doesn't have an account in this iteration).
Scenario: HR will activate Employee's account -> employee will receive a default pass by Sms which he can change later on.
So now my question is: do I need separate BC for the employee's account? Or should I just add a
password property in Employee AR?