Password vaults for teams and agents

Watch

Chapters

Each chapter starts the class video at that moment.

1. Personal vs. business accounts1:14:08
2. Create a shared vault1:14:31
3. Pick the account; share an item link across accounts1:14:48
4. Several vaults per business account1:15:36
5. Migrating with computer use: add a check1:16:04
6. Move an item; choose which vaults can see it1:16:36
7. A vault only you and your agent can open1:16:49
8. Limited cards: “an intern with six PhDs”1:17:07
9. Agents as customers (JP’s forecast)1:17:39
10. Agents now fill in applications and forms1:17:54
11. A form, end to end: the agent drafts, you sign1:18:21
12. Identity items behind a second password1:19:20
13. Follow-up protocols1:20:16

From the class

What this module covers

The video opens on a member's point: a personal account can't be connected to a business account. JP then built a demo vault and showed how he shares access with people and with an agent.

• You can't connect a personal account to a business account. You can switch between the two as a single user.
• Create a new vault for what you share with a specific person or team.
• Pick the account first. A business account is the one to use if you have employees. Keys don't move easily between accounts, but you can share an item's link and the other person can add it.
• A business account can hold several vaults.
• Migrating many passwords by hand is slow. An agent with computer use can move items, and he would not do a blanket move. Put a check in front of each one.
• Use Move to choose which vaults, and so which people or agents, can access an item.
• Keep a vault that only you and your agent can open.
• Treat the agent like a capable intern: give access carefully. If you give it a card, use a limited one with authentication, never an unlimited one.
• More applications and forms are filled in by bots, and some of those bots are fraudulent.
• A form, end to end: the agent found a consent form in email and filled it in, asking him to confirm details. It left the signature to him and sent the form only after he had reviewed and signed it.
• Password managers can hold identity items. The agent pulled identity details only after an authentication request through the security agent and his approval code.
• Follow-up: his agents check back once a day or once a week on the status of a request.

Try it

Put it to work

Never show a vault's secret key, recovery kit or item list on a shared screen.

Passwords and keys stay in the password manager. Nobody pastes them into a chat. Know who can revoke access, and how fast.

1. Create one shared vault for one teammate, and move three low-risk items into it, one at a time.
2. Create an agent-only vault with one low-risk credential.
3. If you test paying with an agent, use a card with a low limit and authentication.
4. Write a follow-up rule for one task an agent sends on your behalf.

Move these logins from [vault A] to [vault B] one at a time. Before each move, show me the item name and the destination vault and wait for my OK. Don't move anything in bulk.

After you send a request for me, check back once a day for a reply. When it's acknowledged, tell me in one line. If there's no reply after three days, draft a follow-up for my approval.

Find the form in my email and fill it in using my identity item in the password manager. Request access through the security bot first. Leave the signature blank and show me the completed form before anything is sent.

Check your work

You're done when

• One teammate can see exactly the items you meant to share, and nothing else.
• Your agent has its own vault.

Tools

Mentioned in this module

• 1Password — Business and personal accounts, several vaults, item links, Move, and identity items.

Also on the class guide

Written before class

• Pre-class guide: what to tell IT
• Pre-class template: the AI employee's job description

Between classes

WhatsApp and YouTube

Join the AI Practicum WhatsApp group

Hive Research Institute on YouTube