Canon Scope and Permissions

2 min read

Project scope means a document applies to this product only. Workspace scope means it applies to every project in the workspace.

The Scope column on the Canon page shows which one each document is.

Project Documents

Documents you add on a project’s Canon page are project documents. The AI uses them in that project only.

This is the right choice for most documents: the product’s PRD, feature specs, API contracts, and acceptance and exit criteria.

Workspace Documents

A workspace document is used in every project in the workspace. It suits material every product must follow:

Company test strategy and QA conventions
Accessibility, security or compliance standards
Regulations every product must meet
Shared terminology

Workspace documents appear in every project’s Canon list with Workspace in the Scope column. They can’t be moved into a project’s folders.

How the Two Combine

Inside a project, the AI Test Case Generator, release readiness, Atlas and Oracle use both that project’s documents and the workspace documents. A question about login can use the login spec and the company accessibility standard.

Permissions

Canon has four permissions, set per role like every other area. See Roles overview.

Permission	Lets you	Default roles that have it
View	See Canon documents and open the documents the AI cites	Workspace Manager, Project Manager, Project Coordinator, Project Member
Create	Add documents and create folders	Workspace Manager, Project Manager, Project Coordinator
Update	Re-index, rename and move documents; rename and move folders	Workspace Manager, Project Manager, Project Coordinator
Delete	Remove documents and delete folders	Workspace Manager, Project Manager

Adding, re-indexing and removing workspace-level documents is limited to Workspace Managers.

Deleting a Project

Deleting a project also removes its Canon documents. Workspace documents are not affected.