Federation
Share tasks, deliverables and meetings with a client's or a partner's Symbifox without opening yours.
Working with a client on their tasks usually means opening an account for them on your side, or asking them to open one on theirs. Both cost, and both leak.
Two instances that trust each other pair by invitation, administrator to administrator: one issues a single-use code, the other accepts it. A shared secret is born of the two halves, neither instance picks it alone, and it then signs every message.
A federated task appears on the other side in a closed project, addressed to someone you propose; the partner decides. State, due date, messages and small attachments travel both ways.
The task does not cross alone. Satellite modules also share delivered documents, meeting agendas and reports, process maps, schedules, timesheet statements and outreach tracking.
⚠️ What does not cross matters just as much. Internal notes stay with their author, unless their side chooses to send them to that partner. A message that begins with 🔒 stays home, always. Nothing is ever deleted: withdrawing a share stops the exchange, it does not erase what was said.
Only projects that name a peer offer sharing, which keeps a task from landing at a partner's through one distracted click.
Comparable to Nextcloud federated sharing, Asana guests, Jira external collaborators
Shall we look at your case together?
Tell us what you run today. We will tell you honestly whether Symbifox helps or not.
The catalog grows almost every month.
What gets added, what we learn deploying it, and nothing else. You leave whenever you want.
One confirmation email, and nothing before you follow its link. Then 10 welcome emails, one a week, then the updates. No tracker, no resale.