Edit Wiki Content

Edit a wiki page when a process, policy, checklist, or reference changes. The knowledge base is only useful when the team can trust that pages are current.

Update wiki content as soon as the real process changes. Outdated internal docs cause repeated questions and inconsistent work.

Do not update a wiki page to describe a future process unless the page clearly marks it as upcoming. Operational docs should describe what the team should do today.

Edit a Page

1. Open the wiki page.
2. Select Edit.
3. Update the title if needed.
4. Edit the page content.
5. Select Save page.

After saving, Agiled returns to the wiki page view.

If the page describes an active process, tell the affected team after saving. People may continue following the old process until they know the wiki changed.

If the change affects finance, HR, security, support, or customer delivery, add the reason for the change or a last-reviewed note so teammates know the page is current.

For sensitive processes, include the owner who approved the change. That makes it clear who teammates should ask when a step is unclear.

Rich Text Controls

The wiki editor supports common formatting controls such as:

• Bold
• Italic
• Underline
• Headings
• Bulleted lists
• Numbered lists
• Code formatting
• Links
• Images

Use headings and lists to keep procedures easy to scan.

Prefer short sections with concrete steps. Long paragraphs are harder for teammates to use during active work.

Put the most common action near the top of the page. Background and exceptions can follow after the checklist or procedure.

What to Include

For process pages, include:

• Purpose
• Owner
• When to use the process
• Step-by-step instructions
• Exceptions or approval rules
• Related files, records, or links
• Last review note when useful

Review Before Saving

Check that links still work, screenshots or references are still current, and the page owner is clear. If a process changed because of a customer or finance issue, include the new decision rule.

Also check related forms, templates, workflows, dashboards, or settings. A wiki edit should match the actual workspace process, not only describe a future change.

Open linked records before saving when the page depends on them. Broken links, renamed templates, archived files, or changed workflow names make a wiki page look current while the process is still hard to follow.

Troubleshooting

If teammates keep asking the same question after an update, move the answer higher on the page or split the page into a clearer checklist.

If a page is no longer accurate, mark it for review or archive it instead of leaving stale instructions in place.

If a saved edit does not appear immediately, refresh the page and confirm you edited the correct wiki, section, and workspace.

Change Communication

After updating an important page:

1. Notify the team that uses the process.
2. Link directly to the changed page.
3. Explain what changed in one or two sentences.
4. Update related templates, forms, workflows, or files.
5. Schedule a review date if the process is still evolving.

Related Docs

• Create a Wiki Page
• Maintain Wiki Pages
• Files