Chrome Profiles and Extension Settings for Shared Machines

One profile per person, one clear setup note, and a clean handover routine

Voiskey Voiskey Team
Gmail DictationChrome ExtensionChrome Profiles Extension

Why Profiles Are the Unit of Setup

Chrome Profiles and Extension settings are the two things that make a shared computer usable without constant reconfiguration. A profile holds a set of settings, and the extension settings live inside the profile that installed them. Once you accept that pairing, the rest of the setup follows: one profile per person, each with its own pinned controls and its own microphone decision. Shared computers fail when people share a single profile and expect separate behavior from it. The browser cannot guess who is sitting at the desk, so the person must choose a profile before typing. That choice is the whole foundation.

Decide how many profiles the computer needs before you set anything up. One per person is the default. Add one shared work profile only if a team genuinely uses the same accounts, and label it clearly so nobody confuses it with a personal profile. More profiles than people is usually a sign of drift, not organization. Write the list on a card and tape it near the screen if the computer is in a common area. Naming and labeling are unglamorous, and they are the difference between a setup that works for months and one that collapses the first time someone is in a hurry.

Give each profile a clear name and a distinct avatar. The name should be a person or a role, not a color, and the avatar should be recognizable at a glance. When two windows are open side by side, the avatar is how you know which one you are typing in. This matters more than it sounds, because a message written in the wrong profile is the most common shared-computer mistake. Check the avatar before you press the shortcut, every time, until the check is automatic. A color is a poor label because two profiles can share one, and then neither is identifiable.

Decide where the dictation setup lives. Voiskey runs at the system level, so it is available regardless of which profile is open, but the browser helper and its pinned control belong to a profile. That split is useful once you understand it: the profile controls the visible entry point, and the system-level app handles the text. Write the split into your setup note so the next person does not try to fix a profile problem by reinstalling the app, or the reverse. If a user cannot explain the split, they will fix the wrong layer, and the problem will return.

Configuring a Work Profile from Scratch

Start by signing in to the profile and naming it. Then set the basics that people change accidentally: the home page, the search engine preference, and the save location. None of these are exciting, and all of them cause confusion when they differ from what the user expects. Next, install the browser helper and pin it in the agreed position. Then make the microphone decision and test it with one sentence. This order matters because each step depends on the previous one. A profile configured out of order usually ends with a working helper in a profile that cannot listen.

Rehearse the handover as part of configuration. Close the browser, reopen it, and check that the profile starts with the pinned control still visible. Open a draft and dictate one sentence. If the pin or the permission disappears on restart, the profile is not finished. Fix that before handing the computer to anyone. A setup that only survives one session is worse than no setup, because it teaches people to distrust the tool. The restart test is the cheapest way to prove the configuration is durable. A restart test takes a minute and tells you more than a week of assumptions.

Record the configuration in a short note: profile name, helper version, pin position, microphone decision, and the date. Keep the note where the computer is used, not in a folder nobody opens. When something changes, update the note the same day. This is the kind of documentation people skip and then wish they had. A five-line note answers most of the questions that come up weeks later, and it gives a new user a starting point instead of a mystery. Write the note in the same format for every computer, so the comparison stays cheap and the note stays readable.

Set expectations for the shared profile, if you have one. Agree that the shared profile is for shared work only and that personal accounts stay out of it. Agree on the pin position and the microphone decision so they do not change from user to user. Agree on a weekly check that the setup still matches the note. Written agreements sound heavy for a browser, and they prevent the slow drift that makes shared computers unpleasant. Three sentences in the note are enough. A weekly check is short, and it catches the drift before a new user meets it as a surprise.

What Belongs in Each Profile

Every profile should contain only what its owner needs for the work it supports. A personal profile does not need the project extensions. A project profile does not need a dozen utilities. Pruning is part of setup, not a separate chore. Before you add anything, ask which task the addition serves and what it replaces. If it replaces nothing and serves no weekly task, leave it out. This rule keeps each profile small enough to reason about, and small profiles are easier to hand over, back up, and rebuild after a problem. The question is not what might be useful, but what the profile's work actually requires.

Bookmarks, saved passwords, and history follow the profile, so treat them as part of the setup rather than as background noise. A profile with the wrong bookmarks feels broken even when the extension works. Check the bookmark bar and remove clutter that will confuse the next user. For shared profiles, agree on a small set of shared bookmarks and keep personal ones out. This is organizational housekeeping, and it pays off every time someone new sits down. A bookmark bar with four short entries is easier to hand over than one with forty, and much easier to explain in a handover.

The extension list deserves a monthly review. Open the extensions page and look at what is enabled. Remove anything unused, and check that the dictation helper is present exactly once. Duplicate installations are a common cause of odd behavior, and they are easy to create when two people configure the same profile on different days. Note the version and the last update in your setup note. A profile that is reviewed monthly stays predictable, and predictability is the whole point of separating profiles in the first place. Note the date of the review as well, so a later change has a known starting point.

