Setting Up Passwords and Logins for Your AI Teammate

A step-by-step way for a small business to set up credentials, two-step checks, and recovery contacts before an AI teammate gets access.

Setting Up Passwords and Logins for Your AI Teammate

Set up separate credentials for an AI teammate before it touches any account. Create them under business addresses the business controls; each credential requires a unique and sufficiently long password. Owners should activate two-step verification and begin with the narrowest authorization that accomplishes the job. Those four decisions largely determine how much harm a mistake, a stolen password, or a misconfigured integration can produce.

This guide describes the correct sequence and the verification that should accompany each stage. It also explains a method for testing the configuration before anyone relies on it.

Why does login configuration matter more than the AI itself?

A login is a grant of permission. Whatever an account is authorized to do, a teammate acting through that account is also authorized to do. An email credential can transmit messages to customers; a calendar credential can relocate appointments. A shared-drive credential can open files that contain customer addresses, contracts, and invoices. Most of the exposure in an AI teammate deployment originates in the accounts it can reach, not in the conversations where owners request assistance.

Many owners configure the teammate first and address security afterward; that sequence makes the work harder. A credential chosen deliberately on the first day is straightforward to get right. The same credential, altered after the teammate has operated for months, is considerably more difficult to change. Other staff members may depend on it, and changing it can disrupt their work. Establish the inventory of accounts first, configure the credentials second, and activate the teammate last.

Consider, for example, a two-person landscaping crew in Auburn that wants assistance with incoming quote requests. Its proprietor might reasonably assume the teammate requires the entire email account. In practice, it needs to read new messages, prepare replies, and consult the calendar. A narrower credential, or a connection that permits only those functions, keeps the remainder of the mailbox out of reach. Limiting scope also limits the consequences of an error.

What should you configure before the teammate touches any account?

Document every system, assign an owner and a least-privilege level to each, and confirm you hold its administrator credential before creating anything. Then follow these steps in order.

  1. Identify every system the business uses that the teammate might require. Typical entries include business email, a calendar, a website editor, a booking page, a shared drive, accounting software, and a telephone or messaging platform.
  2. For each system, document the responsible owner, the intended purpose, and the least privilege that accomplishes that purpose. Specificity matters. "Read the calendar and prepare draft replies" is an actionable plan. "Full access" is not a plan at all.
  3. Verify that you personally hold the administrator credential for each system. Where the platform permits it, designate a second owner or a recovery contact who can intervene if the primary owner becomes unavailable.
  4. Create the teammate's accounts or connections only after the first three steps are complete and documented.
  5. Activate two-step verification, then store the recovery codes in your password manager.
  6. Perform the verification test described later in this guide before granting any write permission.

After step 3, check the inventory: every line should name a responsible owner. You should also be able to describe the procedure you would follow to recover the account. If you cannot identify either one, halt the process and resolve that gap before continuing.

Most modest businesses complete this inventory in a single working session. A cleaning company in Fort Wayne with five systems can usually finish it in one sitting.

Owners across Northeast Indiana, from Auburn to Fort Wayne, can follow the same checklist. A sole proprietor may require considerably less. The investment is modest compared with the effort required to recover from a compromised account. It is also the one portion of the project that is difficult to reverse once the teammate begins operating.

Should the AI teammate share your personal login?

Do not provide an AI teammate with your personal password. The same principle applies to any credential you use for banking, personal correspondence, family accounts, or another business. Shared credentials obscure accountability; when a message is transmitted or a file is modified, you need to determine which identity performed the action. A dedicated account keeps the activity log legible. It additionally permits you to revoke the teammate's access without locking yourself out of your own records.

If a system does not support a second user, investigate whether it offers a delegate role. Alternatively, search for a service account or an approved integration with its own permission set. Many platforms offer one of these options, though availability depends on your plan. Select that route instead of disclosing your own credentials.

If the platform offers none of them, classify the account as elevated risk and keep the teammate out until a compensating control exists. Restrict the teammate's reach away from the account until a safer arrangement is in place.

How strong should passwords be for AI teammate accounts?

Assign long, random, and unique passwords to every account the teammate can reach. Generate them with a password manager, and never reuse one across separate systems. A password recycled from an older website is among the most prevalent routes to account takeover. Attackers systematically test credentials exposed in earlier breaches against numerous services.

