> 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/where-to-go-next.md). # Where to go next Where to go after the proof of concept: production planning and the deeper guides. You proved the core. Everything below lives in the full documentation set at [docs.openiam.com](https://docs.openiam.com) — navigate by the guide and chapter names given here. ## Day-2 operations Before real users touch the system, work through [Start administering OpenIAM](/administration-guide/start.md) in the Administration Guide — it covers what this guide's POC didn't: named admin accounts instead of shared `sysadmin`, notification/email templates, batch task review, and wiring the Grafana/Prometheus dashboards you installed in [Install OpenIAM from RPM](/getting-started-guide/install-openiam-rpm.md) into actual alerting. ## Make the source of truth real The POC used AD as the source. Production deployments usually feed OpenIAM from HR (Workday, SuccessFactors, CSV) and treat AD as a target. Start with [Connect applications and automate lifecycle](/administration-guide/lifecycle.md) (synchronization, incremental sync, provisioning configuration) and the **Connector Configuration** catalog for your HR system. For CSV and manual (connector-less) applications, the **application onboarding** chapter's importing pages include ready-made CSV structures and transformation scripts. ## Automate joiner / mover / leaver Birthright access via roles and membership rules, terminations, rehires, and leave of absence: [Connect applications and automate lifecycle](/administration-guide/lifecycle.md) and [Manage identities](/administration-guide/identities.md) (admin operations, rehire flow). Role design guidance: the **business roles** and **access roles** design pages in the planning chapter. ## Harden the platform Production topology and HA: **Installation Guide → RPM installation** (multi-node clustering, remote databases including PostgreSQL, RabbitMQ TLS — pair the latter with the connector TLS note in [Install the AD connector](/getting-started-guide/lifecycle/install-ad-connector.md)). Air-gapped environments: the **offline installation** page in the same chapter. Upgrades: the **Upgrading** chapter. Changing service passwords the supported way: [Rotate service credentials](/administration-guide/security/rotate-service-credentials.md). Security hardening: **Installation Guide → Hardening**. ## Go deeper on authentication [Secure sign-in and credentials](/administration-guide/security.md): the full adaptive-authentication rule designer with risk scoring, FIDO2/passkeys, certificate authentication, Duo, account unlock. Password management depth (compromised-password checks, AD password expiry): [Password policy](/administration-guide/security/password-policy.md). ## Expand federation and SSO [Configure federation and application SSO](/administration-guide/federation.md) for the complete SAML, OAuth 2.0, and OIDC references, JIT provisioning, and retiring providers; **Developer Guide → API** for the SAML and OAuth/OIDC API references. Applications that can't speak SAML at all: [Administer the Access Gateway](/administration-guide/gateway.md) — header injection, form fill, URL rewriting. ## Governance Access certification campaigns: [Govern access](/administration-guide/governance.md). Segregation of duties: [SoD policies and rule sets](/administration-guide/governance/sod/sod-policies-and-rule-sets.md). Reporting: [Shipped reports](/administration-guide/reference/shipped-reports.md). ## Branding, deeper [Brand the portals](/getting-started-guide/brand-the-portals.md) got you a working brand. The **Developer Guide → Customizing branding** chapter adds Kubernetes deployment variants, downloadable example stylesheets per page type, and custom HTML for template-driven pages. ## For developers **Developer Guide**: REST APIs, custom Groovy (the sync transformation scripts from the [group](/getting-started-guide/lifecycle/import-groups.md) and [user](/getting-started-guide/lifecycle/import-users-and-memberships.md) imports are documented under Synchronization), building custom connectors, and UI customization. ## Planning a production rollout The workforce IAM planning questionnaires in the documentation are useful now — after the POC — as the checklist for scoping the real deployment with your stakeholders or OpenIAM's services team. --- # 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/where-to-go-next.md?ask=&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.