How can we help?

NetoProjects is a control center for everything connected to a project. It keeps tasks, notes, documents, decisions, dates, sources, and people together, so the important context is not scattered across chats and browser tabs.

It is not meant to force every project into one rigid workflow. Use only the sections that help you see what is happening and what needs attention.

Open Projects and select New project. Give the project a clear name, add a short description, and choose a color or icon that makes it easy to recognize.

When the project opens, Plans is the starting section. You can move between the other sections from the project menu and fill them in whenever they become useful.

Use Plans for work and dates, Documents for material you will refer to again, Notes for thoughts and working context, Sources for systems and links, Decisions for choices that need a record, Contacts for the people involved, and Mind Map when the relationship between ideas matters more than a list.

Overview and Calendar summarize information that already exists in the project. Trash is where you recover deleted items.

An organization is the home that groups projects and people. A project is the actual working area with its own plans, knowledge, decisions, members, and permissions.

Use separate projects when the people, goal, or information should be managed independently. Keep them in the same organization when they belong to the same person or team.

A project card shows its name, key, identity color or icon, your role, and who shared it when relevant. Select the card to open the full project.

Under the name you see the tasks: how many are open and overdue, how many are done out of the total, and what is in work or in test. Below that come the next task, the next event and the next reminder, each on its own line.

If you own the project or are its admin, these numbers cover the whole project. If you are a member or a viewer, they cover only the tasks assigned to you.

The Active and Archived views keep current work separate from projects you are no longer using every day.

Archive a project when you want it out of the active list but may need it again. Archiving is reversible and does not erase the project or its contents.

Deleting a whole project is different: only its owner can do it, and the project moves to System Trash for a 14-day recovery period.

A task is something that needs action. Its status moves from In Plan to To Do, In Work, In Test, and Completed. Use Won't Do when the team deliberately decides not to continue.

Bug, Feature, and Change Request describe what kind of task it is. Type and status are separate: a Feature can still be In Plan, In Work, or Completed.

Use an event for something that happens at a particular time, such as a meeting, release, or deadline. Use a reminder when the important part is being prompted to remember something.

Add dates and times carefully: dated items also appear in Calendar, giving the project one shared timeline.

Calendar brings dated tasks, events, and reminders together in a monthly view. Select a day to create a new item without leaving the calendar.

Changing an item in Calendar changes the same item in Plans. It is another view of the same project information, not a separate copy.

Use Documents for information the project will return to: specifications, guides, research, external references, and longer working material. A document can include a title, description, link, and images.

Owners and Admins can connect a GitHub repository and link a document to a file. Sync then refreshes the document from that file instead of leaving an old copy behind.

Use Notes for ideas, observations, meeting context, and anything worth remembering that is not an action or formal decision. Notes can include formatted text and images.

A new note is private by default. Its author can keep it private, share it with selected teammates, or make it visible across the project. Only the author can edit or delete it.

Use Sources for repositories, deployments, servers, dashboards, data feeds, or any other place the project depends on. Store a recognizable name, address or URL, a free-text type, and the context somebody will need later.

Pin the sources the team uses most often. A Source is a reference record; it does not automatically monitor whether a service is online.

A Decision stores what was chosen, why it was chosen, and which alternatives were considered. Link it to relevant tasks, notes, documents, events, or sources so the surrounding context stays connected.

Decisions are a history, so an old one is not rewritten. When the direction changes, create a new decision and mark which earlier decision it supersedes.

Overview summarizes open tasks by status and shows upcoming events and reminders. It is useful when you need the state of a project without opening every section.

Overview does not hold separate data. Update the original task, event, or reminder and the summary follows it.

Use the search control in a project, or press Ctrl+K, to look across its available sections. Search results take you back to the original item instead of creating a duplicate.

Search follows access rules. Content from a section or private item you cannot view will not be exposed in the results.

Use Secrets for API keys, passwords, connection strings, SSH keys, and other values that should not appear as plain text in a note or document. Values are encrypted on the server before they are stored.

A secret can live in the project vault or be linked to a task, note, document, or source. The linked item keeps a reference, not a copy of the sensitive value.

Private means only the creator can access it. Admins limits it to the Owner and Admins. Project makes it available to members who already have access to the project.

