Hi All,
I am new to the forum, and would appreciate some guidance on a design question.
Scenario:
We have a group of non-employee users who currently do not exist in a source system of record (such as HR). These users still require downstream provisioning, including Active Directory access and application access.
This persona does not fall under Non-Employee Risk Management (NERM) in our scenario.
Question:
Is it considered good practice to create and manage these users directly in SailPoint ISC when there is no authoritative source of truth, or would it be better to introduce another authoritative source (e.g. a simple user registry or directory) and use that as the identity source?
What I have tried:
-
Reviewed SailPoint documentation on authoritative sources and identity creation.
-
Looked into whether ISC can act as the identity source for manually created identities and still support provisioning workflows.
Current result:
It appears possible to create identities manually or through workflows, but I’m unsure whether this aligns with best practice for identity lifecycle management.
Expected outcome:
Looking for guidance on recommended architecture or best practice for managing identities that don’t have a traditional source of truth but still require provisioning.
Has anyone implemented a similar model in ISC? Any recommended patterns or approaches would be greatly appreciated.
Thanks in advance.