# 1Password **1Password** is a secure password and secrets management platform that helps organizations store, share, and manage credentials like passwords, API keys, and certificates. By centralizing secrets in an encrypted vault, 1Password reduces the risk of credential sprawl and unauthorized access. You can integrate 1Password with Apono to help your team securely broker access to secrets through access flows, ensuring that sensitive information is only accessible to authorized users when it’s needed without exposing static credentials or requiring manual sharing. *** ### Prerequisites
ItemDescription
1Password service account

1Password service account for Apono with read and share permissions

Learn how to create a service account.


NOTE: During step 4.4, under Permissions, select Read Items and Share Items.

Service account token

Unique token used to authenticate your Apono service account


NOTE: 1Password only reveals your token once after creating a service account (step 4.6). Copy and save your token.

Apono connector

On-prem connection serving as a bridge between 1Password and Apono:

Minimum required version: 1.4.0

Learn how to update an existing AWS, Azure, GCP, or Kubernetes connector.

*** ### Integrate 1Password

1Password tile

{% hint style="success" %} You can also use the steps below to integrate with Apono using Terraform. In step **10**, instead of clicking **Confirm**, follow the **Are you integrating with Apono using Terraform?** guidance. {% endhint %} Follow these steps to complete the integration: 1. On the [**Catalog**](https://app.apono.io/catalog?search=1password) tab, click **1Password**. The **Connect Integration** page appears. 2. Under **Discovery**, click **Next**. The **Apono connector** section expands. 3. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located. {% hint style="info" %} If the desired connector is not listed, click **+ Add new connector** and follow the instructions for creating a connector ([AWS](/docs/aws-environment/apono-connector-for-aws.md), [Azure](/docs/azure-environment/apono-connector-for-azure.md), [GCP](/docs/gcp-environment/apono-connector-for-gcp.md), [Kubernetes](/docs/kubernetes-environment/apono-connector-for-kubernetes.md)). {% endhint %} 4. Click **Next**. The **Integration Config** expands. 5. Enter a unique, alphanumeric, user-friendly **Integration Name** to identify the integration when constructing an access flow. 6. Click **Next**. The **Secret Store** section expands. 7. [Associate the secret or credentials](/docs/connectors-and-secrets/apono-integration-secret.md). {% hint style="info" %} If you select the **Apono** secret manager, enter the following values: * **Serve Account Name**: Name of the 1Password service account for Apono. The name must match the service account name defined in the 1Password platform. * **Service Account Token**: Unique token to authenticate the 1Password service account. Paste your token from 1Password into this field. {% endhint %} 8. Click **Next**. The **Get more with Apono** section expands. 9. Define the **Get more with Apono** settings.
SettingDescription
Custom Access Details(Optional) Instructions explaining how to access this integration's resources

Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters.

To view the message as it appears to end users, click Preview.
Integration Owner

(Optional) Fallback approver if no resource owner is found

Follow these steps to define one or several integration owners:

  1. From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.
  2. From the Value dropdown menu, select one or multiple users or groups.


NOTE: When Resource Owner is defined, an Integration Owner must be defined.

Resource Owner

(Optional) Group or role responsible for managing access approvals or rejections for the resource

Follow these steps to define one or several resource owners:

  1. Enter a Key name. This value is the name of the tag created in your cloud environment.
  2. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated.

    Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.


NOTE: When this setting is defined, an Integration Owner must also be defined.

10. Click **Confirm**.
💡Are you integrating with Apono using Terraform? If you want to integrate with Apono using Terraform, follow these steps instead of clicking **Confirm**: 1. At the top of the screen, click **View as Code**. A modal appears with the completed Terraform configuration code. 2. Click to copy the code. 3. Make any additional edits. 4. Deploy the code in your Terraform. Refer to [Integration Config Metadata](https://docs.apono.io/metadata-for-integration-config/integration-metadata/github) for more details about the schema definition.
#### Usage Now that the integration is complete, you can add 1Password to define the resource in an access flow. This allows requesters to securely access secrets stored in your Apono service, based on the access flow’s approval and provisioning rules. Follow the guidance in these articles to define the resource using 1Password: * [Define the resource (Self Serve Access Flows)](/docs/access-flows/creating-access-flows-in-apono/self-serve-access-flows.md#define-the-resource) * [Define the resource (Automatic Access Flows)](/docs/access-flows/creating-access-flows-in-apono/automatic-access-flows.md#define-the-resource) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.apono.io/docs/additional-integrations/secret-management/1password.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.