Home
/Open the tenant knowledge homepage.
Kognis
AvailableKognis is the internal documentation space for runbooks, procedures, decisions, and team knowledge. Authors can write in markdown, organize pages by area, control access, and keep versioned history for operational reference.
Verified user manual
Kognis user manual
Find, create, structure, revise, and govern internal knowledge in the Kognis 2.0 wiki.
Audience, scope, and prerequisites
Covers Kognis page reading, search, Markdown editing, navigation hierarchy, assets, history, and role-controlled administration. Server, database, storage-target, and authentication-provider administration are excluded.
Who this is for
- Knowledge readers
- Authors and reviewers
- Wiki administrators
Before you sign in
- A Kognis identity in the correct tenant
- An agreed page location, owner, review date, and audience
- Approval and rights for attachments or media
Roles and responsibilities
| Role | Access | Responsibilities |
|---|---|---|
| Reader | Read and search pages and permitted assets. |
|
| Author | Create and edit pages and upload assets where path rules allow. |
|
| Administrator | Manage navigation, groups, permissions, locales, and system configuration. |
|
Find and plan knowledge
Search and browse the hierarchy before creating a page so one authoritative source remains easy to discover.
Find authoritative content
Use navigation and search, then verify ownership and recency before relying on a page.
- 1Browse the hierarchy
Start from the relevant space or parent topic in the sidebar.
- 2Search with specific terms
Use product names, task phrases, error text, and known titles.
- 3Open the best result
Confirm path, tenant, audience, owner, and related pages.
- 4Check recency and history
Review the page metadata or history when the decision depends on current guidance.
- 5Report ambiguity
Ask the owner to consolidate conflicting pages rather than choosing silently.
Expected result
The reader identifies one current, authorized page or records that authoritative guidance is missing.
Plan a new page
Choose a durable path, audience, owner, and structure before opening the editor.
ForAuthor
- 1Search for overlap
Check alternate terminology, acronyms, and neighboring paths.
- 2Choose the parent path
Place the page under the relevant product, team, or process hierarchy.
- 3Define purpose and owner
State who the page serves, what decision or task it supports, and who maintains it.
- 4Gather approved sources
Use authoritative policies, code, release information, or owner decisions.
Expected result
The planned page has a unique purpose, durable location, responsible owner, and approved source set.
Author and publish pages
Write task-oriented content with clear headings, links, and evidence; do not use the wiki as an uncontrolled file dump.
Create or edit a Markdown page
Use the enabled editor and complete page metadata before saving.
ForAuthor
- 1Open the intended path
Navigate to the missing path and choose Create, or open an existing page and choose Edit.
- 2Set title and metadata
Confirm locale, path, description, visibility, and any publish timing fields.
- 3Write structured content
Use one page title, ordered headings, concise steps, meaningful links, and accessible tables or lists.
- 4Preview
Check Markdown rendering, links, code blocks, images, and narrow-screen readability.
- 5Save with context
Use the available description or change message to explain the update.
- 6Verify the page
Open the rendered path and check sidebar placement and permissions.
Expected result
The page renders at the intended path, is visible only to its audience, and has a traceable version.
Upload and insert an asset
Use a controlled folder, durable filename, and accessible description.
- 1Open the asset picker
From the editor, browse the existing asset hierarchy.
- 2Search before upload
Reuse an approved current asset when possible.
- 3Choose the folder
Place the file under the appropriate product or topic path.
- 4Upload the prepared file
Use a stable filename and verify type, size, rights, and removal of unnecessary metadata.
- 5Insert and describe
Add meaningful alternative text or link text and verify rendering.
Expected result
The asset exists once in an authorized folder and is referenced accessibly from the page.
Review history and govern access
Use history for traceability and apply permissions to paths and groups with explicit tests.
Compare or restore page history
Identify the intended revision and restore it through a new traceable change.
- 1Open History
Use the page history action when your permissions allow it.
- 2Review revision metadata
Compare author, time, action, title, path, and content.
- 3Select the recovery point
Confirm it contains the desired state and no outdated policy.
- 4Restore or edit
Use the supported restore/edit flow and describe why the content is being recovered.
- 5Verify permissions and links
A historical version may contain paths or references that are no longer valid.
Expected result
The recovered content is published as a traceable current revision and remains valid under present policy.
Change page or path access
Use groups and path rules to implement the least access required.
ForAdministrator
Before you begin
- Approved access change with affected paths and test identities
- 1Identify effective scope
List the exact path, descendants, locale, groups, and required read/write/history/asset permissions.
- 2Review existing rules
Account for inherited allow and deny behavior before adding a rule.
- 3Apply the smallest change
Grant only the required permissions to the approved group.
- 4Test allowed access
Use a representative authorized account to verify required actions.
- 5Test denied access
Use a representative unauthorized account to confirm content, history, source, and assets remain protected.
Expected result
Authorized users can perform required actions and unauthorized users cannot discover or retrieve protected content.
Security and data handling
- Place content in the correct tenant, locale, and path.
- Use groups and path rules rather than sharing credentials or public links.
- Protect page history, source, assets, and search results as well as the rendered page.
- Do not store secrets or unnecessary regulated data in wiki pages.
- Review AI-assisted edits and semantic answers against authoritative sources.
Known limitations
Read before relying on an unsupported workflow
These limits describe the source-pinned Kognis 2.0.0 scope and must be rechecked when the product changes.
- Available editors, search engines, semantic search, and AI features depend on administrator configuration.
- Page history and source access require separate permissions.
- Assets follow path and role checks and may not be accessible to every page reader.
- Restoring old content does not make old links, policy, or attachments current.
Troubleshooting
You cannot sign in to Kognis
Likely cause: The session expired, the identity is not assigned to the application, or the tenant claim is missing.
- Open the application from the approved portal and complete sign-in again.
- Confirm that the correct organizational identity and tenant are selected.
- If access is still denied, record the time and request an entitlement check from support.
A documented action or navigation item is not visible
Likely cause: The current role, release, tenant configuration, or feature flag does not expose that operation.
- Confirm the role and prerequisites listed for the procedure.
- Reload the page after signing in again; do not attempt to bypass the interface through direct URLs.
- Ask the product owner whether the feature is enabled for the tenant before reporting a defect.
A saved change or background operation is not visible
Likely cause: Validation failed, processing is still running, or the current view is stale or filtered.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search for the item by its stable name or identifier.
- Do not repeat irreversible or externally visible actions until the original operation status is known.
A page is missing from navigation but opens by URL
Likely cause: The page exists but the navigation tree, locale, group visibility, or cache does not include it.
- Confirm page path, locale, and publish state.
- Review navigation rules and group scope.
- Do not duplicate the page solely to make it appear in the sidebar.
Search does not return a known page
Likely cause: The page is not published or readable, indexing is delayed, or search terms differ from the content.
- Open the page directly and confirm permission and publication.
- Search exact title and distinctive body terms.
- Ask an administrator to review indexing only after access is confirmed.
Contact support
Contact support when
- A repeatable Kognis error blocks an approved workflow
- Expected data, permissions, or tenant boundaries appear incorrect
- A security, privacy, compliance, or data-loss concern is suspected
- Conflicting pages cannot be consolidated safely
- A permission or search result may expose protected content
Include
- The page, action, and expected result
- The exact error text and time of occurrence, including time zone
- Your tenant, role, browser, and a sanitized record or item identifier
- Whether the problem can be reproduced and which troubleshooting steps were tried
Never include
- Passwords, access tokens, API keys, recovery codes, or session cookies
- Unredacted personal, health, financial, or other regulated data
- Private encryption keys or complete confidential documents unless an approved channel is provided