Replace scattered docs with a crowdsourced wiki. Attain OS and Atty AI draft your internal wiki page from project context. Review and publish in minutes.
An internal wiki page is more than a document — it's the living memory of your team. It captures processes, policies, and tribal knowledge so everyone stays aligned. But building one from scratch? That's a slog. You end up copying from old emails, chasing subject matter experts, and formatting for hours.
Attain OS changes that. Instead of juggling a stack of separate tools (Notion, Google Docs, Confluence), you work in one all-in-one system. And with Atty, your built-in AI agent, you don't start with a blank page. Atty drafts a polished internal wiki page from your project context, brand settings, and notes. You review, refine, and publish — all without switching apps.
Your team is growing fast, and every new developer asks the same questions. Instead of answering individually, you create an internal wiki page with onboarding steps, code conventions, and team contacts. Atty pulls from your existing notes and tasks to produce a draft that covers everything from day-one setup to first commit.
The monthly budget reconciliation is a nightmare of spreadsheets and emails. You want a wiki page that spells out each step, who approves what, and where to find templates. Give Atty the project context (your Budgets and Tasks apps) and it writes a clear procedure. You just add a few specifics and share it with the team.
After a long strategy session, key decisions are scattered across notes and memories. You create a wiki page to record the outcome, action items, and rationale. Atty scans your Calendar and Notes to generate a draft that captures the context and decisions, saving you from reconstructing the conversation.
Open the Content Creator app and select 'Internal Wiki Page' as the deliverable. Atty looks at your project — your Notes, Tasks, Calendar, and even past Documents — to understand the topic and audience.
Atty produces a first draft with clear sections like 'Purpose', 'Process', 'Roles', and 'Resources'. It uses your brand voice (set in the system) and structures the content like a real wiki entry.
You get a nearly finished page. Edit headings, add links to relevant People or Tasks, insert screenshots from your Documents, and clarify any points. Atty's draft is a starting point — you have full control.
Once satisfied, publish the page directly to your team via The Feed or Sharing Hub. No export, no third-party tool. The wiki lives inside Attain OS, accessible to everyone with the right permissions.
A close-to-finished draft — not a blank page. Here's the kind of result the flow hands you, ready to review, tweak, and publish.
This page outlines the steps to request and approve expense reimbursements. It ensures consistent handling and timely payments.
Employee submits a request via the Forms app. Manager reviews and approves in Tasks. Finance processes payment using Budgets and Reconciliations.
1. Fill out the Expense Reimbursement Form (available in Forms). 2. Attach receipts as PDFs. 3. Route to your manager. 4. Manager approves in Tasks. 5. Finance reconciles in the Budgets app.
Yes. You can add images, PDFs, and other files from your Documents app directly into the wiki page. Atty does not insert media automatically, but you can drag and drop them during review.
Open the wiki page from the Content Creator or Documents app, edit it, and republish. There is no version history, so you may want to keep a backup note of previous versions in your Notes app.
Absolutely. The editor supports internal links to People, Tasks, Notes, Forms, and other wiki pages. This creates a connected knowledge base inside Attain OS.
Atty works best when you provide project context — like related notes, tasks, or calendar events. It drafts from what it can see in your Attain OS workspace. The more context you give, the better the draft.
