Skip to content

1Password Orientation - Vault Access and Passkeys

VIDEO TRANSCRIPT | Recorded: 2025-10-30 | Verify against current system state

Abstract

Team orientation session for migrating from Password Safe to 1Password. Covers the rationale for migration (two-factor authentication requirements), vault-based access control structure, passkey authentication for supported sites, browser extension usage, and the distinction between employee personal vaults and shared team vaults. Demonstrates login workflows for Google and Salesforce environments.

Key Procedures

  • Install 1Password browser extension for autofill functionality
  • Associate website URLs with password entries for automatic recognition
  • Use passkeys for passwordless login on supported sites (e.g., Google)
  • Create new login entries via browser extension prompt
  • Select correct vault (Employee vs App Dev Team) when saving new passwords
  • Apply tags to password entries for categorization and search
  • Search passwords by tag (e.g., AANP-CB, BluePay, Azure)
  • Navigate multiple Salesforce environments using 1Password
  • Request vault access via infrastructure team helpdesk ticket

Notable Statements

  • 0:00:21 "We are moving from password safe over to one password"
  • 0:00:26 "So many providers now require two-factor authentication, specifically like a one-time password, and you just can't do that with password safe very easily"
  • 0:01:18 "I think it's up to five licenses for guests, and then you have these 10 licenses for normal users" HEDGED
  • 0:01:21 "When you log in, you may only see the app dev team and the shared vaults"
  • 0:01:45 "These triage ones... I am figuring out where these pieces should live, if they're duplicates"
  • 0:01:57 "My goal is to get this down to zero before I leave" DATED
  • 0:02:32 "If you are on the dev team, you have full access. We did not make this view only"
  • 0:02:50 "If you attach a website to this list, this password will show up whenever you hit the site"
  • 0:04:04 "A pass key is a new type of authentication that doesn't require you to enter a password or two-factor authentication"
  • 0:05:36 "Everybody here is going to have at least two vaults, the first one to be their employee vaults"
  • 0:05:43 "The employee vault is any accounts that are related to you specifically"
  • 0:06:11 "Anything shared here is going to be visible to anyone else that is part of this group"
  • 0:06:22 "You do not want to store your personal employee records in app dev team"
  • 0:07:54 "By default, it's setting me to the app dev team because it's probably the last place I saved to"
  • 0:09:32 "It's very useful... especially useful for Salesforce because you've got so many different environments and so many different logins"
  • 0:12:13 "Will or just open up a help desk ticket and they can add somebody in"
  • 0:13:15 "The limit has only 10 members" DATED

Systems & Configurations

Systems Mentioned

  • 1Password (desktop and browser extension)
  • Password Safe (legacy system being replaced)
  • Salesforce (multiple environments - staging, production, sandboxes)
  • Google Workspace
  • SessionBoard

Specific Configurations

Item Value/Setting Timestamp Notes
Team member licenses 10 0:13:15 Account limit reached
Vault structure App Dev Team, Infrastructure, Core Passwords, Employee 0:01:21 Team-based access
Passkey support Enabled for Google 0:03:54 Passwordless login
Dev team access Full edit access 0:02:32 Not view-only
Salesforce login URLs login.salesforce.com, login.sandbox.salesforce.com 0:10:54 Multiple entry points

Credentials/Access Mentioned

  • IT Support account (Google)
  • Infrastructure team manages vault access
  • Helpdesk ticket process for adding new users/vault access

Vendor Contacts Mentioned

None mentioned in this recording.

Errors & Troubleshooting

  • Issue: Account member limit reached
  • Cause: 10-member license limit on team plan
  • Resolution: Jeff offered to remove himself so Matt could be added
  • Timestamp: 0:12:56

Transcript Gaps & Quality Notes

  • Multiple unidentified speakers (Speaker 2, 3, 4) - likely team members being trained including McKenna, Matt, Keith, Shrini
  • Visual demonstrations of browser extension and vault navigation not captured
  • Reference to "Plusify" unclear - may be vendor name or transcription error
  • Recording is part of a larger meeting/orientation session