Maintain control over the password manager itself. Store the vault in an account that only you can recover, and record the master password in a secure location at the business. Do not paste passwords into chat messages, support tickets, or shared spreadsheets, even briefly. A pasted credential persists in locations you do not govern and cannot reliably purge.

When a configuration prompts for a password, select the connection method the provider recommends. Some tools permit you to approve access through a sign-in window that you complete personally. Others issue scoped tokens after you confirm a list of permissions. Both approaches keep the password out of the conversation, and both allow you to withdraw access from a single location.

Is two-step verification worth the additional effort?

Yes; two-step verification ensures that a stolen password, by itself, does not open the account. An intruder must also possess the second factor, which is usually a time-limited code from an authenticator application or a physical security key. For any account the teammate can reach, this safeguard is the most valuable protection after unique passwords.

Prefer an authenticator application or a hardware security key over text messages whenever the platform offers a choice. Text-message codes depend on your phone number and your carrier, and they can be intercepted or redirected through social engineering. Store the recovery codes in your password manager; confirm that the recovery telephone number and recovery email address belong to the business. They should also belong to an owner who will remain with it.

Anticipate verification prompts that the teammate cannot satisfy. Certain steps require a person to approve a sign-in on a phone or to enter a code delivered by message. A properly designed configuration halts and notifies the owner when such a prompt appears; it must not attempt to circumvent the prompt.

If a tool repeatedly fails at the same step, treat that failure as evidence that the configuration requires revision. Do not treat it as an obstacle to overcome with a workaround.

Which accounts should the teammate reach first?

Begin with the accounts that present the lowest risk and yield the most valuable information, then add the remaining accounts one at a time. A sensible sequence proceeds as follows:

  • Read-only access to the calendar and to a shared document listing services, prices, and hours that you have already approved.
  • Draft-only access to the inbox, in which the teammate prepares replies and the owner transmits them.
  • Write access to a booking page or calendar, restricted to changes you agreed to in advance, such as confirming or rescheduling an existing visit.
  • Outbound messages to customers, granted only after several weeks of reviewed drafts demonstrate consistently accurate output.
  • Any function that moves money, deletes records, or changes customer data. These functions should remain with a person, or require a specific approval for each instance.

The permission levels described in our guide to read-only, draft-and-approve, and full access correspond precisely to this sequence. Assigning a level to each account individually, rather than applying one level to everything, keeps the configuration comprehensible to the people responsible for it.

Consider a hypothetical cleaning business in Auburn that wants its teammate to answer scheduling inquiries. During the first week, the teammate reads the calendar and prepares draft replies. During the third week, the owner permits it to confirm visits that already appear on the calendar. Refunds and price adjustments remain with the owner; each expansion of permission is a decision the owner makes deliberately and records with the date.

Beyond the order of access, three principles address most situations; first, separate reading from writing. Reading carries low risk and provides substantial value; writing is where errors become visible to customers. Second, require an approval step for any content a customer will see; third, designate the individual who grants approval. An approval that nobody clearly owns quickly degenerates into either a rubber stamp or a bottleneck.

Document these principles in the plan before the teammate begins operating. Include the approver's name, the channel through which approvals arrive, and the interval after which an unanswered request expires. If nobody approves within that interval, the request should lapse; it must not proceed by default.

Remain vigilant about gradual expansion of scope. A teammate configured to prepare drafts may acquire a new permission after a software update or when an additional integration is connected. Review the permission list after every change to a connection, and compare it against the documented plan. Every difference should reflect a decision you made intentionally, rather than an unexpected condition you discovered afterward.

What should you do when something appears wrong?

Respond quickly and follow a fixed order; first, pause the teammate or disconnect the affected account so that no further actions execute. Second, revoke the active session or connection, and change the password if there is any reasonable possibility that it was exposed. Third, examine the activity log for the relevant period. Search for transmitted messages, altered records, and sign-ins from unrecognized locations.

Fourth, determine whether a customer requires notification. If a message was sent in error, a brief and candid note from the owner is generally the appropriate response. Avoid characterizing the problem as something other than what it was. Fifth, prepare an incident record that states the date, the account, what occurred, what you changed, and what you intend to verify next. That record informs any future decision to restore or expand access.

Do not restore the teammate's access until the cause is understood. Premature restoration frequently reproduces the original failure, and a repeated failure is usually more difficult to explain to customers than the first one.

How do you test the configuration before trusting it?

