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, 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.

A workspace 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 workspace when they belong to the same person or team.

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

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.

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.

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.

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.