Engagement

A built-in feature of Attain OS — included with every app.

Project Activity Feed

One stream per project with activity from your apps and updates from your team, plus replies, likes, @mentions and filters.

Unified Organization & Productivity

Activity From Your Apps

Connected to the same project, people, permissions, and AI context.

Team Posts With Attachments

Connected to the same project, people, permissions, and AI context.

Replies, Likes and @Mentions

Connected to the same project, people, permissions, and AI context.

Filters and Search

Connected to the same project, people, permissions, and AI context.

Atty can read the project's most recent feed entries and sum them up for you in chat, and it can draft a post or a reply that goes up only after you approve it. It also adds a short one-line insight to a few key entries, such as a completed task or a new booking.

Connected to the same project, people, permissions, and AI context.

Working guide

An internal communication app gives a team one place to post updates, answer them and mention the people who need to act. The Feed in Attain OS works per project: it collects activity from that project's apps and the team's own posts, with replies, likes and @mentions under each entry. Use it for updates the whole project should see, and keep one-to-one chat in Conversations.

Workflow map

From an update to a team that acts on it

JobAppWhat it does here
Post the updateThe FeedWrite the update with formatted text, and attach images, PDFs, Word or Excel files. Each attachment is also saved in Documents, so the file stays with the project after the post scrolls out of view.
Keep the discussion attachedThe FeedReply under the post, like it, and edit or delete your own comments. The answers stay with the update, so the next person who reads it sees the question and the reply together.
Ask a specific person to actTeamMention a teammate with @ to notify them. Check the team directory first if you are unsure who handles the topic or how they prefer to be contacted. Mention only the people who must act, so their notifications stay meaningful.
Keep private exchanges separateConversationsChat messages and direct exchanges stay in Conversations rather than the Feed. Use a conversation when two people need to work something out, and post the outcome in the feed if the project needs to know it.
Find what changedTasksFilter the feed by type, team member and time range, or search the text of entries. Completed tasks show up as entries, so you can see what finished this week without opening each list. The feed reflects what the apps recorded; it does not replace the task itself.
In practice

A week of updates that reach the right people

  1. Monday · post the priorities

    The project lead posts a short update with the week's priorities and attaches the plan as a PDF. Teammates read it when they open the project. The attachment also lands in Documents, where the plan is easy to find later.

    The Feed
  2. Tuesday · answer under the update

    A teammate asks whether a supplier delivery is still due on Thursday. The answer goes under the post as a reply, so the question and the answer stay together. If the answer changes the plan, the person who knows should edit their own comment or post a correction.

    The Feed
  3. Wednesday · mention the owner

    A customer complaint has been logged as a case, and the teammate who owns cases needs to act on it today. Mention them in a feed post that names the case, so they are notified and see the context. The case itself stays the record of what was done.

    Customer Care
  4. Thursday · review one teammate's week

    Before a check-in, filter the feed by one team member and a time range. You see the tasks they completed and the notes they added, which gives the conversation a starting point. Use it to ask questions, not as a score.

    Tasks
  5. Friday · catch up

    Open the feed and filter by type to see new documents, completed tasks and form responses from the week. Search for a supplier or customer name to find the thread you need. The feed loads when you open it, so reopen it before you start the day to see later entries.

    Documents
Start here

Memos, policies and ideas that need a record

Corporate memo

Choose a memo when the update is formal and needs one clear version, not a running thread.

Employee suggestion box

Collect operational ideas in a form that can be anonymous or identified, instead of a public post.

HR policy portal

Keep the policy text on one page and use the feed only to announce that a policy changed.

Mistakes to avoid

Where a feed goes wrong

Using the feed as a chat channel

The feed holds posts and replies about the project's activity. People read it when they open it, so it is a poor place for a question that needs an answer within minutes. Put quick exchanges in Conversations, and post only the result here.

Posting a decision without an owner

An update that says a supplier will change needs a named owner who acts on it. Mention that person, and turn the next step into a task so the feed is not the only record of what was agreed. A post without a follow-up is easy to read and forget.

Treating a like as a sign-off

A like only shows that someone liked a post. It is not a confirmation that they agree or have completed a step. When you need a confirmation from each person, use a form or give each person a task with their own name on it.

Working checklist

Before you post to the feed

Write the post

  • Name the project and keep the post to one topic.
  • Attach files only when the post needs them, and give each one a clear name.
  • Mention only the person who must act, and say what they need to do.

After the discussion

  • Turn each agreed action into a task with one owner.
  • Record the decision in the app that owns it.
  • Check the filters when you need to find the thread again.
What this agreement means

What the Feed gives your team

  • The Feed is one activity stream per project, with entries from tasks, notes, budgets, tickets, cases, forms, calendar events and more, plus posts from the team.
  • Posts take formatted text and attachments: images, PDFs, Word and Excel files. Each attachment is also saved in Documents.
  • Replies, likes, @mentions and edits or deletes of your own comments sit under each entry.
  • Filters cover type, team member and time range, and a search reads the text of entries.
  • Chat messages stay in Conversations, and the feed loads when you open it rather than streaming live.

Feature evidence: the project feed page, the feed item card, the comment input and the project activity service that saves attachments to Documents. The feed is a team activity stream, not a compliance audit log.

Frequently asked questions

What does an internal communication app do for a small team?

It gives the team one shared place for updates that the whole project should see, with replies and mentions so each discussion stays attached to its update. It suits announcements and progress notes. For quick questions and private exchanges, use a chat tool, and decide before you start which kind of message each place carries.

Is a team activity feed the same as a group chat?

No. The Feed collects activity from the project's apps and the posts the team writes for the project. Chat messages stay in Conversations, and a feed post does not open a private thread. Use the feed to record what the team should see, not to hold a running exchange.

Can a feed post notify a specific person?

Yes. An @mention notifies the teammate you name. Mention only the people who need to act, so that each notification means something to them.

Can the feed confirm that everyone has read an announcement?

No. A like or a reply is not a sign-off. If you need each person to confirm something, collect that in a form, or give each person a task with their name on it.

Attain OS BETA