The community feed is a shared social space for everyone in your workspace. Members and staff can publish posts, react with likes, and hold conversations through comments and replies. This article explains how each part of the feed works, who can post, how posts can be scoped to a single location, how notifications are sent, and how moderation and deletion are handled.
Posts
A post is the top-level unit of the feed. Each post belongs to a single workspace and is authored by the signed-in user who creates it. When a post is created, Deskie records the author, the workspace, the post text, and an optional image.
To create a post, type your message into the post composer at the top of the feed. A post must contain either text or an image: if you try to submit with no text and no image, Deskie asks you to write something or add an image first. You can attach a single image to a post. Images are uploaded to secure storage before the post is published, so if you attach a picture you need to wait for the upload to finish before posting. Images can be up to 10MB.
Posts are displayed newest first. Each post in the feed shows the author's name and profile photo, the post content, the image if one was attached, and running counts of how many comments and likes it has received.
Who can see and post to the feed
By default the feed is workspace-wide: every member of the workspace sees the same stream of posts, and posts are not tied to any particular location. This is the standard behavior for single-location spaces.
For multi-location workspaces, Deskie offers an optional per-location feed mode that is turned on in workspace settings. When per-location scoping is enabled, a new post is stamped with the author's current location, and that post is only shown to people who are currently working in that same location. Posts that were created before per-location mode was switched on, or any post that has no location attached, remain visible to everyone. This keeps older content readable while newer posts respect location boundaries.
Comments and replies
Every post supports a conversation thread. There are two levels of discussion:
- Comments are written directly on a post. A comment can include text and, optionally, an image.
- Replies are written on a comment. A reply is text only and does not support an image attachment.
Comments and replies are both shown in chronological order, oldest first, so a thread reads naturally from top to bottom. Each comment and reply displays the author's name and profile photo alongside the message. To open the discussion on a post, expand its comments, type your comment, and submit it. To respond to a specific comment, use that comment's reply option and write your response.
Likes
Likes are available at all three levels of the feed: you can like a post, a comment, or a reply. Liking works as a toggle. The first time you tap like, your like is recorded. Tapping it again removes your like. You can only ever count once toward an item's like total, so liking is a simple on or off state per person.
Deskie keeps a running like count for every post, comment, and reply, and it also tracks whether you personally have liked each item so the interface can show your current state. You must be signed in to like anything: liking is tied to your user account.
Names and profile photos in the feed
The name and photo shown next to a post, comment, or reply come from the author's user account. If an author's name cannot be resolved, the feed displays "Unknown User" rather than leaving the byline blank.
Notifications for new posts
Workspaces can optionally notify everyone when a new post is published. This is controlled by a feed setting in workspace settings and is off by default. When it is turned on, creating a post triggers a notification fan-out to eligible workspace members.
The notification step never blocks or delays publishing. The post is saved first, and notifications are then sent in the background, so a slow or unavailable email or push provider cannot prevent a post from going live.
Recipients are determined as follows:
- The author is always excluded, since they already know about their own post.
- If the post is workspace-wide (no location attached), every member of the workspace is eligible.
- If per-location scoping is on and the post is stamped with a location, only people who have a role at that location are notified.
Eligible recipients can receive both a push notification on their subscribed devices and an email. Push and email are sent independently, so a problem with one does not stop the other. The email includes a short preview of the post and links the recipient back to the feed. Email sending also goes through Deskie's shared notification service, so it respects your workspace email configuration and the platform-wide notification switch like the rest of Deskie's email. For more on notification behavior across the product, see Notifications.
Moderation and deleting posts
Moderation in the feed is handled through deletion. There are two ways a post can be removed:
- Authors can delete their own posts. The person who wrote a post can always remove it.
- Staff with feed management permission can delete any post. This permission belongs to workspace owners, workspace admins, and location admins, giving them the ability to moderate content that others have published.
The delete option only appears in the interface for posts you are allowed to remove. When you delete a post, you are asked to confirm the action first. Deleting a post is permanent and also cleans up everything attached to it: the post's comments, all replies on those comments, and every like on the post, its comments, and its replies are removed at the same time. There is no separate moderation queue or approval step. Posts publish immediately and are taken down by deletion when needed.
To learn more about which roles include feed management and other staff capabilities, see Roles and permissions.
Tenant isolation
Every part of the feed is scoped to your workspace. Posts, comments, replies, and likes are always read and written within the context of the current workspace, so feed content never crosses between different workspaces on the platform.