Perform a brief test before connecting any system capable of sending, spending, or deleting. The test requires less than an hour and verifies three conditions.

  1. The teammate performs the function you intend. Send a test message from a personal address you control. Then confirm that the teammate reads it and prepares a reply in the expected location.
  2. The reply remains a draft. Confirm that nothing reached the customer's inbox, and that an approval step appears before any transmission occurs.
  3. The teammate cannot perform functions you have not authorized. Request an action beyond its permission level, such as deleting a calendar entry or messaging a number you never approved. The action should fail, or it should stop and request your approval.

Record the results in a simple log. Include the date, the test performed, the expected outcome, the actual outcome, and the person who verified it. Repeat the test after any change to the connection, the permission level, or the teammate's instructions. A test that cannot be repeated provides little more than a memory of confidence.

How frequently should you review your logins?

Conduct the review once each month. Confirm that every account nonetheless has a named owner, that every permission level remains appropriate, and that every recovery contact nonetheless functions. Remove accounts that nobody uses. If the teammate no longer requires an account, disconnect it rather than leaving it open on the assumption that it might prove useful later.

Repeat the review whenever a staff member joins or departs. A departing employee may have created a shared login, registered a recovery telephone number, or held an approval role. Remove those associations on the final working day, and verify that the teammate's approval requests nonetheless reach a person who remains with the company.

Every quarter, rotate the passwords on shared systems and confirm that the password manager's entries match the credentials the systems actually accept. Small businesses frequently discover stale entries during this check; remediating them promptly costs far less than discovering them during an incident.

Hey Button sets up an AI teammate around the access level you choose, beginning with the first conversation. If you want help matching each login to the work you need done, begin with the questionnaire on the start page. Read the access guide linked above before you connect anything, so that the level you choose is the level you intended.

Frequently Asked Questions

Often, yes, depending on the plan. Many business email platforms offer a delegate role, a shared mailbox, or a service account with its own sign-in. Check your provider's administrator help pages, test the option with one harmless message, and record the decision in your access inventory before granting anything further.
Treat that account as higher risk and keep the teammate out of it until you add a compensating control. Options include read-only access, a dedicated low-privilege account, or a rule that requires your approval before any change. Write the exception down and review it every month.
Keep one sheet with the account name, the owner, the purpose, the access level, the recovery contact, and the date it was last reviewed. Store it in a restricted folder or in your password manager's notes. Never keep it in a chat thread, where it can be copied without your knowledge.
Choose an owner or manager who will still be at the business, and use an email address and phone number that belong to the company. Avoid a personal number belonging to an employee who might leave. Add a second recovery method where possible, and store those codes safely.
Usually, yes, where the platform supports them. A passkey or hardware security key is harder to phish than a code typed into a page, because it checks the site it is talking to. Keep a recovery method on record, since losing the only device can lock the owner out as well.
Can an email platform give the teammate its own delegate access?
Often, yes, depending on the plan. Many business email platforms offer a delegate role, a shared mailbox, or a service account with its own sign-in. Check your provider's administrator help pages, test the option with one harmless message, and record the decision in your access inventory before granting anything further.
What if a system does not support two-step verification?
Treat that account as higher risk and keep the teammate out of it until you add a compensating control. Options include read-only access, a dedicated low-privilege account, or a rule that requires your approval before any change. Write the exception down and review it every month.
What should a login record sheet contain?
Keep one sheet with the account name, the owner, the purpose, the access level, the recovery contact, and the date it was last reviewed. Store it in a restricted folder or in your password manager's notes. Never keep it in a chat thread, where it can be copied without your knowledge.
Who should be the recovery contact for the teammate's accounts?
Choose an owner or manager who will still be at the business, and use an email address and phone number that belong to the company. Avoid a personal number belonging to an employee who might leave. Add a second recovery method where possible, and store those codes safely.
Are passkeys better than two-step codes for these accounts?
Usually, yes, where the platform supports them. A passkey or hardware security key is harder to phish than a code typed into a page, because it checks the site it is talking to. Keep a recovery method on record, since losing the only device can lock the owner out as well.

Hey Button

Want a teammate that handles this for you?

Answer a few questions about your business and Hey Button will show you what an AI teammate would take off your plate, with you approving anything that goes out.

Start the questionnaireSee what teammates do
Lucas M. Button

Written by Lucas M. Button

Founder, Hey Button

Lucas builds AI teammates for small businesses across Northeast Indiana and writes about what works, what doesn't, and what to hand off first. More about Lucas