Social in Inflow Home
Availability: Social is not available as a user-facing page in the current Inflow Home. Do not follow the sample actions below in a live environment. They show how the proposed experience is intended to feel; the current backend is default-off and some planned capabilities are not connected to a usable Home screen.
This guide uses a simple People Operations story to explain the intended experience. Rana wants to share an update with her team, read a colleague's reply, and save a useful post for later. No part of this example grants access to a workspace, record, task, or document. A future release must check the signed-in user's current access whenever it shows or opens content.
What a future Social page may look like
1. Find updates you are allowed to read
Rana opens Home and chooses a workspace she can access. A future Social page could offer Recent, Following, and Saved views. These would be different ways to find posts; following or saving a post would not give Rana permission to see it. A post linked to a record or document would appear only while both the post and the linked source remain available to her.
For example, Rana may see “The leave calendar is ready for review” in the People Operations workspace. She opens the post and reads its comments. If a comment or linked item is removed or becomes unavailable, the page should not reveal its old text or hidden target. If the service is temporarily unavailable, the page should say that it could not load the content rather than presenting an empty feed as if there were no posts.
2. Write an update for a specific audience
In the proposed flow, Rana chooses an audience offered to her, writes a short update, reviews it, and selects Post. The audience determines who may see the post; it does not grant those people access to linked business records. Posts are plain text, not executable HTML or scripts.
Before the feature is released, the audience choices, edit/remove controls, and any comment actions must come from the server's current permissions. Editing should show Rana the version she started from. If another person changes it first, Rana should review the current version before deciding whether to save her own edit. Removing a post hides it according to the platform's retention and audit rules; it does not delete linked business records or documents.
3. React, save, or follow without changing business work
A future page may let Rana react to a post, save it for herself, or follow it for later updates. These actions are social preferences; they do not complete tasks, approve requests, or alter records. Following a post must never bypass access checks.
Notifications for mentions or followed-post changes are not currently delivered by Home. Typing @Rana into a message does not notify anyone. The user-facing feature would need a private recipient picker and fresh access checks before sending a notice. A moderation report would request review by an authorized moderator; it would not automatically hide the post.
4. Recover safely if a save is uncertain
When a future Social page is available, a lost response may leave the result of a save uncertain. The safe experience should offer a way to check that same attempt. If it cannot establish the result, use the same attempt's recovery path or the ordinary supported workflow. Do not repeat the action as a new post or edit just because a response was slow. If the page reports that the content changed, read the current version before trying again.
Today there is no Social page or Check outcome control to use. Continue with the application's ordinary supported workflow until this feature is released.
Attachments, links, and mentions
The current Home Social write path does not accept non-empty attachment, business-reference, or mention content. There is no supported way to attach a private document, share a record link, or notify a person from a Home Social post today. Do not paste credentials, use an arbitrary external URL as a substitute for a private attachment, or assume that typing a person's name shares a record with them.
A future release may add a Share in Social action to approved parts of Inflow. Selecting it would add a private link hint to the draft, not copy protected record contents into a public post. When a reader opens that link, Inflow must check their access again and show only the destination's ordinary permitted view. If access was removed or the destination is no longer available, the link should open as unavailable without exposing process diagnostics or hidden data.
Arabic, keyboard, and privacy expectations
When Social is delivered, the interface should support Arabic right-to-left reading and mixed-direction names and references. Every action should be reachable by keyboard and have a clear accessible name. A user's visible content and pending changes must not leak into another account's session. Signing out or changing workspace should remove protected content from view and stop work that belongs to the previous context.
These are release expectations, not proof that a screen or journey exists today. For the current Home scope and availability, see Inflow Home, publishing, operations, and the Social completion record.