> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/getting-started-guide/lifecycle/poc-checklist-and-cleanup.md).

# POC checklist and cleanup

Verify the lifecycle proof of concept end to end, then clean up the test objects.

## Acceptance matrix

| # | Claim                                                         | Evidence                                                                                                                       | Pass |
| - | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | ---- |
| 1 | Stack installs from RPM and reports healthy                   | `openiam-cli status` output                                                                                                    | ☐    |
| 2 | Served over HTTPS with a valid cert                           | Browser padlock on `/webconsole`                                                                                               | ☐    |
| 3 | Connector connects and receives work                          | Consumer on `<Queue>_Request`; green Test connection                                                                           | ☐    |
| 4 | `ON_DELETE = DISABLE` set before first write                  | Managed-system attribute screenshot ([Connect OpenIAM to Active Directory](/getting-started-guide/lifecycle/connect-to-ad.md)) | ☐    |
| 5 | Groups imported, scoped, idempotent                           | Counts match AD; re-run unchanged                                                                                              | ☐    |
| 6 | Users imported with memberships, managers, status — read-only | Counts + spot-check user; connector log shows reads only                                                                       | ☐    |
| 7 | Provisioning creates an AD account on role assignment         | `Get-ADUser poc.provision1` in the Provisioned OU                                                                              | ☐    |
| 8 | Delete in OpenIAM disables (not deletes) in AD                | Same DN, `Enabled : False`; no delete in logs                                                                                  | ☐    |
| 9 | Nothing was touched outside the POC OU                        | `PermittedDN` + spot check of sibling OUs                                                                                      | ☐    |

Nine of nine and you have a defensible lifecycle POC. Anything failed: the page that produced it has the troubleshooting table.

## Cleanup (in this order)

1. Re-enable and remove the test account in AD if you're keeping the lab; or
2. Deactivate your cloned sync configs (so no scheduled run surprises you later);
3. Remove the `POC AD Access` role assignments;
4. Delete `poc.provision1` from AD if the lab is disposable;
5. Leave `ON_DELETE = DISABLE`, the managed system, and the connector in place if you're continuing to the authentication and federation parts;
6. Tearing everything down? Delete the POC OU tree and the service account; uninstall the connector via Windows **Control Panel → Uninstall a program** (removes both `OpenIAM*` services; the `C:\Connectors\<Name>` folder may retain logs and config — delete it manually); snapshot/discard the VMs.

## Turning the POC into a decision

You have now proven install, connectivity, read (groups, users, memberships), write (provision), and safe removal (disable). What a production decision still needs on top: an authoritative source (HR) feeding OpenIAM rather than AD-as-source, joiner/mover/leaver workflows, approval flows, and HA topology — all covered in the Administration and Installation guides ([Where to go next](/getting-started-guide/where-to-go-next.md)).

Continue with [authentication and self-service](/getting-started-guide/authentication.md), or jump to [federation](/getting-started-guide/federation.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openiam.com/getting-started-guide/lifecycle/poc-checklist-and-cleanup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.