[GH-ISSUE #6616] [Bug] Space stolen / hijacked #2906

New issue

Closed

opened 2026-03-23 21:26:04 +00:00 by mirror · 0 comments

mirror commented

2026-03-23 21:26:04 +00:00

Owner

Originally created by @JoopBman on GitHub (Oct 24, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6616

Bug Description

I'm trying out AppFlow with two accounts. I switch between them. I created a public space with account A. Then accessed that with account B. From account B i change it to private. Now account A can't see it anymore. So basically B stole it from A.

There is another space created by B and A was added as a member there. Does that cause a weird loophole. This behaviour is probably not desired?

How to Reproduce

Expected Behavior

When A created a space, he should always remain the owner?

Operating System

Windows 11

AppFlowy Version(s)

0.7.2

Screenshots

No response

Additional Context

No response

Originally created by @JoopBman on GitHub (Oct 24, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6616 ### Bug Description I'm trying out AppFlow with two accounts. I switch between them. I created a public space with account A. Then accessed that with account B. From account B i change it to private. Now account A can't see it anymore. So basically B stole it from A. There is another space created by B and A was added as a member there. Does that cause a weird loophole. This behaviour is probably not desired? ### How to Reproduce . ### Expected Behavior When A created a space, he should always remain the owner? ### Operating System Windows 11 ### AppFlowy Version(s) 0.7.2 ### Screenshots _No response_ ### Additional Context _No response_