Claude can support a personal writing project, a research brief for your employer, and a proposal for a client. As those responsibilities accumulate, the challenge becomes keeping the work attached to the right account, organization, and source material.
There are several ways to manage multiple Claude accounts, and each handles a different kind of separation. Claude's own account menu can switch between eligible personal and organization accounts associated with the same email. Projects organize related work within an account. WebCatalog profiles help arrange distinct signed-in identities alongside the other web apps involved in a task.
A useful setup connects those layers to the way you work. Start with the owner of the task, organize its recurring context, and give yourself a reliable path through research, drafting, and review.
Map the account behind each task
Make a short inventory of the work you already do in Claude. For each recurring task, write down the login email, the intended personal or organization account, and where the finished result belongs.
For example, a product marketer might have a personal Claude account for learning and a company Team account for launch materials. A consultant could have a separate client-issued login for work carried out inside that client's organization.
These situations need different mechanisms:
| What needs to stay organized | Mechanism to use | What it identifies |
|---|---|---|
| Personal and organization accounts under the same email | Claude's account menu | The active account and its conversations and projects |
| Different login identities | A separate WebCatalog profile for each | The signed-in session and browsing data |
| A recurring subject or deliverable within an account | A Claude Project | Relevant reference material and project instructions |
| Claude alongside the other apps for a workflow | A space in WebCatalog | The collection of apps and profiles used together |
A new assignment under your existing work identity may only need another Project. A client-issued login calls for attention to the identity itself. Choosing at the right level keeps the setup useful as your responsibilities change.
Use Claude's account menu for accounts under the same email
Anthropic documents native account switching when an individual Claude account and a Team or Enterprise account share an email address. Select your initials in the lower-left corner, choose the desired account, and look for the check mark showing which account is active.
That is the first option to use when the accounts already appear together. You do not need to create another email identity simply to move between them.
Before beginning a work task, check the selected account as well as the email. The email alone may not distinguish your personal workspace from the organization workspace attached to it.
Anthropic's personal and organization account guidance explains that these accounts have separate conversations and projects. It also distinguishes keeping both accounts from migrating personal content into an organization. Regular account switching is the appropriate starting point when you intend to continue using both; migration is a separate decision about where your existing work should live.
Name your recurring tasks accordingly. “Company launch brief” and “Personal course notes” make the ownership clearer than two projects both named “Research.”
Give recurring work a Project within the correct account
Claude Projects provide a place for relevant documents, context, and instructions. Projects are available across Claude plans, including Free, which currently allows up to five projects.
Use a Project when the same background material belongs with a series of tasks. A launch project might need an approved product description, audience notes, and editorial requirements. A personal study project might need your syllabus and a set of reading notes.
Keep the contents intentional. Add the material you expect to reference repeatedly, then decide what each new request needs beyond that foundation. A folder full of unrelated documents can make a project harder for you to maintain even when the files are technically available.
Use project knowledge for the maintained documents and decisions you want available across the project's chats. Keep an approved product specification there instead of treating a correction buried in a long conversation as its only record. Anthropic's project management guide describes how to add that material.
Review memory separately. The same guide explains that projects can have memory and may also use account memory, depending on your settings and organizational controls. Its Use account memory option controls that interaction. A new Project therefore deserves a memory-settings check when you want its context kept apart. A separate WebCatalog profile changes the browser session; it does not reset Claude's memory settings for an account you sign into again.
Project instructions can capture the way you want recurring work handled. For a launch brief, an instruction might be: “Write for existing customers, preserve approved product terminology, and flag claims that need evidence.” Treat that as guidance for the work, then review whether the output follows it.
Choose a desktop arrangement that fits the surrounding work
Claude already has official desktop apps for macOS and Windows, plus a Linux beta. The available experience depends on your platform and Claude plan. If that app suits your routine, it is a useful direct route to the service.
WebCatalog is helpful when the daily task involves several identities or several web apps. Its value is the organization around Claude: a named account context, related tools nearby, and a consistent place to return to a particular kind of work.
For distinct login identities, WebCatalog profiles separate cookies, sessions, and browsing data. Give the profiles names you can interpret immediately, such as “Personal” and “Acme work.”
To create one, use Profiles → Add profile in WebCatalog Desktop, give it a name, then open Claude with that profile and sign in to the intended account. The profile guide also explains how a profile can be reused across related apps.
Use the sign-in method associated with the account, and check the resulting identity inside Claude. If the login provides access to both personal and organization accounts, select the intended account there too. A profile name does not replace Claude's account selection.
Assemble the tools around a research and review task
Consider a marketer preparing a customer launch brief. The source documents are in Google Drive, questions arrive through Gmail, and Claude helps turn approved information into a draft for review.
A work space can collect those apps and their appropriate profiles in one window. Spaces organize the tools; the profiles determine which browsing sessions remain separate.
For the two Google apps, the same work Google profile can support the shared identity. Use the Claude profile that contains the intended work login, then confirm the organization inside Claude. The collection can include different service identities while still representing one coherent task.
Placing Drive and Claude in the same space does not automatically connect their content. Supply the material Claude needs through the features available to your account, or manually provide a focused selection of notes.
The three-app example exceeds WebCatalog Basic's two-app allowance. Basic includes two desktop apps, two profiles, and one space; Pro and Business support larger arrangements with unlimited apps, profiles, and spaces. Begin with the tools your task needs and choose the appropriate scope.
Run the brief through three passes
Use a deliberate sequence for the launch brief: establish the evidence, shape the explanation, and review the result. This keeps the task moving toward a usable document instead of an expanding conversation with an unclear endpoint.
Pass 1: Build an evidence outline
Open the work account and the relevant launch Project. Gather the approved product notes, the intended audience, and any decisions already made about the announcement.
Ask for an outline tied to that material. For example:
Using the supplied launch notes, propose an outline for a customer announcement. For each section, identify the supporting note and the question it answers for the reader. List missing information separately. Keep unconfirmed capabilities out of the proposed claims.
Review the outline against the original documents. If two sources disagree, resolve the disagreement with the owner before using either claim. Keep the resolution in the project's maintained reference material or working brief so it remains visible during later revisions.
Pass 2: Draft for a specific reader
Once the outline is sound, request the first section or a short complete draft. State what the reader should understand and what action, if any, the announcement should invite.
Read the result for substance before polishing the sentences. Does it explain the customer benefit using supported facts? Does it introduce a promise that the product notes never made? Would a reader understand who the change applies to?
If the direction needs adjustment, describe the problem concretely. “Explain the setup requirement before the example” is easier to act on than “Make this better.” Keep revisions tied to the brief so stylistic changes do not gradually alter the meaning.
Pass 3: Prepare a reviewable handoff
Move the working draft into the destination your team expects. Include links to the supporting documents and a short list of questions the reviewer needs to answer.
Separate confirmed text from open decisions in your working notes. A reviewer should be able to see whether they are checking wording, validating a fact, or choosing between alternatives.
If the team will collaborate through a Claude Project, use its actual sharing controls. Project visibility and sharing are available on Team and Enterprise plans and are subject to administrator settings. Check the intended audience and permissions before sharing.
The handoff is complete when another person can understand the draft, its supporting evidence, and the decision you need from them. A conversation alone may not contain that structure in an easy-to-review form.
Keep the arrangement accurate as responsibilities change
Review your account map when you join a team, take on a client, or change roles. Confirm the login, active organization, relevant Project, and final document destination for each recurring workflow.
When something seems missing, check those layers in that order. The correct email can still lead to a different personal or organization account. The correct account can still have several similarly named Projects. A missing shared Project may require the owner or administrator to confirm your access.
WebCatalog profiles organize your access to the service. Claude determines the account's plan, features, usage allowances, and organizational permissions. Keep those distinctions clear when diagnosing an unexpected difference between contexts.
At the end of a work block, leave a useful next action in the working document: which claim needs a source, which section needs approval, or which question the next conversation should address.
Make the next review easier to pick up
Bring a current writing or research assignment into Claude in WebCatalog. Select its account, gather the relevant context, and arrange the tools needed to produce a reviewable result.
Keep the finished draft, evidence, and open decisions easy to find. When you return, that structure lets you continue from the actual state of the work, with the right identity and project already clear.
