Help

Moshaar help centre

Short guides to what you actually do in Moshaar: how to start, how to turn a message into a task, how to raise an invoice from a project, and who sees what. Each guide is its own page and reads in two minutes.

Getting started

Your first hour in Moshaar: the workspace, the team and the apps.

  • Create your workspace and sign in for the first time

    The workspace is your company inside Moshaar: every conversation, task, invoice and document lives in it, and only the people you invite can see it. Creating one takes a few minutes.

    Read the guide
  • Invite your team and assign roles

    The platform does nothing with one user. Invite your team first, then give each person a role — the role decides what they see and what they can change, not their job title.

    Read the guide
  • The mobile and desktop apps

    Moshaar runs in the browser, and has a mobile app for iPhone and Android and a desktop app for Windows. One account, one set of data — what you write on the phone is on the desktop immediately.

    Read the guide

Chat and tasks

From a message to a task with an owner and a date — the heart of the platform.

  • Chat: groups, messages and threads

    Chat is not an added feature here, it is where work starts. Everything created after it — a task, a document, an invoice — stays linked to the message it came from.

    Read the guide
  • Turn a message into a task

    What teams lose is rarely the written task — it is what everyone agreed to in chat and nobody wrote down. This is the step that closes that gap: the message itself becomes a task, with no re-typing.

    Read the guide
  • Following tasks: statuses, the board and reminders

    Once tasks exist, the question is where they stand today. The Tasks module shows work by status, owner and date, so you see what is late before a client asks about it.

    Read the guide
  • Calls and their minutes

    A call inside the platform keeps its context: the conversation that called it, and the project or client it concerns — so its decisions do not live only in the memory of whoever attended.

    Read the guide

Projects and clients

Organising longer work: the project, the client record and the calendar.

  • Create a project and link it to its client

    A project in Moshaar is the umbrella that holds the tasks, the conversation, the documents and the invoices of one piece of work. When the client asks where things stand, the answer is on one screen.

    Read the guide
  • The client record: from first contact to after delivery

    The client record holds everything about them in one place: contact details, their conversations, projects, quotes and invoices. A client’s history stops living in one employee’s head.

    Read the guide
  • The calendar, appointments and sessions

    The calendar brings team appointments, client sessions and deliveries into one picture, linked to the project or the client — not a calendar that lives apart from the work.

    Read the guide

Finance

From the quote to the payment, inside the platform itself.

  • From a quote to an invoice

    Finance is inside the platform, not a second program. A quote becomes an invoice with no re-entry, and the invoice stays linked to the project and client it came from.

    Read the guide
  • Recording payments and collection

    An issued invoice is not collected money. Recording each payment as it arrives is what keeps the receivable figure true, and turns collection into follow-up rather than guesswork.

    Read the guide
  • Reading the reports and deciding from them

    Reports here read the same data your team works in — not a file assembled by hand at month end. Which means they are exactly as true as your daily recording is disciplined.

    Read the guide

Documents and files

Writing together, notes, and where attachments belong.

  • Collaborative documents: writing with your team at the same time

    Documents here are edited live: several people write on the same page and each sees the others’ edits as they happen. No more files called "final version 3".

    Read the guide
  • Notes: what gets written fast and does not get lost

    Not everything you write is a formal document. Notes are for what is written in the moment — an idea, a number from a call, a reminder — and they stay attached to their context instead of ending on a desk sticky.

    Read the guide
  • Files, attachments and where they belong

    A file sent in a conversation and left there is lost a month later. The Files module gathers work attachments and ties them to a project or client, so whoever needs one finds it without asking who sent it.

    Read the guide

Administration

Who sees what, leave requests, and connecting your sales channels.

  • Roles and permissions: who sees what

    Permissions are built on roles, not on individuals. Define a role once and assign it to whoever needs it — so you are not re-configuring access for every new hire.

    Read the guide
  • Leave requests and approvals

    Leave asked for in a chat leaves no trace when someone asks three months later. A request inside the platform has a clear path: submitted, reviewed, approved or refused — and it stays on record.

    Read the guide
  • Connecting your sales channels

    Anyone selling on more than one storefront spends the day between scattered dashboards. The Channels module brings orders and buyer conversations into the same platform as your tasks and invoices.

    Read the guide