Orangescrum
Documentation index for AI agents (llms.txt). A markdown version of this page is available at /project-collaboration-software.md or by requesting this URL with the header Accept: text/markdown.
Project collaboration

Collaboration That Stays Attached to the Work

Not another chat tool. The comments, files, and decisions live on the task they are about, so context survives handovers, holidays, and people leaving.

Free forever plan · No credit card required · Set up in minutes

What is project collaboration software?

Project collaboration software is where a team works together on the actual work, rather than talking about it somewhere else. The distinction matters: chat is good for quick questions and bad at keeping decisions findable. Orangescrum keeps discussion, files, and approvals on the task, project, or document they concern, so six months later the reasoning is still where the work is.

The problem

Why context evaporates

Decisions live in chat
The reason for a change is in a thread that scrolled away in April.
Discussion attached to the work item.
Files are in three places
The current version is on somebody's drive, in an email, and in the tool.
Files on the task, with the work.
Handover means an archaeology dig
A new owner has to reconstruct why things are the way they are.
History that travels with the task.
What you get

Everything in the same place as the work

  • Comments and @mentions

    Ask on the task and pull in the right person, instead of starting an email thread.

  • Files on the work

    Attachments sit on the task or project, so the reference material is where it is needed.

  • Notifications and watchers

    Follow work you care about without owning it, and hear about changes that matter.

  • Activity history

    Who changed what and when, kept with the task rather than reconstructed later.

  • Wiki and documents

    For knowledge that outlives a task, with approvals in the self-hosted edition.

  • Unlimited users

    Everyone who needs to be involved can be, including clients and stakeholders.

How it works

How teams work together here

1
Discuss on the task
Ask the question where the work is, so the answer is findable later.
2
Mention the person
@mention pulls in whoever is needed, with a link straight to the context.
3
Attach the material
Files and screenshots land on the work item, not in an inbox.
4
Write down what lasts
Anything that outlives the task goes in the wiki or a document.
Who it's for

For teams that are not in one room

Distributed and remote teams
Async decisions that survive time zones.
Learn more →
Agencies and clients
Client feedback on the deliverable itself.
Learn more →
Regulated teams
An auditable record on your own servers.
Learn more →
Availability

Which edition includes what

Orangescrum runs as managed cloud, self-hosted on your own servers, or as the open-source Community Edition. Here is exactly what each one includes.
Discussion and files are in every edition. Wiki and documents are not.
CapabilityCloudManaged SaaSSelf-HostedOn-premise / private cloudOpen SourceCommunity Edition
Comments and @mentions
File attachments
Activity history
Task notifications by email
Task watchers
Wiki and knowledge base
Document management with approvals
Collaborative document editing
Frequently asked questions

Project collaboration FAQ

Does Orangescrum replace our chat tool?

Not for quick back and forth, and we would not claim it does. It replaces the part of chat and email where decisions about specific work get made and then lost, because those belong on the work item rather than in a thread.

Where do files live?

On the task or project they belong to, so the reference material is next to the work rather than in a drive somebody has to be pointed at. The self-hosted edition adds full document management with versions and approvals.

Can clients and contractors take part?

Yes. Every plan includes unlimited users, and role based permissions mean a client can discuss their own deliverables without seeing internal notes or other clients.

Is collaboration in the free Community Edition?

The core is. Comments, @mentions, attachments, and activity history are all there. Email notifications, task watchers, the wiki, and document management are in Cloud and Self-Hosted.

How do I keep up with work I do not own?

Task watchers let you follow specific work and get updates without being assigned to it, which is how leads stay informed without owning every task.

Where should long lived knowledge go?

In the wiki rather than in task comments. Comments explain a decision on one piece of work. The wiki holds the things that stay true across many, and in self-hosted it supports approvals.

Can we run this on our own servers for confidentiality?

Yes. The Self-Hosted edition runs on your own infrastructure, private cloud, or an air gapped network, so nothing leaves your environment.

Keep the context with the work

Comments, mentions, and attachments are in every edition, including the free Community Edition.