> 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/administration-guide/reference.md). # Reference Look up a property, an enumerated value, or a shipped object without reading a task page. ## What this is, and when you need it Task pages in this guide link here instead of restating values, so a value appears in one place and stays consistent. This section is for the administrator who needs the exact name, the exact type or the exact default — every table on these pages is the shipped state of a release rather than a transcription. Come here for the value; go back to the task page for what to do with it. Each page states its own coverage counts. ## Choose your outcome | I want to… | Go to | | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Look up an exact error message, log line, UI message or observable symptom | [Error and symptom index](/administration-guide/error-and-symptom-index.md) | | Look up what a setting is called, what type it is, and what it ships as | [System property reference](/administration-guide/reference/system-properties.md) | | Look up an event name, or how long that event is kept | [Audit actions and retention](/administration-guide/reference/audit-actions-and-retention.md) | | Look up what is actually in a drop-down | [Enumerated value reference](/administration-guide/reference/enums.md) | | Look up a lifecycle menu item, the screen behind it, or one of the 21 user statuses | [User lifecycle reference](/administration-guide/reference/user-lifecycle-reference.md) | | Look up a column name or optional criterion the user-search properties accept | [User search configuration](/administration-guide/reference/user-search-configuration.md) | | Look up a field on the managed-system form, or what reaches the connector request | [Managed system fields and the connector request](/administration-guide/reference/managed-system-fields.md) | | Look up which connectors ship, the queue each names, and what each supports | [Shipped connectors](/administration-guide/reference/shipped-connectors.md) | | Look up a field on the synchronization form for my source type | [Synchronization configuration fields](/administration-guide/reference/synchronization-configuration-fields.md) | | Look up a synchronization script's method signature or a transform return code | [Synchronization script contracts](/administration-guide/reference/synchronization-script-contracts.md) | | Look up what a reconciliation situation response will actually write | [Reconciliation situations and responses](/administration-guide/reference/reconciliation-situations-and-responses.md) | | Look up which BPMN definition drives an approval, and how to change it | [Shipped approval workflows](/administration-guide/reference/shipped-workflows.md) | | Look up whether a job is automatic, its cron expression, and whether it ships enabled | [Shipped batch tasks](/administration-guide/reference/shipped-batch-tasks.md) | | Look up which template a notification uses | [Shipped mail templates](/administration-guide/reference/shipped-mail-templates.md) | | Look up which reports exist and what runs them | [Shipped reports](/administration-guide/reference/shipped-reports.md) | | Look up a report builder property, its audit actions or the shipped report templates | [Operate the report service](/administration-guide/reports/operate-the-report-service.md#operate-properties) · [System templates](/administration-guide/reports/system-templates.md) | | Look up a working example of an extension point | [Shipped Groovy scripts](/administration-guide/reference/shipped-groovy-scripts.md) | | Look up where a script is stored, which columns reference one, or the sandbox allow-list | [Groovy script reference](/administration-guide/reference/groovy-script-reference.md) | | Look up an SoD enum, the rule JSON schema, a shipped catalogue or a violation-report field | [SoD rule and policy reference](/administration-guide/reference/sod-rules-and-rule-sets.md) | | Look up a certification table or preview-store field for a report or a break-glass query | [Certification database tables](/administration-guide/reference/certification-tables.md) | | Look up which index backs a screen, and how to rebuild it | [Search indexes and the authorization graph](/administration-guide/reference/search-indexes.md) | | Look up a password or authentication policy parameter, and what the default policy enforces | [Password and authentication policy parameters](/administration-guide/reference/policy-parameters.md) | | Look up why a label is still in English, or which languages are available | [Languages and localization reference](/administration-guide/reference/languages.md) | ## What "shipped" means on these pages A shipped value is what a newly migrated database contains, established by replaying every Flyway migration in order — including the deletions and updates that later releases apply. It is not the first value a feature ever had, which is what a page written from a single migration tends to report. A deployed system can differ from shipped state for three reasons: an administrator changed it, an upgrade path left an older value in place, or a container override is supplying a different value to the service. Verify against the running system before you rely on a default. *Applies to OpenIAM 2026.8.1. Last reviewed 7 August 2026.* --- # 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/administration-guide/reference.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.