# Building 1Password Published articles for Building 1Password. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Evolving AI maturity for our user experience team DevFeed: [Evolving AI maturity for our user experience team]() Original publisher: [Read original article]() Author: info@1password.com (Matt Davey) Published: 2026-08-07T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [AI Chat]() Tags: [ai](), [building-1password](), [community](), [design](), [experimentation](), [prototypes](), [user-experience](), [workflow]() ### AI overview The article presents an AI maturity model for user experience teams, arguing that mature adoption improves decisions, collaboration, and product experiences rather than merely accelerating work. ### Source excerpt AI is changing how products get made. For user experience teams, that means the very shape of the work is changing. There are two key elements of user experience design. On one side is craft: the interaction, nuance, visual judgement, emotional texture, and other qualities that make a product feel considered. On the other side are systems, strategy and behavioural thinking: journeys, concepts, mental models, product architecture, behavioural patterns, and the shared systems and languages that help teams make better products. AI tooling has created opportunities to deepen both of these skillsets. Designers can now get closer to the front-end experience using real components, real data, and realistic prototypes, instead of hoping that important details survive the process. At the same time, we now have more ability to work upstream, shaping product decisions at the strategy level. Now, rather than strategy and execution conflicting with each other, they can harmonize more closely, held together by a team that can think clearly and ship responsibly. The challenge of AI is that working faster simply produces more work; it doesn't always mean that work is better. For UX and design teams, AI maturity is not simply about whether a team uses AI, but whether it improves the quality of our decisions, our collaboration, and the experiences we ship. An AI maturity model for user experience teams In the early stages of adoption, AI use tends to be experimentation without much structure. A designer might use it to generate a few rough ideas or make an impressive prototype, but it falls apart when the team asks how it would actually work. To avoid the pitfalls of confusing AI enthusiasm with maturity, 1Password has been investing in AI fluency across the company. To make that progress visible and chart a path to impact, we have developed a simple maturity model for design teams, which charts AI use from limited, reactive, developing, embedded, and finally through to leading. Head ## Scaling security reviews at 1Password: Solving the context and nondeterminism problems DevFeed: [Scaling security reviews at 1Password: Solving the context and nondeterminism problems]() Original publisher: [Read original article]() Author: info@1password.com (Megan Barker) Published: 2026-07-30T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [Security](), [Code review](), [Large Language Model](), [long-context](), [GitHub](), [Python](), [Go Language](), [pull-requests]() Tags: [ai](), [building-1password](), [code](), [context-window](), [developers](), [github](), [go](), [llm](), [nondeterminism](), [python](), [review](), [security]() ### AI overview 1Password describes how it evolved SAGE to scale security code reviews across large repositories. The v2 design addresses limited LLM context and nondeterministic outputs by generating directory-level scaffolding that compresses structural security context, with a Python proof of concept being productionized in Go. ### Source excerpt In our last post, we shared how we began to scale our security code review process with SAGE. We discussed how we gathered historical Product Security (ProdSec) review records to create a 1Password-specific ruleset, the three-stage Finder/Critic/Judge pipeline, and the limitations of our v1 implementation. Above all, human ProdSec reviewers still had to bring full context to the findings: where the trust boundaries lie, which directories are sensitive, and whether mitigations exist elsewhere in the codebase. Our goal for v2 was to help SAGE understand our entire codebase. Many of our GitHub repositories are huge, including our client and server monorepos. That means we have way too much information to fit within any LLM's context window. We had to find a way to let SAGE perform deeper reasoning about the PR diffs it reviews without the codebase itself. There was another hurdle. As we built v2, we ran into a fundamental LLM trait: they can't reliably produce the same output twice. We knew we had to do our best to manage this nondeterminism so we could trust SAGE to be a relatively consistent security reviewer. We had two things to figure out: how to fit a lot of data into a context window, and how to get consistent output from inherently inconsistent tools. If we could solve those riddles, SAGE wouldn't just know 1Password, it would finally understand it. And it would earn the name SuperSAGE. Compressing context with scaffolding As it turns out, our Security Research team had already developed a Python proof of concept designed to compress our code context. It was a set of LLM prompts that generated one SCAFFOLDING.md file per source directory. Those scaffolding files carried compressed structural context like sensitivity ratings, attack surfaces, trust boundaries, and file summaries. It was a great foundation; we just had to productionize it as a Go rewrite on top of SAGE v1's model-agnostic llm.Client harness. To start, the PoC took inventory of our code structure. ## The data platform 1Password needed didn't exist. So we built it. DevFeed: [The data platform 1Password needed didn't exist. So we built it.]() Original publisher: [Read original article]() Author: info@1password.com (Wayne Duso; Mandy Gu; and Amie Bright) Published: 2026-07-22T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [data](), [Data Infrastructure](), [data-governance](), [real-time](), [Unified Access](), [Artificial Intelligence]() Tags: [agentic](), [ai](), [building-1password](), [data](), [data-governance](), [data-infrastructure](), [developers](), [real-time](), [sql](), [systems](), [unified-access](), [workflows]() ### AI overview 1Password describes building an internal data platform to make business data accessible, trustworthy, and available in real time across product, finance, engineering, analytics, SQL, APIs, dashboards, and AI workflows. The effort addresses bottlenecks caused by a centralized data lake, bespoke pipelines, and tightly coupled storage, governance, and compute. ### Source excerpt Consider a few tasks that take place across every business, every day: A product team ships a feature and wants to know if customers are using it successfully. A finance team needs customer and account information for planning. An analyst needs definitions to create a report. An AI assistant needs operational context to answer a business question. Those sound like different workflows, but they all rely on the same underlying data. And each one of these actors, across each of these teams, needs that data to be both accessible and trustworthy. At 1Password, trust is at the center of everything we build. Millions of people and businesses rely on us to protect the credentials, secrets, and access workflows that power modern work. The same principle applies to our own internal data. As our products, systems, and use of AI evolved, data became a shared dependency across the business. It powers everything from Unified Access andsecure agentic access patterns for customers, to the workflows used by product, finance, and engineering teams. As those systems grew, so did the number of people and applications that depended on our internal data. But our data infrastructure did not respond well to this. We had built a centralized data lake supported by a growing collection of bespoke data pipelines and one-off solutions. Each new use case required another integration or transformation. Over time, the data platform became a bottleneck: teams turned to CSVs to move faster, and data engineers spent more time maintaining pipelines than enabling new capabilities. What we learned was that manually moving data was no longer enough. Data needs to be available in real time, accessible wherever it's needed, and trusted through the forms our customers need, whether that is through SQL, APIs, dashboards or AI workflows. Privacy and governance need to be built into data the moment it's created so every downstream use remains secure and unambiguous by design. This is the foundation we're build ## How 1Password's culture is evolving DevFeed: [How 1Password's culture is evolving]() Original publisher: [Read original article]() Author: info@1password.com (Katya Laviolette) Published: 2026-07-02T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [Artificial Intelligence](), [Cybersecurity](), [Security & Privacy]() Tags: [ai](), [building-1password](), [collaboration](), [company](), [cybersecurity](), [growth](), [how-we-work](), [integrations](), [learning](), [life-at-1password](), [performance](), [scale](), [tools](), [work](), [workflows]() ### AI overview An article about how 1Password is evolving its workplace culture as the cybersecurity industry and company change. It discusses AI fluency, internal AI tooling adoption, AI Champions, employee learning, trust, privacy, responsibility, collaboration, and balancing high performance with sustainable work. ### Source excerpt The cybersecurity landscape is changing fast. At 1Password, that means we're continuously evolving what we work on, how we work, and the culture we need to achieve our goals. Last year, I wrote about what high performance means to us. As our industry continues to move quickly, I want to share a more holistic view of the culture we're continuing to shape and strengthen to meet this moment. I recently joined the Culture Uncoveredpodcast to talk about what that looks like in practice. Now, I'm bringing some of those reflections here for anyone exploring a career at 1Password, and for people-focused practitioners curious about how culture evolves inside a growing security company. Listen to this episode on Apple Podcasts null Listen now Listen to this episode on Spotify null Listen now Building on a strong foundation 1Password was founded in 2005 and has grown steadily for over two decades. I joined in early 2022, the same year we closed our Series C, which was, at the time, the largest round raised by a Canadian company. Since then, we've entered a chapter of incredible growth. As we scale, a big part of my role is to honour the culture that got us here while making sure our people and systems are ready for our future. Here's what we're focused on right now. How we're enabling our people to lead with AI This is one of the most significant shifts happening across our company and our industry. At 1Password, we're continuing to invest in our people to help them develop AI fluency, use best-in-class tools and integrations with confidence, and do their best work. We've reached roughly 98% adoption of AI tooling internally, with AI Champions embedded across departments. "AI Champions" are employees who are trained to experiment with workflows, drive peer learning, and build AI confidence in practical ways. What we've learned along the way is that the process is about being curious, listening intently to employee feedback, and building trust. Our team members have important q ## What an AI hackathon taught us about being builders, not just writers DevFeed: [What an AI hackathon taught us about being builders, not just writers]() Original publisher: [Read original article]() Author: info@1password.com ( Chantelle Sukhu) Published: 2026-06-23T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [Artificial Intelligence](), [User experience (UX)](), [Information Architecture](), [Software as a service](), [systems](), [Tooling]() Tags: [2026](), [ai](), [architecture](), [b2b](), [building-1password](), [hackathon](), [saas](), [ux]() ### AI overview This article describes how 1Password's content design team participated in an AI-themed hackathon to apply content design, information architecture, systems thinking, and real-time AI prototyping to product improvement. The team focused on the 1Password SaaS Manager Savings tracker, which reports reclaimed licenses and calculates cost savings for B2B administrators. ### Source excerpt When 1Password announced we were having an AI-themed Hackathon, my first thought was that the content design team had to be involved. Over the last few months, our content design team saw massive changes not only in tech but also in our ways of working. It felt like everything was shifting to AI all at once: how we designed, prototyped, built new features, and collaborated across teams. I didn't want our team watching from the sidelines. Content designers often do great work, but in the margins of larger design projects. This felt like the perfect moment to show how words can shape a great UX experience. And ironically, being the anointed "wordsmiths" of 1Password's products is just a fraction of what we do. Content designers shape page structure, look at the information architecture, create journey maps, and are systems thinkers at heart. We look at: what users need to know, when they need to know it, how information shows up, and how each action builds towards the best possible outcome for the customer. AI lets us take those skills and supercharge them. Content designers can use AI to prototype the flow of information in real time. When you're building with AI, you can look beyond a single screen or interaction to see how a user's entire journey unfolds. That's exactly the kind of thinking that content designers do best, and the Hackathon was our chance to prove it. The opportunity: Uncovering value in 1Password SaaS Manager Participating was the easy part. We have a small but mighty content design team which include the talented Amar Majali and Grace O'Neil, who I happily "voluntold" into the hackathon. Our design leadership was genuinely excited to see what three content designers could do with AI. The hard part was deciding what area of the product we wanted to improve. We tossed around a few ideas but came across a report that struck our interest: the SaaS Manager Savings tracker. It's a report that shows reclaimed licenses and calculates cost savings. This re ## Strengthening Snow for the open source community DevFeed: [Strengthening Snow for the open source community]() Original publisher: [Read original article]() Author: info@1password.com (Daryl Martin and Christian Rask) Published: 2026-06-16T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [open-source-security]() Tags: [building-1password](), [contributors](), [cryptographic](), [developers](), [open-source](), [pull-requests](), [review](), [rust](), [security](), [testing]() ### AI overview 1Password funded and published an independent security assessment of Snow, an open-source Rust implementation of the Noise Protocol Framework. The review found 10 issues; eight, including a nonce-handling flaw and an invalid-PSK panic, have been resolved and validated. ### Source excerpt At 1Password, we regularly invite outside experts to challenge our assumptions and strengthen our security. We encourage security researchers to participate in our bug bounty programs, and have spent years building a collaborative research environment. We also believe in the benefit of open source software and standards, which raise the bar for the industry as a whole, while ultimately benefiting our 1Password customers. That's why we funded an independent security assessment of the open source library Snow, worked closely with the maintainer on remediation, and are making the results publicly available for anyone to review. Where to read the report The results of the independent security assessment are available now for anyone who wants to learn more. Read the report Why we invested in Snow Snow is a Rust implementation of the Noise Protocol Framework, a system for building secure channels using customizable cryptographic handshake patterns based on Diffie-Hellman key exchange. We rely on Noise-protected channels in parts of 1Password. Since Snow gives Rust developers an implementation of that framework, that makes it, for us, part of the security foundation we care about getting right. Funding validation on Snow allows us to improve something we care deeply about while giving back to the open source community that helps make 1Password possible. We are active contributors to Snow. The pull requests we've opened and the independent security assessment we funded reflect our commitment to helping strengthen the project. What Trail of Bits found Trail of Bits reviewed Snow through a combination of manual review and automated testing over four engineer-weeks. Their report identified 10 findings in total: one medium-severity issue, one low-severity issue, and eight informational findings. The most important issue discovered was a nonce-handling bug that could let an attacker permanently disrupt an encrypted channel without knowing any cryptographic secrets. Another findi ## The architectural reason 1Password can't read your vault data DevFeed: [The architectural reason 1Password can't read your vault data]() Original publisher: [Read original article]() Author: info@1password.com (Rick Fillion; Wayne Duso; K.J. Valencik; Daryl Martin) Published: 2026-05-20T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [Architecture & Design](), [Encryption](), [Cryptography](), [Security](), [passwords](), [data](), [Server](), [QR Code]() Tags: [architecture](), [building-1password](), [cryptographic](), [data](), [encryption](), [post](), [product](), [security](), [servers]() ### AI overview The article explains that 1Password cannot technically decrypt or read users' vault data. Vault items are encrypted locally before leaving the device, while the Secret Key and account password remain on users' devices and are never transmitted to or stored on 1Password's servers. ### Source excerpt There's a question we get asked constantly, and it's the right one to ask: "Can 1Password see the contents of my vault?" The answer is no, and it's because of how we built the product, not just a promise we're making. That's an important distinction, because "we promise" has never been an acceptable answer in this industry. After all, promises get broken, and companies get compromised, acquired, and are under constant attack from threat actors. 1Password's commitment to our security principles is genuine, but what matters more is how we've built that commitment into our product and architecture, and the transparency we back it up with with our security white paper. So here's the precise answer: The way 1Password is built means that we are incapable, on a technical level, of decrypting and reading your vault contents. We're not policy-prevented or contractually restricted; we are technically incapable. This post explains what that means, why we built it this way, and what the real tradeoffs are. Your data is encrypted before it ever leaves your device When you save a password, a credit card number, or a note in 1Password, the first thing that happens is encryption, and it happens on your device, before any data moves anywhere. Encryption here doesn't mean we "hide" or "scramble" your data and promise not to look. It means your plaintext vault item is transformed into ciphertext using cryptographic keys that are only available on your devices. Without these keys, 1Password is unable to decrypt and read your data. The two keys in question are your 128 bit Secret Key (a 34-character value separated by dashes) and your account password. Together, these produce the cryptographic key that locks and unlocks your vault. Here's the critical part: neither your Secret Key nor your account password is ever transmitted to 1Password or stored on our servers. We never possess the keys needed to decrypt your vaults. When you set up your 1Password account on a new device, you're not ## Device Trust MCP Server: Natural language queries for your entire fleet DevFeed: [Device Trust MCP Server: Natural language queries for your entire fleet]() Original publisher: [Read original article]() Author: info@1password.com (Evan Sandhu) Published: 2026-05-14T00:00:00Z Content type: release Language: en Sources: [Blog on 1Password Blog]() Topics: [Device Trust](), [Model Context Protocol](), [Security](), [Open Source](), [API](), [Claude](), [Large Language Model](), [ChatGPT](), [cursor]() Tags: [agents](), [ai](), [ai-agents](), [ai-tools](), [api](), [building-1password](), [chatgpt](), [claude](), [compliance](), [device-trust](), [mcp](), [mcp-server](), [open-source](), [platform](), [security]() ### AI overview 1Password announces the open-source Device Trust MCP Server, which connects Device Trust data to AI tools such as Claude and ChatGPT. Security and IT teams can query device-fleet status in natural language, with actions logged and auditable, through the MCP ecosystem and the Device Trust API. ### Source excerpt Today we're releasing the 1Password Device Trust MCP Server, an open-source server that connects your Device Trust data directly to the AI tools your team already uses, like Claude or ChatGPT. It's available now for all customers on Device Trust Connect. As AI agents take on more of the work across your organization, IT and security teams need visibility and control that keeps pace. The Device Trust MCP Server is part of how 1Password is extending that control to the way security teams actually work today, inside AI tools, in plain language, with every action logged and auditable. Once it's running, you can query your entire device fleet without leaving your AI client. Which devices have disk encryption off? Who owns the machines failing compliance checks? How long does it typically take to resolve a specific issue across the fleet? Instead of navigating dashboards or writing custom scripts, you just prompt. What is MCP, and why does it matter? If you use AI tools like Cursor or Claude, you may have already come across the Model Context Protocol (MCP). MCP has become the standard way to connect LLMs and AI agents to data sources and tools. It's an open standard that lets AI tools connect to external data sources and take action on your behalf, with built-in controls over what those tools can access and do. It's supported by every major AI platform, and the ecosystem has grown from around 1,200 servers in early 2025 to over 6,400 today. IT and security practitioners are increasingly doing their work inside AI-powered tools, and MCP is what makes those tools useful for real administrative workflows. The Device Trust MCP Server plugs your device security data into that ecosystem. Instead of switching between tools, admins can stay in their AI client of choice and get answers in seconds. What you can do with the Device Trust MCP Once connected, you can ask questions like: "Which devices are currently failing checks?" "Who owns the devices with disk encryption disabled?" ## A first step toward post-quantum security DevFeed: [A first step toward post-quantum security]() Original publisher: [Read original article]() Author: info@1password.com (Daryl Martin) Published: 2026-03-31T00:00:00Z Content type: release Language: en Sources: [Blog on 1Password Blog]() Topics: [Cryptography](), [web applications]() Tags: [algorithms](), [attacks](), [browser](), [building-1password](), [chrome](), [communication](), [cryptographic](), [cryptography](), [data](), [deployment](), [encryption](), [firefox](), [infrastructure](), [launch](), [post-quantum](), [quantum](), [security](), [tls](), [web]() ### AI overview 1Password has deployed hybrid post-quantum key exchange for web-application connections, protecting compatible-browser traffic against future harvest-now, decrypt-later risks. ### Source excerpt At 1Password, our mission is simple: to protect people's most critical information, their credentials. At the time of writing this post, I personally have 291 items in my vault, so the long-term confidentiality of this data is critical to myself and every 1Password user. We are thrilled to announce the first major milestone in our post-quantum cryptography (PQC) journey, the successful deployment of PQC on 1Password's web application. If you're using a PQC-capable browser, such as Chrome or Firefox, your data is protected today with no action required. The threat of a large-scale quantum computer, sometimes referred to as a cryptographically relevant quantum computer (CRQC), is its potential to break the public-key cryptographic algorithms. These algorithms are used in most communication protocols and digital signature schemes. While it's unclear that a quantum computer powerful enough to break the public key cryptography will ever exist, we are not waiting for one before taking action to protect your data. "Harvest now, decrypt later" attacks are a practical concern where adversaries intercept and store encrypted traffic today with the intention of decrypting it in the future, once quantum computers become powerful enough. We are putting protections in place now to ensure the long-term confidentiality of our customers' data well into the future. This is the first step in our long-term plan to protect customer data and withstand harvest-now, decrypt-later attacks. We will provide updates in the future as we migrate other parts of our infrastructure to support PQC, as we firmly believe that cryptographic designs should be done in the public. What we delivered We began our PQC rollout where it matters most for long-term confidentiality: internet-facing traffic. When a browser connects to 1Password, it establishes a TLS session using public-key cryptography to negotiate encryption keys. Historically, that key exchange relied solely on classical algorithms like elliptic ## Next-generation automated provisioning, without compromising zero-knowledge security DevFeed: [Next-generation automated provisioning, without compromising zero-knowledge security]() Original publisher: [Read original article]() Author: info@1password.com (Chas Lynch) Published: 2026-03-17T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [Cryptography]() Tags: [api](), [automation](), [building-1password](), [cryptographic](), [cryptography](), [developers](), [encryption](), [identity](), [saas](), [security](), [server](), [zero-knowledge]() ### AI overview 1Password describes automated user provisioning in a zero-knowledge system, focusing on the risks of trusting a server to distribute or replace cryptographic keys. ### Source excerpt Automating user provisioning sounds simple, until you remember everything that provisioning really touches. For most SaaS products, SCIM is "just" user and group lifecycle management. Your identity provider calls an API, accounts get created, access is assigned, and offboarding removes it. But for 1Password, provisioning intersects with something far more sensitive: the cryptographic foundation that protects every vault. 1Password is end-to-end encrypted by design. We do not hold your encryption keys and cannot see your vault contents. This provides a powerful guarantee that even if 1Password's servers were to be compromised, your data would remain unreadable, as the keys required to decrypt it are never accessible to us. That model is why customers trust 1Password with their most sensitive credentials, but it also makes automation genuinely hard. After all, how can we automate provisioning inside a zero-knowledge platform, without reintroducing trust in the server? That is the problem Automated Provisioning hosted by 1Password solves, and it's why our approach is fundamentally different from other provisioning options on the market. The hidden tradeoff in "hosted SCIM" Most hosted provisioning solutions are built on a straightforward assumption: the service performing provisioning can be trusted to manage the system state, distribute keys, and act as an authority. This is what makes many SCIM implementations "easy" to host, but that assumption quickly breaks down in a zero-knowledge system. If a server can create, hand out, or swap cryptographic keys without independent verification, then clients are ultimately trusting the server as a source of truth. Even if the threat is theoretical, the trust model is real, and even a theoretical gap matters for 1Password. The problem Public key cryptography is built around two keys: a private key that must remain secret, and a public key that can be shared freely. When you share something securely, you encrypt it using the rec ## Automated Provisioning hosted by 1Password: A Simpler, Smarter Way to Manage Access DevFeed: [Automated Provisioning hosted by 1Password: A Simpler, Smarter Way to Manage Access]() Original publisher: [Read original article]() Author: info@1password.com (Allie Dusome) Published: 2026-03-17T00:00:00Z Content type: news Language: en Sources: [Blog on 1Password Blog]() Topics: [Provisioning](), [Security](), [API](), [Multi-tenancy](), [Confidential Computing](), [Single sign-on (SSO)](), [zero-knowledge](), [Software as a service]() Tags: [api](), [building-1password](), [developer](), [enterprise](), [infrastructure](), [multi-tenancy](), [news](), [oauth](), [security](), [zero-knowledge]() ### AI overview 1Password announces Automated Provisioning hosted by 1Password, alongside enterprise multi-tenancy, verified emails, an OAuth-based Users API, and Security Automation integrations for its Enterprise Password Manager. ### Source excerpt Modern enterprises aren't just adding employees; they're adding subsidiaries, multiple teams, contractors, AI builders, temporary projects, and new SaaS tools every week. And every new addition to a company's ecosystem also brings more credentials to manage. Unfortunately, not all of those credentials can be managed by solutions like single-sign-on (SSO) or privileged access management (PAM). Many of them might be stored in shared spreadsheets, developer environments, browser sessions, and automation workflows that traditional identity security systems were never designed to govern. This results in identity sprawl, operational drag, and an overall widening of the Access-Trust Gap. In the face of this ever-expanding attack surface, security leaders are left struggling to deploy credential security across every team and workflow, without having to build more infrastructure just to manage their infrastructure. In light of these issues, today we're introducing a new evolution for 1Password Enterprise Password Manager (EPM): enterprise-grade provisioning, structure, governance, and security automation built directly into the platform. This launch includes: Automated Provisioning hosted by 1Password Enterprise multi-tenancy Verified emails from 1Password OAuth-based Users API and new Security Automation integrations Together, these capabilities make EPM easier to deploy, easier to scale, and easier to operate as the foundational tool of modern identity security. Introducing Automated Provisioning, hosted by 1Password Automated Provisioning hosted by 1Password is our next-generation provisioning solution, built directly into 1Password. Automated Provisioning requires no servers to deploy, no bridge to maintain, and no ongoing infrastructure burden. In early testing, the response from admins was immediate. "We were done in about five minutes. We set everything up from scratch, added the integration in Okta, and it worked immediately. Adding and removing users was seamless. ## Automating SOC workflows with 1Password Enterprise Password Manager DevFeed: [Automating SOC workflows with 1Password Enterprise Password Manager]() Original publisher: [Read original article]() Author: info@1password.com (Clarence Wong) Published: 2026-03-17T00:00:00Z Content type: release Language: en Sources: [Blog on 1Password Blog]() Topics: [SOC](), [API](), [Automation](), [OAuth 2.0](), [Authorization](), [Security](), [Authentication]() Tags: [api](), [apis](), [authentication](), [automation](), [building-1password](), [compliance](), [developers](), [integrations](), [oauth](), [security](), [security-operations-center](), [soc](), [workflows]() ### AI overview 1Password announces the public preview of its Users API for Partners and new security automation integrations for Enterprise Password Manager. The capabilities let SOC teams programmatically suspend or restore users when risk is detected, using OAuth 2.0 authentication and delegated, scoped authorization within coordinated security workflows. ### Source excerpt Introducing our Users API for Partners in public preview and new Security Automation integrations that enable SOC teams to execute programmatic user actions within automated workflows in 1Password Enterprise Password Manager. Modern security teams increasingly rely on integrated security operations center (SOC) workflows that correlate signals and alerts, while orchestrating detection responses in real time. Behind every alert is an identity: a person, a service account, an API key, or an AI agent. However, when remediation requires manual steps, investigation and response slows, increasing security risks. Organizations are also expected to maintain continuous compliance via clearly enforced access controls and auditable processes. Today, 1Password is expanding the 1Password Enterprise Password Manager (EPM) through the public preview of the Users API for Partners, enabling security teams to respond to incidents faster during active security events. Powered by the Users API for Partners, security automation integrations with partners like CrowdStrike, in addition to BlinkOps, Elastic, Sumo Logic, Tines, and Torq enable mutual customers to automatically suspend or restore users in EPM when risk is detected. Together, these capabilities embed identity actions programmatically into coordinated SOC workflows. Moving from visibility to response with the Users API for Partners The Users API for Partners, now in public preview, enables execution of user-related actions within 1Password EPM. The API uses OAuth 2.0-based authentication designed for secure, enterprise-grade security. This enables ecosystem partners to build integrations for 1Password Enterprise Password Manager and use delegated, scoped authorization to list users, suspend access when risk is detected, and restore access after remediation. We're also introducing api.1Password.com as the single access point to 1Password APIs, accessible to ecosystem partners looking to build solutions with 1Password. The Users