How to Use Grok Projects for Ongoing Work

To organize ongoing work in Grok, start on grok.com, choose the appropriate workspace, and attach the source files needed for the conversation. xAI names Projects in its consumer FAQ↗ (opens in a new tab), but does not establish a complete Project creation or saved-instructions procedure there. fenbs can keep the checked findings and next step so useful work remains available when you change devices or assistants.

The practical goal is a conversation grounded in the right material. First prove that Grok can read a small source accurately. Then decide what to retain for the next session, rather than assuming a named container makes every file and instruction available everywhere.

Where should you start your ongoing work?

1. Open grok.com in a standard Chrome or Chromium browser and sign in with the account you intend to use.
2. For a Business account, use the workspace selector at the bottom left before starting the conversation. Choose Personal Workspace or Team Workspace as appropriate.
3. Write a short opening message with the goal, the material you will supply, and the result you want.
4. Attach one small source file and check a specific answer against the original before adding more material.

The workspace selector and its two workspace types are documented in the Grok Business guide↗ (opens in a new tab). Team Workspace access requires an active Business license, and an Enterprise organization can disable Personal Workspace. These are web instructions; the guide does not supply a matching mobile workspace path.

Is a Project the same as a workspace?

Keep those terms separate. The consumer FAQ acknowledges Projects, while the Business guide documents Personal Workspace and Team Workspace. An API billing team is another object. The existence of one does not establish the creation steps, sharing rules, or retained context of another.

If your account shows a Project feature, inspect its own explanations before depending on it. This guide cannot supply a verified New Project command, instruction field, or permanent file library from the cited documentation. Do not substitute a workspace switch for a Project creation step and assume you have completed the same setup.

For the separate question of what carries into a fresh conversation, use the Grok memory guide. A correctly organized conversation and reliable cross-session recall are different things to check.

How do you attach the source you want analyzed?

xAI documents direct chat uploads on web, iOS, and Android. In the file-upload instructions↗ (opens in a new tab), the control is the + beside the message input; the web app also supports dragging files into the conversation. That is a documented chat attachment flow, not proof of a permanent Project attachment.

1. Choose a file you are allowed to share, preferably a short document with a fact you can easily check.
2. Click or tap + beside the message input, then select the file from your device. On the web, you can also drag and drop it.
3. Ask for one specific result, such as the delivery date in a named section and the surrounding sentence.
4. Compare the answer with the original document. Correct the instruction or supply a narrower excerpt if the answer is incomplete.

For example, use a sample event brief and ask for its venue, setup time, and unanswered questions. Give the file a meaningful name before uploading. A filename such as event-brief-approved is easier to distinguish from an old draft when you later review what informed the answer.

What instructions make the analysis easier to check?

Supply the goal and boundaries explicitly in the conversation. This is a suggested message structure, not a claim that Grok has a particular saved-instructions field. Include what counts as evidence and what the assistant should do when the document does not answer a question.

• Goal: prepare a short event setup checklist from the attached brief.
• Source: use the attached approved brief for dates, names, and requirements.
• Boundary: identify missing information instead of filling it in.
• Output: list each action, its source section, and anything a person still needs to confirm.

Ask one question whose answer you already know before requesting a broad summary. Then check one detail from a later part of the file. That gives you a more useful signal than a polished paragraph that could have been written without reading the attachment. Keep confirmed findings with the work using the fenbs work record.

Why might files or Projects appear to be missing?

The FAQ recommends grok.com in a standard Chrome or Chromium browser and specifically mentions missing features, including Projects, on other hosts. It also warns that upload support can vary by platform or subscription, that long files may be summarized in sections, and that embedded images in non-PDF documents may not be interpreted. Check the current FAQ↗ (opens in a new tab) before treating an upload as complete understanding.

Start diagnosis with the exact host, account, workspace, filename, and question. If an answer misses a chart inside a document, provide the relevant material in a clearer supported form and test again. Avoid adding more files until you know whether the problem is access, the source format, or an overly broad request.

If the job needs live access to another service rather than an attachment, the separate Grok MCP setup guide covers that connection. Uploading a document and authorizing an outside tool have different checks.

What should you keep before leaving the conversation?

Keep the source version, the findings you checked, the choices a person made, and the first unfinished action. Distinguish “Grok suggested this” from “we approved this.” A useful record might say that the venue and setup time were checked, while the equipment list still needs the organizer’s confirmation.

Grok’s overview↗ (opens in a new tab) says conversations and settings sync across web and phone when you use the same account. That is different from proving every new conversation can use every old attachment. If you later compare assistants, the Grok versus ChatGPT guide handles that separate choice.

How to keep checked work with fenbs

Save the useful result once so you can carry on from exactly where you left off, on any device and in any other AI. You only need the small set of facts and next steps that makes the next session easier.

1. Create a free account.
2. Add the work you want to finish and write what you are trying to do in one sentence.
3. Save the source name, the answers you checked, and anything still waiting for a person.
4. Connect Grok to fenbs. Ask it to read the saved work before continuing and save what changed before stopping.

fenbs does not import Grok chats or turn a chat attachment into a permanent document library. It is unnecessary if you only need a one-time answer from a disposable file. Browse the AI at work hub for more ways to carry useful results into the next session.