You open a business document and Google asks you to request access. Before making another copy, check which account is open. Small identity mix-ups can leave work scattered across personal, business and old school accounts.
Give each identity a clear job, then connect your email, files and everyday tools around that structure. These maps use fictional addresses and a suggested setup you can adapt to your venture.
Map what you already have
List the services your business depends on. For each one, record the login, the workspace you expect to enter and the account that owns it. Add the billing destination separately. One address may do several jobs, but those jobs are still different.
You might sign in to a design service with founder@example.com while invoices go to billing@example.com. Changing where invoices arrive does not establish that ownership has moved. Check the service's own account and workspace settings before changing its login.
Separate everyday work from super-admin access. Google recommends a separate, non-admin account for daily activities when you are a super administrator. Keep powerful administration settings in their own identity, and give other accounts only the access they need. Check which identities need paid mailboxes before adding users. Google's administrator guidance.
One founder. Different jobs.
Email, documents and ordinary business services.
founder@example.comPowerful settings kept separate from everyday email and documents.
Administration onlyPersonal mail and activity, kept in its own browser profile.
Personal profileThe same person can do all three jobs. Use a non-admin identity for daily work and a separate one for super-admin duties.
Try this: fill in the account map for the three services you would most miss tomorrow. Record recovery-check dates, not passwords or recovery codes.
Make business email work
Choose the domain and business address you want to keep. Follow Google's current setup instructions to verify the domain and route incoming mail to Gmail. If the domain already receives email elsewhere, plan the switch before replacing its mail settings.
Send a message to an outside address, receive a reply and check the sender address. Include other services that send on your behalf, such as a booking or newsletter tool, in the authentication review.
SPF identifies permitted sending services. DKIM adds a signature that receiving systems can check. DMARC connects authentication to the address readers see and specifies how failures should be handled. Google recommends all three; review legitimate senders and reports before choosing a stricter DMARC policy. Use instructions for your actual services rather than copying someone else's DNS values. Google's email authentication guidance.
Try this: confirm a send-and-reply exchange from your business address, then record which services legitimately send email for the domain.
Use extra addresses without multiplying logins
If one person handles enquiries and billing, hello@example.com and billing@example.com can be aliases delivering to the same mailbox. An alias is an extra address, not another Google Account: it cannot independently sign in to Drive.
Add a separate user when you need a distinct identity, mailbox or access boundary. If another person needs to help with an inbox, consider delegation instead of sharing a password. Google's guide to aliases.
Two addresses. One inbox.
Receives both sets of mail.
Try this: mark each role address as an account, an alias or a question to resolve. Keep documented exceptions, such as a legacy service or eligible education subscription, visible in your account map.
Make the right sign-in the easy one
Create a clearly named business browser profile with a distinct colour and your work bookmarks. Keep personal browsing in its own profile. Chrome profiles separate browser information, but you can still select a different Google account inside Gmail or Drive. Check the email on the page as well as the profile label. Profiles are not a security barrier against someone using your unlocked computer. Google's profile guide.
Check three places.
- 1Browser profile
Am I in the business window?
Business ● - 2Google identity
Which account is open on this page?
founder@example.com - 3Service workspace
Did the right business and role open?
Example Studio Owner
Allowed→Enrolled→You approve→Sign-in tested
Use a trusted password or passkey manager consistently. Where the account and Workspace policy support it, passkeys can replace password typing with device approval. Permission to use passkeys, the preference to use them, an enrolled passkey and a successful sign-in are separate checks. Turning on a preference alone does not create a passkey.
One phone can hold separate credentials for different accounts. Keep recovery available and expect occasional verification or fallback prompts. Google's passkey guidance.
At another service, “Sign in with Google” is a way to authenticate. Confirm that it opens the intended workspace and role. If changing its login, verify the replacement route before disconnecting the old one. Inventory locally saved data before deleting duplicate browser profiles.
Try this: open your business profile, confirm the Google identity, then sign in to one important service and check the workspace and role you receive. On mobile, check the account within each app; account separation depends on the platform.
Give company files a clear home
A folder shared from My Drive is different from a shared drive. In My Drive, files have individual owners. Shared-drive files belong to the organization that owns the drive and remain when a member leaves. Google's comparison.
Use a simple structure: Operations, Projects, Brand and publishing, References, and Archive. Adapt the names to your work. Keep one authoritative working file, using links or shortcuts when it belongs in more than one place.
Before moving files, check ownership, collaborators and the access they will receive. Verify your edition's shared-drive availability, membership roles and sharing controls. Some editions have fewer controls. Give collaborators access to the work they need; keep finance and personal records behind an appropriate, verified access boundary.
Give each kind of file a home.
- Operations & templates
- Projects
- Brand & publishing
- References & archive
Individual working files. Sharing a folder does not turn it into a shared drive.
Finance, personal records and other sensitive work behind a verified access boundary.
Before moving a file: check its owner, the people who need it, and the access the destination grants.
Try this: choose a small, nonsensitive set of business files. Confirm its owner and intended readers before moving anything. Use the folder example as a starting point.
Make a small Start Here page
Create one page that opens the working day. Link business email, company files, current projects, useful templates and your account map. Add a short note naming the profile or account each service expects.
Link the subscription tracker and company brief where they already live. Start Here gives you a route to the authoritative records. A new collaborator should be able to find current work without guessing which copy is right.
A front door to the working day.
Try this: use the Start Here template, close your scattered work tabs, then reopen the essentials from that page. Fix links that lead to the wrong account or an outdated file.
Connect AI to a deliberate set of files
A connector lets an AI service retrieve supported files from Drive. Connecting it does not establish that every shared drive is included or every answer uses the latest file. The selected account, approved permissions and connector capabilities all matter.
Check whether your connector supports shared drives, which file types it can use, how it finds updates and whether it can make changes. Choose read-only or the smallest useful scope where available. Keep credentials and recovery material outside connected content.
Access comes before the answer.
Shared-drive support depends on the connector.
Supported files · permissions · search or indexing limits
Summarize, compare or find.
Right file? Recent enough? Within the intended scope?
Start with a small, nonsensitive folder or file set if the connector supports that scope. Test it before relying on it:
- Ask for a known file by name. Check that it returns the right document.
- Open its source link. Confirm the account and file are the ones you intended.
- Make a harmless edit to a test file. Check when the tool sees it; do not assume updates are immediate.
- Confirm who and what can access the content. If the connector cannot limit access to a folder, understand its broader scope before connecting.
- Ask for a summary or comparison. Check it against its sources, and approve proposed changes separately.
Try this: ask, “Find our sample project brief, link the original, and tell me its current objective.” A convincing answer is useful only if its source and freshness check out. Follow the current documentation for your chosen AI service; these maps do not assume a particular connector is already configured.
Your first setup check
Build the setup around your venture
At Mevanu, organizing accounts and files has been part of building the company alongside the product. Clear labels, one authoritative file location and individual account checks are practical lessons from that work. Each venture has its own evolving needs.
Start with the smallest structure you can understand and maintain. For company roles, written briefs and continuity, continue with our workspace setup guide. A consultant can help adapt your setup to your budget, time, complexity and ambitions, and turn it into a working roadmap. Work with Mevanu.