Choose the narrowest visibility that still lets the right people do their work. A project role never grants access beyond the visibility set on the secret itself.

Opening or copying a secret is recorded in the access log. Owners and Admins can review that history and investigate access from a new location.

If a warning was caused by your own activity, acknowledge it. If it was not, change the secret value and review who can access the project.

Contacts belongs to your account rather than to a project, so the same book opens from whichever project you are standing in. A contact does not have to belong to anything at all — the client you spoke to once is as much at home here as the contractor working on three projects.

The dropdown above the list decides what part of the book you are looking at: everything, only the contacts attached to the project you are in, the archive, or the trash. The search box matches every word you type against every field, in any order, so "acme invoices" finds the person at Acme you tagged that way.

Every contact is a person. Which team they belong to is a plain text field on the card, next to Company — put a company name, a department, a squad, whatever fits.

It is free text, so nothing has to be set up first and two people can be on "Backend" without either of them pointing at a shared record. The team shows on the card next to the role and company, and the search box reaches it like every other field.

Every contact starts private. You can open it to people you name, to organizations you belong to, or to every organization you are in. Sharing a contact has nothing to do with sharing a project: attaching a contact to a shared project does not put it in front of that project's members.

Whoever you share it with reads it and nothing more. If they need it changed, they press "Make it mine" and get their own copy to edit — so there is never a question of whose version is the right one.

Import accepts a CSV or a vCard file, which is what Google Contacts, an iPhone and Outlook all export, and export hands the book back in either format. Imported contacts arrive private.

Archive a contact you no longer deal with and it leaves every view except Archive, still in the book and still findable by search. Deleting is separate: the contact waits 14 days in the Contacts trash, where it can be restored or removed for good.

Open the Finances tab. There is nothing to set up: add entries right away, each in its own currency. Euros stay euros and shekels stay shekels, nothing is converted and no exchange rate is used, and totals are always shown per currency, for example “300 € · 150 ₪”. Who else sees an entry is set in that entry's own form: “Who sees” and, when it is open to someone, what they also see.

Only the owner and the admins add or change anything in Finances. Start with a list of categories that fits the project, for example materials and delivery for a renovation, or tickets and hotels for a trip.

The tab lists the entries, newest first. A row shows the title, the amount in its own currency, the date, the category, who it was paid to (or received from) and, when there is something to say, one short status: a planned payment reads “Pay supplier by 19 Oct” (an expected income reads “Awaiting payment by 19 Oct”, red once the date has passed), a paid entry reads “Paid to supplier 17 Oct” (an income reads “Paid to me in full 17 Oct”) with “To be returned 400 ₪” beside it while something is still owed, and once everything is paid and returned it reads “Closed 18 Oct”. The owner and the admins also get a trash button on each entry. Click a row to open everything about that entry: who paid, how it was divided, who owes whom, its files, and when it was added and last changed. The owner and the admins add one with the Expense or Income button above the list, or change it with Edit inside an opened entry. On the line under it you can show only expenses, incomes, planned ones or entries with money still to be returned, sort by date, due date, amount or name, and switch between cards and rows. Once the project has categories, one more filter next to them shows a single category or the entries without one. While a debt is open, the badge ends with who is owed, for example “To be returned 400 ₪ → Alex”, or with their number when several people are owed.

An expense and an income each have their own button and their own form. Give the entry a title, an amount, a date and a category, and pick the currency from the list; you can search it by name. Paid to is who got the money, for example the hotel or the contractor (for an income it is Money from, for example the client). You can leave it empty. Under Who paid you see who paid and how much (for an income it is Who received). You start as the only payer with the whole amount. If two people paid, press Another payer and give each their part of the amount: the line under the list says Allocated 1 200 of 1 200 when it adds up, and says what is left when it does not. Save waits until it adds up. What you save here is always paid; a payment that has not happened yet is planned instead.

Plan a payment is for money you still have to pay, and Expected income is for money you are still waiting for; each has its own button and form. Say what it is for, the amount, who will pay (for an income, who will receive) and, if you want, to whom (from whom). The Pay by date (Expected by for an income) is required: the Center reminds on that day. In the opened entry a planned payment reads Not paid, pay by 1 Nov, with a Paid button (Money received for an income). Press it and the entry becomes an ordinary paid one, dated today, showing Paid 17 Oct with an Undo link. From then on you can edit it like any entry.

