Workspace & Organizer

Projects and folders

Use a project for a sustained objective and folders to group related work. Access and creation controls depend on the user’s role; visibility is not permission to change everything.

Conversations

Begin with the task, constraints, and the result you need. Keep the discussion with the project it belongs to and check saved history when returning to the work.

Search and context

The Organizer includes search across projects, folders, conversations, and messages. Check which project and conversation are active before adding documents or changing contextual guidance.

Dashboard and workflow

The Dashboard includes project context, a workflow-board interface, Skills & Tools, and memory summaries. Use the information available in your deployment to understand the task’s boundaries.

Find the right place to work

Use Toggle Organizer if the panel is hidden. The search field covers projects, folders, conversations, and messages. Check the selected project and conversation before sending content. Use Create new conversation when your role permits it; project creation can require an administrator.

Ask Friday to guide you

In an authorized FridayLocalAI conversation, try:

Help me organize [goal] in FridayLocalAI. Suggest a simple project, folder, and conversation structure, then guide me through the controls available to my role. Do not claim anything was created until I verify it in Organizer.

Tell Friday what you can see and which step you have reached. If the instructions do not match your screen, say so; ask for the relevant Help topic or contact your operator. Friday cannot be assumed to see your screen or know your current settings.

Organize around outcomes

Use a project for a continuing area of work rather than creating a new structure for every prompt. A project might hold an article series, a research question, or an internal process improvement. Folders can separate useful areas within that project, and conversations can focus on individual questions or deliverables. Keep the structure simple enough that you can explain why each part exists. For example, a research project might have conversations for source questions, comparison notes, and an eventual summary. It does not need a folder for every short exchange. Start with the smallest arrangement that makes the work easy to find, then add organization when there is a clear need. A tidy structure is useful only if it supports the way you actually return to and review the work.

Confirm the selected context

Before sending a message, inspect the active conversation title and its associated context. This matters especially after searching, switching projects, or returning to the application. A response belongs to the conversation in which it was requested, and guidance saved in a particular scope may affect related work. Taking a moment to confirm the target prevents avoidable confusion later. Do the same before attaching a file or creating a Memory Note. If the selected item is not what you expected, navigate to the intended work first. Ask Friday to explain the visible structure if necessary, but do not assume it can see every item on your screen. Describe the names and labels relevant to your question without exposing unrelated private project information.

Use meaningful names and descriptions

A useful conversation title describes the task: “Draft the customer onboarding outline” is easier to recognize later than “New chat” or the name of a model. If renaming is available to your role, use it once the purpose becomes clear. Descriptions can explain the intended scope, such as the audience, source set, or decision the work supports. Keep names short enough to scan and descriptions focused enough to remain useful. Avoid embedding credentials or sensitive personal information in labels. A title is navigation metadata, not an access control or a complete instruction. If the assistant needs a detailed requirement, include that requirement in the appropriate conversation or prompt context rather than expecting a name alone to communicate the whole task.

Search for the work you remember

Organizer search includes projects, folders, conversations, and messages. Start with a distinctive term from the task, source, or expected result. Review the result in context before continuing work. Similar wording can occur in several conversations, so confirm the title and the relevant exchange rather than assuming the first result is the one you need. If the panel is hidden, use the workspace layout control to show Organizer. If a search does not find the expected item, check the wording and the intended workspace with the controls available to you. A search result is not permission to access another user’s material, and a missing result does not prove deletion. Preserve the distinction between navigation, visibility, and the underlying state of the work.

Keep conversations focused but connected

A conversation works best when its participants can understand the current objective and the context needed to continue. If the task changes substantially, consider starting a separate conversation in the appropriate place. If it remains the same task, give a concise update rather than repeating the entire history. State the decision made, the new information, and the next result you want. Ask Friday to summarize the current state when a discussion becomes long: established facts, open questions, decisions, and next steps. Review that summary before using it as a handoff. A generated recap can omit or misstate details, so it should not silently replace the original exchange. For enduring guidance, consider a Memory Note with an appropriate scope rather than relying on an unreviewed summary.

Work within the controls available to you

Creating a project and creating a conversation can have different role requirements. If a control is absent or unavailable, ask the operator about the intended workflow. Do not treat the limitation as something a prompt should bypass. A shared workspace needs consistent rules for who can organize, modify, or administer it. When you return to a task, verify that the expected conversation and recent messages are present. If state appears inconsistent, stop making organizational changes and record what you observed. Friday can help explain the interface or prepare a report, but the saved structure is the evidence of what exists. Good workspace habits combine clear naming, a manageable hierarchy, intentional context, and a reliable way to recognize the work you meant to open.