Knowledge ownership is optional. Add it when a responsibility Role should be visibly responsible for keeping a collection useful. The owner control in the product is on the Area; Source-level ownership is reachable through the API only. Leave it empty when the origin already provides the maintenance model or no accountable owner is needed.
Source owner
Useful for one distinct item.
- A specific maintainer
- A separate risk or review cycle
- Visible stewardship
Area owner
Useful for a maintained collection.
- One coherent scope
- Shared review responsibility
- Less repetitive assignment
Ownership does not change authority
An owned Source remains Knowledge. Ownership improves stewardship, but it does not make the content an organizational rule and does not make it override a Standard.
Choose a maintainable level
Assign ownership where someone can realistically review changes. Responsibility at the Area can be clearer than giving every small Source a separate owner. Use Source-level ownership when one item has a distinct maintainer or risk.
External origins
For a synchronized Source or Website, the upstream publisher may remain the real content owner. Tindre ownership can identify who is responsible for scope, connection health, and whether the material should still be used internally.
Ownership and access are separate
An owner does not automatically gain broad editing permissions, and assigning an owner does not restrict readers. Access roles govern actions; Role visibility governs readable material where applied.