If a payer or the other side is not a project member, type the name or the company name in the search box of the list and press Enter, or click Add “name” at the top. If a member or a contact has exactly that name, that one is picked instead. Under the chosen name you can add an e-mail, so that reminders reach them, and tick Save to Contacts to keep them in your own Contacts, private to you. Without the tick, the name and the e-mail stay on this entry only. Both apply when you save the entry.

Every entry stays in the currency you chose. Nothing is converted, so entries in different currencies are never added together.

A payment can be paid in parts. In the Plan a payment or Expected income form tick “Pay in instalments”: the single date gives way to a list where each instalment has its own date and amount. An instalment you have already paid is ticked “Already paid”, with the day it was paid (a day in the past is fine) and the amount. In the opened entry the Instalments block shows Paid 278 009 ₪ of 817 000 ₪ and what is Left, and each instalment has a Paid button (a small window for the day, the amount and a receipt), Edit and Undo. The entry becomes paid by itself when what was paid adds up to the total. The instalments may add up to less than the total, never to more.

When one expense is for several people, press Split with others in the form. Under Divide between add everyone who shares the cost, the people who paid included, and type each one's part: a hotel of 1 200 for three is 400 each. The Equally button divides the total between the people in the list. The parts must add up to the total.

You do not write down who owes whom, the Center works it out. For each person it takes what they paid minus their part. Anna paid 800, Ben paid 400, and the three of them (Anna, Ben and Cara) share the cost, 400 each: Cara owes Anna 400. Without a Divide between list nothing is divided, so there are no debts.

In an opened entry the first lines say what it was: the amount, the type and the date, then who paid, for example Paid by Anna → Hotel, or Paid: Anna 800 ₪, Ben 400 ₪ → Hotel, then how it was divided and the category. Under Who owes whom each debt is a row such as Cara → Anna 400 ₪ with the buttons Mark returned, Remind by e-mail and Show in the Center. A returned row stays, crossed out with its date and an Undo return button, and a green check appears by the heading when everything is returned. The proof files stay attached after Undo return.

If you change the entry later, a debt between the same two people keeps its row, its returned mark, its proof and its reminders. A debt that was already returned cannot change or disappear: mark it as not returned first, then save.

Only the owner and the admins mark a debt as returned. You can attach a screenshot of the transfer or a receipt as proof, and the people on the row can open it. A member sees only the rows they are on.

In the opened entry, the button Remind by e-mail on a debt's row sends an e-mail to the person who owes. It works for project members, for contacts that have an e-mail address, and for anyone you added by name with an e-mail. If someone has only a name, the button reads Add e-mail instead: tick Save to Contacts to keep them in your Contacts, or leave it off to keep the address on this entry only. Or press Show in the Center, and the person sees a window with the debt when they next enter the app, at most once every three days. Under the name you see when an e-mail was sent and when the reminder was shown in the Center; the result of a button appears right under the same row. A name with an e-mail also has Change e-mail and Remove e-mail under it; to give the address back, press Add e-mail again.

The window stops when the debt is returned or when you press Cancel reminder. While it is on, the Finances item in the project menu shows a dot for that person.

Payments that are due for you are shown on the entry itself. The owner and the admins see a badge on an entry with a planned payment or a debt not yet returned, starting three days before the date: “Due in 3 days”, “Due tomorrow”, “Due now” on the day, and a red “Overdue by 2 days” once it has passed. The closer the day, the louder the badge. The Finances item in the project menu shows a dot while something is due today or has passed.

Each instalment has its own e-mail reminders: 7, 5, 3 and 1 day before its date, on the day, and every 3 days after the date while it is not paid. Tick the days you want in the form. The e-mail goes to who will pay (who will receive, for an income) and, for an expected income, to who the money is expected from. It is sent once a day.

Members and viewers can only read. The owner and admins see everything. Who else sees an entry is chosen in that entry's own form, on the “Who sees” line: Only me, Everyone in the project, or Selected people. When it is open to someone, the “They also see” line adds who paid and how much, who owes whom, and the files; the title, amount, date and category are always shown. Anyone named on an entry always sees it and their own debt row. The list card shows a lock, an eye or people for the choice; for the people an entry is opened to by name, the badge reads “Shared with me”.

