Short answer: How internal links in Aamu.app connect docs, tasks, projects, meetings, support tickets, files, and other workspace context.

Internal links connect Aamu tasks, Docs, tickets, emails, meetings, databases, files, designs, posts and chats.

Whenever you are writing rich content in Aamu, such as a Doc, task description, ticket reply, comment, meeting note, or post, you can link to another Aamu item instead of copying context by hand.

What an internal link is

An internal link is a link from one Aamu item to another Aamu item. It can point to the exact task, Doc, ticket, email, meeting, database, design, file, or other workspace item that gives context to what you are writing.

For example:

  • a task can link to the Doc that explains the feature,

  • a Helpdesk ticket can link to an internal policy Doc,

  • a meeting note can link to the task that should be completed next,

  • a Doc can link to a database that contains the structured data, and

  • a support reply draft can link to the relevant internal source material for the team.

Where you can add them

Internal links are available in many Aamu writing surfaces. The exact UI depends on the editor, but the idea is the same: while writing, open the internal-link search, find the item, and insert the link.

You will see this pattern in places such as:

  • Docs,

  • task descriptions and comments,

  • Helpdesk tickets and replies,

  • Email comments and drafts,

  • Meeting descriptions and comments,

  • posts and status updates, and

  • chat and other rich-text contexts.

The editor search can show full Aamu links, so you do not need to know or paste raw URLs manually.

How to use them well

The best internal links are specific. Link to the item that actually answers the question.

Instead of writing:

See the docs.

Write:

See the cancellation policy Doc.

Instead of copying a long customer issue into a task, link the task back to the original Helpdesk ticket and summarize only the action needed.

Internal links vs linked content

Aamu also has linked-content relationships in some workflows. For example, creating a task from a ticket can create a stronger relationship than just placing a link in text.

Use the two tools differently:

  • Use an internal link when you want to reference something inside text.

  • Use linked content when the relationship itself matters to the workflow, such as a ticket causing a task or a database item being connected to another item.

Why internal links matter for support

Support work often needs context. A customer asks a question, and the correct answer may depend on a policy Doc, a previous ticket, a task, or an internal product note.

Internal links let the team keep that context close. A support person can link the ticket to the relevant Doc, create a task for the follow-up work, and later return to the ticket without reconstructing the history.

Why internal links matter for Docs

Docs become more useful when they point to the work around them. A project brief can link to tasks, designs, meetings, and databases. A support knowledge Doc can link to example tickets. A blog source Doc can link to the database row that publishes it.

Why internal links matter for AI

Internal links help people maintain clear source material for AI: which Doc explains a decision, which tickets illustrate it and where repeated answers belong.

When a repeated support answer becomes a Doc and tickets link back to it, the team has a better source for future AI-assisted drafts and live chat answers.

A practical habit

Whenever you write "see this", "related to that", "from the customer issue", or "as discussed", pause and add the internal link.

Related articles