From 73f6f1fad9cbf009b74e672873ee8a7c9e94bb82 Mon Sep 17 00:00:00 2001
From: Clayton J Barnette <110616975+claytonjbarnette@users.noreply.github.com>
Date: Wed, 23 Nov 2022 10:32:18 -0500
Subject: [PATCH] Added Detailee Use Case

Added use case from issue #591
---
 _playbooks/playbook-ilm.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/_playbooks/playbook-ilm.md b/_playbooks/playbook-ilm.md
index d1f310aff..7d37ad7c4 100644
--- a/_playbooks/playbook-ilm.md
+++ b/_playbooks/playbook-ilm.md
@@ -285,6 +285,8 @@ Make attributes available for authorization decisions. Federation is not only ac
 
 See the [Cloud Identity Playbook Federation section]({{site.baseurl}}/playbooks/cloud/#federation) for more information on federation and using trust frameworks for government, mission partner, or public identity federation.
 
+**Detailee Use Case** - An Agency A employee is detailed to Agency B. How can Agency B use their ILM system for this existing Agency A employee, but short-term Agency B employee. Can Agency A share HR data to do birth-right provisioning in Agency B? I think the corpus of this use case is how Agency B can provision Agency A employee without issuing them an Agency A piv card and an Agency A email.
+
 ## Summary
 
 The ILM playbook outlined an identity lifecycle process and four steps to create a master user record and lifecycle process within your agency. ILM is the evolution of an identity from creation to deactivation. There are specific steps within each lifecycle phase of the joiner-mover-leaver process. A master user record is the core of ILM and acts as an aggregation point of identity data for all agency users. A master user record integrated with access management tools provides a foundation for more mature ICAM processes.