The topic author cannot always see their own topic.
Sometimes, TL3 users move topics to categories that the topic author cannot access, resulting in a loss of access to the topic.
This is definitely not the intended behavior. Regardless of the category, the topic owner should always be able to see their own topic.
At the very least, an option should be added for site administrators to customize this.
AI-generated summary
The discussion Topic owners should always see their post began with SoteFun pointing out that topic authors may lose access to their own topics when moved to categories they cannot access by TL3 users. SoteFun believes this is not the intended behavior and suggests adding an option for site administrators to customize this. Jagster considers this a #feature or Product Support request rather than a bug.
Canapin questions the intended behavior, prompting 6512345 and SoteFun to provide real-life use cases. In these scenarios, a post is moved to a category only accessible by higher trust level (TL) users, resulting in the topic owner losing access. SoteFun suggests adding global or category settings and a hint when moving categories to prevent this issue. Jagster disagrees with giving total rights to see own posts, as sometimes posts need to be hidden from the public. merefield finds the forum structure strange and inquires about the reason for restricting access. SoteFun explains that access is restricted to prevent abuse of voluntarily shared services.
Contribute > Feature or Support request, defenetly not a bug. But I don’t change that.
Or should moderators be guided bit better?
1 Like
I moved it to Contribute > Feature
Seems like the intended behavior to me. 
Can you describe a real-life use case?
1 Like
A TL2 user creates a post, it got moved to categories that only TL3 user can access.
The user who creates the post will not be able to edit or view the post.
I’ve done such move once accidentally, because I wasn’t thinking what I did. But giving total right to see own post thru whole forum is not a solution, because sometimes there is need to hide a post from public totally, and unlisting doesn’t do that.
After that one case I reconsidered what category settings I really need and told to myself it is always good react, but next time measure twice, cut once — old carpenter’s thought.
I’m involved in a forum related to resource sharing. For part of the reason, we need to limit viewing permissions for posts through trust levels to prevent misused resources.
Some TL3 users will kindly switch a post to a higher TL category in order to restrict access more strictly. But at this time, TL3 users will not know that they are blocking the topic owner from accessing their own posts.
This happens frequently and causes a lot of confusion
Indeed, at some point this is expected behavior, but it’s better to add global/category settings and add a hint when moving categories?
1 Like
Sounds like a strange structure for a forum. Why are they restricting access at all? What’s so special about the topic you were discussing?
2 Likes
We have some services that users voluntarily share, because preventing abuse causes usually set higher TL restrictions.