Keep the microphone decision visible in each profile. If the profile is for writing mail, the microphone should be allowed and tested. If the profile is a read-only reference space, it does not need the microphone at all. Making this explicit prevents accidental grants and reduces the number of prompts people see. Write the decision next to the profile name in your note. When a prompt appears in a profile that should not need it, you have found a configuration error rather than a mystery. A profile that never needs the microphone should never be asked for it, and should never ask.

Handing Over a Shared Computer Cleanly

A handover has three parts: the profile, the setup note, and a two-minute demonstration. Sign out of the profile you used, have the next person sign in to theirs, and confirm the pinned control and microphone decision are as expected. Then watch them dictate one sentence. Do not narrate every step; let them try and note where they hesitate. A handover that ends with the next person writing a sentence on their own is complete. A handover that ends with you explaining for ten minutes is not. If the sentence lands and the pin is visible, the handover is done.

Keep the demonstration script short and stable. Open a draft, press the shortcut, say one sentence, read it, and close the draft. That is the whole script. Repeat it in the same order every time so the next person learns the rhythm rather than a set of tips. If they ask about a feature outside the script, answer briefly and return to the script. The goal is competence in the core motion, not a tour of everything. Competence in one motion is what makes the rest learnable later. A short script also makes it easy to spot when a profile is not configured.

Handle the awkward case where two people need the computer at the same time. Use separate windows in separate profiles and label them, or agree on a schedule if the computer is slow. Do not share a profile to save a step; the shared profile is where confusion starts. If a deadline forces a shared session, one person drives and the other dictates, and both check the avatar before sending anything. Improvised sharing is fine for a short task as long as the ownership of the profile stays clear. Ownership is the detail that keeps a shared computer from becoming nobody's responsibility.

After the handover, leave the note updated and the desk tidy. Remove drafts that belong to nobody, empty the scratch fields, and confirm the profile list on the card is still accurate. These small acts make the next handover easier and signal that the setup is maintained rather than improvised. A shared computer is a small piece of infrastructure, and infrastructure is judged by how it behaves when the usual person is away. Clean handovers are the test. Leave the card and the note in the same place every time, so nobody has to hunt for them during a busy handover.

Keeping Settings Aligned Across Profiles

Alignment does not mean identical. Each profile should have the same structural choices, such as the pin position and the shortcut habit, while keeping its own content. Write a short standard that lists the structural choices and apply it to every profile you configure. When a new profile is added, run through the standard before anyone uses it. This keeps the experience consistent across people without forcing them to share the same bookmarks or accounts. Consistency in structure and separation in content is the combination that works. Write the standard on the same card as the profile list, and keep both current.

Review alignment monthly with a simple checklist: is the helper pinned in the agreed position, is the microphone decision correct, is the note current, does the restart test pass? Four questions, five minutes, one profile at a time. If a profile fails, fix it and note the date. Do not fix multiple profiles in one sitting if you can avoid it, because the restart tests start to blur together. One profile at a time keeps the evidence clean and makes the review short enough to repeat. A profile that fails the checklist gets fixed before anyone uses it again that day.

When you add a new computer to the rotation, Download Voiskey for macOS and Windows and set up each profile as a fresh decision. Do not copy a whole profile folder unless you understand what it contains; a copied profile often carries stale settings that look correct and behave strangely. Rebuild from the standard instead. Rebuilding takes longer once and saves time repeatedly, because every setting is deliberate. Keep the setup note with the computer so the next person can see what was chosen and why. A fresh setup also gives you a clean reference configuration for the next rebuild.

Finally, accept that drift is normal and plan for it. People add extensions, change pins, and make microphone decisions without telling anyone. A monthly review catches most of it, and a shared note catches the rest. The goal is not a frozen configuration; it is a configuration that anyone can explain in a sentence. If a new user can describe the profile, the pin, and the microphone decision in one breath, the setup is aligned. If they cannot, the note and the review have work to do. If the note is missing, write it before the next review rather than after the next failure.

FAQ s

Voiskey runs at the system level and works regardless of which browser profile is open. The browser helper and its pinned control belong to a profile. Keep one profile per person, record the pin position and the microphone decision in a short note, and test each profile after a restart.

Only what the profile needs for its work. Keep one helper installed rather than two, pin it in the agreed position, and make the microphone decision explicit. Remove unused extensions monthly, and note the version so a later change can be compared with a known state.

Sign out, have the next person sign in to their own profile, and confirm the pinned control and microphone decision. Then watch them dictate one sentence without narrating every step. Update the setup note and remove drafts that belong to nobody before you leave.

Because people add extensions, move pins, and make microphone decisions without telling anyone. A monthly checklist of four questions catches most of it: pin position, microphone decision, note accuracy, and restart behavior. Fix one profile at a time so the evidence stays clear.

Say less. Get more
Say less. Get more
Say less. Get more
Say less. Get more
VoiskeyVoiskey

Your voice, amplified.

Download Voiskey for Mac and Windows and give each profile a tested setup.

Use it across macOS, Windows, iOS, and Android

Use it across