Glossary and data model
A project is the shared workspace for members, issues, categories, saved views, pages, integrations and its feedback board.
Choose the right object
A project is the shared workspace for members, issues, categories, saved views, pages, integrations and its feedback board. Each person in it has a role: one owner, members who work on the content, and readers who follow it. An issue is a discrete unit of work with status, assignee and optional plan, due date, objective, categories, relations, comments and resources. An objective groups project issues around a result and tracks progress. A personal cycle selects one user’s weekly or fortnightly work across projects; it is not a shared sprint or project objective.
Separate knowledge from requests
A page stores durable context such as a specification, decision or runbook and can contain nested pages, attachments and discussion. A page database stores property columns with entries that are full pages. A feedback post describes a user need with votes and a public status, separately from an internal issue. Linking a post to an issue makes its public status follow that work. A saved view filters/sorts existing issues without changing them. The task notebook is private personal notes and checkboxes; promote an item when the project should track it.
Connect the objects in a concrete workflow
For a release, create an objective in its project, describe the decision in a page and attach that page to implementation issues. A member adds selected issues to their personal cycle. Customer feedback can link to the relevant issue without exposing its private discussion. A routine starts a new Numo conversation with project context on a schedule or when a chosen event matches its conditions, such as an issue entering a status or a new database entry; it is not a recurring issue and does not change repository code. Keep object IDs and ownership when integrating: related context does not imply identical access.