Organisation
One customer account, with its identity, ownership, policies and member directory. Each Organisation has exactly one Organisation Owner.
Start here to understand where work belongs, what each role can do and how working context becomes approved knowledge.
Structure
Every piece of context in cRUD Collab has a home, and that home decides who can see it.
One customer account, with its identity, ownership, policies and member directory. Each Organisation has exactly one Organisation Owner.
A customer product, service or governed body of work. Organisation membership alone does not grant access to every Product.
A grouping of members within one Product, used to manage access. It is never an organisation-wide permission shortcut.
A defined body of work within one Product. Project members come from the parent Product, and every Project inherits the Product’s approved shared context.
A persistent collaboration space scoped to a Product or Project. A Room defines context and membership, not what participants do inside it.
One live or individual occurrence linked to a Room, Product or Project. A Room persists, and each time people work in it is a Session.
Context
cRUD Collab separates what has been observed from what has been proposed, and both from what has been approved.
Traceable source material or an observation, such as code, a test result, a document or a Session record. Evidence is not automatically the truth.
Draft, proposed, uncertain or under-review understanding. It is never presented as approved knowledge.
Current, trusted knowledge. Only a person in the Context Approver role can promote information into this state.
A purpose-specific, permission-scoped collection assembled for a person, Session, workflow or AI tool. It references context rather than becoming a separate source of truth.
Lifecycle. Context moves through Draft, Proposed, Under Review, Approved and Active. Later it can be Superseded, Rejected, Retired or Archived. Approved information is never silently overwritten.
Roles
Professional titles do not grant authority in cRUD Collab. Access and approval come from the roles a person is given.
Manage the account, its members, policies and directory. Ownership can be transferred, and there is always exactly one Organisation Owner.
Set membership, context policy, inheritance and exceptions for their Product or Project. Ownership does not by itself make them the only approver.
A person authorised to approve specified context at Product, Project or category scope.
Creates Evidence and Working Context and proposes knowledge, without automatically approving it.
Takes part in or follows the work within the access granted, with no approval authority by default.
Joins specific work by invitation. Guest access never bypasses Product membership.
Session roles such as Facilitator or Host, Moderator, Presenter, Participant and Observer organise a Session. They do not grant context approval.
Review and approval
Approval follows the policy set for the Product or Project. The defaults are deliberately simple.
An approved AI tool never receives more context than the person who started its work.
Alongside your systems
Repositories, editors, issue trackers, CI, documents and communication tools remain authoritative for the work they already do. Evidence brought into cRUD Collab keeps a link to where it came from, and actions that belong to another system stay in that system.
cRUD Collab is browser-first collaboration, not a browser IDE. Code stays in the editors and repositories the team already uses.
This page explains concepts and terminology. It does not list every capability, configuration or connected system. To see the context model in motion, read the workflow, the approach and the solutions.
Questions
Product status
The product has not been released. Explore the current design and product thinking, or contact the team about the direction.