A starting point for cRUD Collab terms.

Get familiar with the language we use to describe work, evidence and approval. The cRUD Collab documentation goes deeper into roles and permissions.

Structure

Where work and context belong.

Every piece of context in cRUD Collab has a home, and that home decides who can see it.

Organization

One customer account, with its identity, ownership, policies and member directory. Each Organization has exactly one Organization Owner.

Product

A customer product, service or governed body of work. Organization membership alone does not grant access to every Product.

Product Team

A grouping of members within one Product, used to manage access. It is never an organisation-wide permission shortcut.

Project

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.

Room

A persistent collaboration space scoped to a Product or Project. A Room defines context and membership, not what participants do inside it.

Session

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

Four terms that keep trust explicit.

cRUD Collab separates what has been observed from what has been proposed, and both from what has been approved.

Evidence

Traceable source material or an observation, such as code, a test result, a document or a Session record. Evidence is not automatically the truth.

Working Context

Draft, proposed, uncertain or under-review understanding. It is never presented as approved knowledge.

Approved Context

Current, trusted knowledge. Only a person in the Context Approver role can promote information into this state.

Context Package

A collection assembled for a defined purpose and limited to people who have permission. It can serve 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

Roles define who can do what.

Professional titles do not grant authority in cRUD Collab. Access and approval come from the roles a person is given.

Organization Owner and Administrator

Manage the account, its members, policies and directory. Ownership can be transferred, and there is always exactly one Organization Owner.

Product Owner and Project Owner

Set membership, context policy, inheritance and exceptions for their Product or Project. Ownership does not by itself make them the only approver.

Context Approver

A person authorised to approve specified context at Product, Project or category scope.

Contributor

Creates Evidence and Working Context and proposes knowledge, without automatically approving it.

Participant or Viewer

Takes part in or follows the work within the access granted, with no approval authority by default.

External Guest

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

How context becomes trusted.

Approval follows the policy set for the Product or Project. The defaults are deliberately simple.

  • One authorised Context Approver is sufficient
  • Sensitive categories can require more than one approval
  • A contributor cannot approve their own proposal unless an explicit, scoped policy grants that authority
  • AI tools can propose, but never approve
  • Session roles and job titles never grant approval on their own

An approved AI tool never receives more context than the person who started its work.

Alongside your systems

Systems of record stay where they are.

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 works in the browser, but it is 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

Context and access

What is included in a Context Package?
A Context Package references material selected for a specific person, Session, workflow or AI tool. Its scope is limited by the purpose of the package and the permissions that apply.
What determines what an External Guest can see?
The access granted for the guest’s role and the relevant scope determine what they can see. Review the role and context boundaries before including an external participant.

Continue on the cRUD Collab website.

See the product in more depth, or ask the team how these concepts map to the way your engineers work.