A deleted entry waits 30 days in Trash. Receipts and screenshots use the same file space as document files.

Create nodes for ideas, systems, questions, or stages, then connect related nodes. Drag nodes to organize the canvas and use zoom controls when the map grows.

Double-click a node when you need to edit it. Keep node labels short and put the detailed explanation in a Note or Document when it becomes too large for the map.

A Mind Map can be shared with selected project members. Sharing the project does not mean every private map must automatically be visible to everyone.

Use map sharing when somebody needs the visual context, and remove access when that work is finished.

Most sections have AI buttons next to the fields. They suggest a title, write or tidy up a description, and turn a piece of text or an attached document into a list of tasks.

Documents get a few more: a short summary, a rewrite in a different shape, or several versions to pick from. In Decisions, AI suggests alternatives worth weighing. Secrets and Contacts have no AI buttons.

The assistant button sits in the project header. Ask what's overdue, what changed this week or what a document says, and it answers from that project's records. It only reads and never changes anything.

It is there for the Owner, Admins and Members. It never sees Secrets, the trash, other people's private items or other projects.

AI actions are counted per day and per month. Each AI button press or assistant question uses one action, and the next one is refused as soon as either count runs out.

How many you get depends on your plan, and project supporters get more. The line under the AI buttons shows what's left for today and for this month.

A donation usually adds 15 AI actions a day for 30 days per $5, and the days from several donations add up. These numbers can change, but anything already granted stays valid until the end of its paid period.

Availability also depends on the platform's overall AI token budget. If it runs out, AI can be unavailable for a while even when you still have actions left.

The Owner controls the project and its lifecycle. Admins manage access and protected project settings. Members contribute to day-to-day work. Viewers can read what is shared with them but cannot change it.

Give each person the lowest role that matches what they need to do. Roles are enforced by the server, so hiding a button is not the only protection.

Documents can only be created, changed, archived, deleted, or synced by the Owner and Admins. A Member can work in other shared sections, but deleting project content requires the separate Can delete permission.

People still control their own notes, decisions, comments, and Mind Maps. Private or specifically shared content stays limited even when somebody has access to the wider project.

An Owner or Admin can choose which project sections are visible to each role. This keeps a simple project simple and hides areas a particular group does not need.

Plans and Trash remain available because Plans is the project starting point and Trash is the way back to deleted work.

Archive an item when it is finished or no longer current but still useful as history. Archived items are hidden from the main list and can be shown and restored later.

Archive is usually the safest choice when you are unsure whether something will be needed again.

Deleted project items move to the project's Trash instead of disappearing immediately. Open Trash, find the item, and restore it to return it to its original section.

Permanent deletion cannot be undone. Read the confirmation carefully before removing anything from Trash for good.

Project owners can download a backup from Admin → Backup. The file keeps the project structure and can be used to restore a project later.

A backup is useful before a large cleanup or transfer. Store it somewhere protected, especially when the project contains sensitive information.

Account -> Backup & Restore downloads your own items from every project you are in as one file. It covers your items, not the whole project, so other people's private items are never in it.

Restore puts the items back into their original projects, into a project you pick, or into a new one. If a project no longer exists, it can be created again.

Account -> Preferences switches between two designs. Classic is the original look; Modern is lighter, with soft shadows, a stripe of the project color on cards and the project header, and a floating sidebar.

The choice is yours only: teammates keep whatever design they picked.

Every list can be shown as cards or rows with the switch above it. Your choice is remembered.

In Account -> Preferences -> Sidebar order, pick a project and drag its tabs into the order you like. Only your own sidebar changes, and Trash always stays last.

Use a magic link sent to your email, or continue with Google. A magic link is single-use, so request a new one if the old link has expired.

On a public or shared computer, select the matching option on the sign-in page so NetoProjects does not remember your email or name on that device.

If email two-factor authentication is available, turn it on under Account → Security. After Google confirms your identity, NetoProjects will send a short code to your email before opening the account.

Magic-link sign-in already proves access to your email, so it does not ask for the same second email step again.

Use Contact Us for account trouble, access problems, unexpected behavior, or product feedback. Include the email used to sign in, the project name when relevant, and a short description of what happened.

Never send passwords, API keys, recovery codes, or other secret values in a support message.