[GH-ISSUE #1874] [FR] Different Users #735

New issue

Closed

opened 2026-03-23 20:40:21 +00:00 by mirror · 2 comments

mirror commented

2026-03-23 20:40:21 +00:00

Owner

Originally created by @DonTomasDeLaVega on GitHub (Feb 20, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/1874

Description

A simple way of having different users could benefit teams working on appflowy out there. The main uses would be when you want someone to be tagged for example, so that they see a document. Lets admit you work with appflowy as a team. You can synchronize your documents already (for example with a synology device or any other cloud syncing technology), and you would like a user to be notified you're tagging them. Without doing something too intricate, you could simply have a little notification/bell icon, that contains the places where you've been tagged and that you haven't tagged as read. This would work with usernames, but might need a UserID refactoring part, where you have a "static" user ID and name list or something, to know which users you can tag; list that would be shared with the documents across all users.

Impact

This alone would benefit teams that work together with appflowy, and need a communication flow that goes back and forth easily.

Additional Context

No response

Originally created by @DonTomasDeLaVega on GitHub (Feb 20, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/1874 ### Description A simple way of having different users could benefit teams working on appflowy out there. The main uses would be when you want someone to be tagged for example, so that they see a document. Lets admit you work with appflowy as a team. You can synchronize your documents already (for example with a synology device or any other cloud syncing technology), and you would like a user to be notified you're tagging them. Without doing something too intricate, you could simply have a little notification/bell icon, that contains the places where you've been tagged and that you haven't tagged as read. This would work with usernames, but might need a UserID refactoring part, where you have a "static" user ID and name list or something, to know which users you can tag; list that would be shared with the documents across all users. ### Impact This alone would benefit teams that work together with appflowy, and need a communication flow that goes back and forth easily. ### Additional Context _No response_

mirror

2026-03-23 20:40:21 +00:00

closed this issue
added the
2024

new feature
labels

mirror commented

2026-03-23 20:40:22 +00:00

Author

Owner

@Jabe64 commented on GitHub (Mar 22, 2024):

Yes it would be awesome to be able to comment different projects like Monday.com does.

And we could also imagine other collaborative communication tools, for example to be able to create a new page type (on top of the classic Document/Grid/Board/Calendar etc) called "chat channel" or "Comments" and inside of it messages will appear with usernames and time of post and it will allow AppFlowy to replace Slack 🤯

@Jabe64 commented on GitHub (Mar 22, 2024): Yes it would be awesome to be able to comment different projects like Monday.com does. And we could also imagine other collaborative communication tools, for example to be able to create a new page type (on top of the classic Document/Grid/Board/Calendar etc) called "chat channel" or "Comments" and inside of it messages will appear with usernames and time of post and it will allow AppFlowy to replace Slack 🤯

mirror commented

2026-03-23 20:40:22 +00:00

Author

Owner

@annieappflowy commented on GitHub (Jun 21, 2024):

#3899 comments planned in Q3
We supported team collaboration

@annieappflowy commented on GitHub (Jun 21, 2024): #3899 comments planned in Q3 We supported team collaboration