> ## Documentation Index
> Fetch the complete documentation index at: https://www.presolve.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Request and review API access
> Understand the credential form and hand off scoped access to an integration owner.
Open **API Keys** in [Settings → Integrations](https://attorney.dearlegal.com/dashboard/settings?tab=integrations). Use this entry when an approved integration needs access to Presolve data. Staff can describe the business task without handling the credential themselves.
## Prepare the access request
Tell the integration owner which records the external system needs and whether it only reads information or also changes it. Include the expected duration and who will own the integration.
## Review the creation form
| Control | What to decide |
| - | - |
| Name | A recognizable name identifying the integration and purpose. |
| Expiry | How long the credential should remain available. |
| Read only preset | Whether the integration can operate with read access. |
| Resource read/write scopes | Which types of records and actions are required. |
| Organization management | Whether this additional administrative capability is actually needed. |
| Acting attorney | Existing active member used for supported write attribution and current HQ reporting permissions. |
| Current organization + child organizations | On by default for saved report runs. HQ rollups need the acting attorney’s HQ/report/data grants; this does not widen all API endpoints. |
| Optional webhooks | Whether the integration also needs event notifications. |
Have the owner choose the access needed for the task. Use the [scope reference](/docs/scopes), [authentication guide](/docs/authentication), and [webhook overview](/docs/webhooks/overview) for technical details.
## Manage an existing key
Key management requires **Manage Integrations**. Review the key's issuing organization, name, prefix, expiry, scopes, acting attorney, and last-used time before editing it. Use Configure to update its settings without changing the secret. Use Revoke when the integration should no longer authenticate with that key.
The secret is shown once at creation. If it is lost or needs replacement, create a new key, test and switch the integration to it, then revoke the old one. Give each integration a recognizable name and an owner responsible for expiry and access reviews.
## Set up HQ reporting
Use a key issued by HQ and an existing active HQ member as its acting attorney. Leave **Current organization + child organizations** on for report rollups. The member needs reporting, export, HQ visibility, and the appropriate case/accounting permissions. NSA data has its own access requirement. The member does not need a new account in each child organization for this authorized reporting path.
The toggle affects saved report API execution. It does not change access in the Accounting or Lead Overview pages, and it does not make other API endpoints multi-organization. Report publication, application sharing, and saved filters remain separate checks.
See [HQ and acting-attorney permissions](/docs/authorization) for the access checklist and [report troubleshooting](/docs/reporting/troubleshooting) for missing records or reports.
## Keep access and outcomes separate
A configured credential does not establish that an external system successfully read or updated a record. The integration owner should verify the intended operation and resulting record separately.
This guide covers the access-request and setup controls. Use the linked technical documentation and the integration owner's process for credential handling and lifecycle management.
Related: [Integration overview](/docs/help/integrations/overview).