How pages get written
How source changes refresh articles, how corrections work and what version history retains.
Sources become topic pages
OpenTag builds wiki articles from accessible company documents, Slack discussions and meeting records. A procedure in your handbook can become a starting point; later decisions and related evidence can add context.
Articles group useful knowledge by topic. Names of people, projects or customers do not automatically create a separate page for each one.
Updates take time
Changes in connected sources can refresh the articles that use them. While an update is being prepared, the last authorised version may remain visible with an update-pending indicator. A newly connected source can take time to appear.
If a page is missing something, first check that the source is connected, shared appropriately and available to you. A page cannot fill a gap in source access.
Correct a claim
Name the statement and the correction, ideally with its source:
@OpenTag the wiki says Priya owns the billing pipeline. That is outdated: Sam took over on 4 June. The handover is in this thread.
Make it clear whether you are correcting a company fact or a personal preference. Ambiguous corrections may need clarification. Team admins can correct shared company claims; personal-source corrections require their owner.
Corrections are processed in the background. Do not assume that a conversational acknowledgement means every article has already refreshed. Check the resulting page and evidence.
Change the source document
For an authored handbook or process document, edit it in its source app so the underlying material is correct too. The wiki's generated articles and version history are not a general-purpose document editor.
A request to forget a learned fact is also different from deleting the original message or source document. See Deleting your data.
History and comparisons
Open a page's history to see daily changes or individual versions, compare text, and name a version. The Changes view covers updates across the wiki.
Recent versions are kept in full for 30 days; older history is reduced to weekly versions. Named versions and the newest edition are retained. The history view does not restore an old version as the current article.
Keep sources appropriate
Use channel membership and integration sharing to control what OpenTag can reach. A prose instruction such as “don't write this down” is not a substitute for removing source access or making a data deletion request.