A way to create vaults

Is there any way we can expose this to the user? There isn't currently any mechanism to automate vault creation, short of scripting something around op vault. Exposing this in the SDK would be a game changer for automation.

@demon

Hi @demon, thank you for your feedback! Can you describe your use-case around creating vaults and why this would be a game changer for automation?

At $DAYJOB, we are using the 1Password Connect Server alongside external-secrets. We currently have a mapping of 1 vault -> 1 k8s cluster. We automate all of this using Pulumi & Flux -- the notable exception being the creation of vaults (& connect servers).

I've got Pulumi shelling out to op which...works...but isn't very elegant. If we had vault creation (& deletion) available to us in the Python SDK, we could write a package around it to properly manage the resources.

@demon

Thanks for your feedback @demon and explaining your use-case in more depth. We are currently in the process of prioritizing vault CRUD in our roadmap for this year, so please keep an eye out for that! Can you describe your current automation process and how you would like to implement the creation of vaults and Connect servers?

Just to add to this. It's absolutely imperative for us to be able to programmatically create Vaults. We're an MSP and would like to use 1Password to store a Vault per customer but we've got 1000+ supported customers.

@simonbaker-tio

Hi @simonbaker-tio,

Thank you for sharing your feedback and for your interest from the MSP perspective. We’d love to dive deeper into your specific use case as we may already have tools that could support you. Please reach out to us at dev-products@agilebits.com, and we’ll ensure you’re connected with the right team at 1Password.

Looking forward to hearing from you!

@sadiaazmal

Is there any way we can expose this to the user? There isn't currently any mechanism to automate vault creation, short of scripting something around op vault. Exposing this in the SDK would be a game changer for automation.

Hi @sadiaazmal, any updates regarding this enhancement?
We'd love to be able to programmatically create Vaults and manage them (specifically the "Update vault access & permissions" functionality would be a game changer instead of using share-links for each secret) via the SDK.

Thank you!

@MarioBartolome

Hi @MarioBartolome

Thank you for reaching out and sharing your feedback on programmatically creating and managing vaults, including updating vault access and permissions. We recognize how impactful this functionality would be, and it’s something we’re actively considering as we balance priorities across our roadmap.

To better understand your needs, could you share more details about your specific use case and the value this feature would provide? Additionally, do you have a preferred authentication method for managing vaults and permissions? Your insights will help us shape the feature to meet your needs effectively.

@sadiaazmal

Hi @sadiaazmal,

Ideally we would like to integrate 1Password's Python SDK with our application's backend to achieve the following:

Use a Service Account with enough permissions to create and manage new vaults
Once a user logs in a new Vault is generated for them.
- Not possible from the SDK but possible from the CLI.
New secrets are generated for the user.
- Unfortunately not in a new Vault at the moment, but in a predefined Vault as the Service Account can't use the SDK to achieve this.
The user gets access to the vault and its secrets.
- Not to the entire Vault, as it is the predefined one at the moment and not a user-specific Vault, but only to the specific secrets. We are currently sharing a share-link for the secrets with the users.

All of these operations are possible from the CLI (op vault ...), but using it from a programatic environment sets a bad precedent and is prone to input sanitization issues.

Thank you!

@MarioBartolome

@MarioBartolome Thank you for providing more details about your use case, this insight is invaluable as we shape our 2025 roadmap. We'll keep your input in mind as we refine our plans, please let me know if you have any additional thoughts or requirements.

+1 for sdk-accessible vault creation. It would greatly assist us in onboarding users quickly and without manual intervention.

+1 This would be a great feature for my use case where I want a single service account to be able to create other vaults and then have access to manage all items in the vaults it creates

Are there any developments in this to report? Maybe a beta version?

@sadiaazmal

Hi @sadiaazmal,

Can you share any insights about the 2025 roadmap that would include this issue?

Thanks!

Thank you all for expressing your need for a way to create vaults. This is something we're actively evaluating as a potential addition to our roadmap.

Your insights are incredibly valuable, and if you're interested, a quick chat would really help us better understand your use cases and ensure we're building the right tools to support you. Feel free to book a 20-minute meeting with me here.

Alternatively, you're welcome to share your use case in this thread—whatever works best for you. Thank you again for your feedback!

@sadiaazmal

Hi @sadiaazmal, apologies it's been a while for me. We still have this use case and I'm more than happy to talk it through with you. If you send me a link I'll happily book something.

Another vote for this to be prioritized. We use one vault per customer to keep their secrets separate and ensure one tenant doesn't have access to the others' secrets. Currently, we have to manually create each vault whenever a new customer signs up, but this will not be feasible at scale.

@simonbaker-tio

Thank you for reaching out again @simonbaker-tio and for sharing your use-case @jm-pando. These insights are incredibly helpful for prioritization. Here is an updated link to book a call. I look forward to hearing more about your use-case!

Another strong vote for prioritizing this feature. As others have pointed out, the lack of programmatic vault management severely limits scalability. This becomes particularly problematic when new service accounts are required to access newly created vaults, as outlined here: https://developer.1password.com/docs/service-accounts/manage-service-accounts#if-you-need-to-change-a-service-accounts-permissions-or-vault-access.

Additionally, the only official reference I’ve found regarding parallelism constraints is in the Terraform provider documentation: https://registry.terraform.io/providers/1Password/onepassword/1.4.2/docs#use-with-1password-cli. Without API support for vault management, working around these limits often involves creating many fine-grained vaults manually — which adds significant operational overhead.

Altogether, the combination of these limitations makes it difficult to use 1Password effectively at scale in IaC environments.

Without managing vaults, that python library is basically useless as one HAS TO rely on the 1password CLI to get things done in a script (python or not).

Another vote for a programmatic Vault operations.

I would like to develop a plugin for an access broker that will allow us to:
Create a vault
Once approved by the access broker, add a user to the vault with appropriate permissions (i.e. add as read-only, add as read-write)
Remove a user from the vault when their access expires
Compare list of users with access to the vault against users with access in the access broker to ensure membership hasn't drifted.

So the following commands would be necessary for this workflow.

If possible both in python and in golang

op vault create
op vault delete
op vault group grant
op vault user grant
op vault group revoke
op vault user revoke

@demon

Hey folks!

We’ve recently released support for vault management. Give it a try and let us know what you think.

Thank you for being users of 1Password Developer! 🙂

cc: @demon @BrandonNolet @vhatsura @dreid @szeestraten-nina @hh2k @simonbaker-tio @jm-pando @osama-AI71
@renepupil @patrick-adroit @jess-work

Navigation Menu

Repository navigation

A way to create vaults #36

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

A way to create vaults #36

Description

Activity

sadiaazmal commented on May 28, 2024

demon commented on May 30, 2024

sadiaazmal commented on Jun 3, 2024

simonbaker-tio commented on Oct 8, 2024

sadiaazmal commented on Oct 9, 2024

MarioBartolome commented on Jan 16, 2025

sadiaazmal commented on Jan 16, 2025

MarioBartolome commented on Jan 16, 2025

sadiaazmal commented on Jan 20, 2025

kchoudhu commented on Mar 10, 2025

ck-pando commented on Mar 18, 2025

BrandonNolet commented on May 2, 2025

MarioBartolome commented on May 9, 2025

sadiaazmal commented on May 9, 2025

simonbaker-tio commented on Jul 7, 2025

jm-pando commented on Jul 7, 2025

sadiaazmal commented on Jul 8, 2025

nb-exerp commented on Jul 22, 2025

renepupil commented on Nov 3, 2025

jess-work commented on Feb 18, 2026

vithyeakim commented on Mar 16, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions