Planning documents built to your own standards

Documents

Your sections, in your order, in every planning document

Most organisations already have a house style for these documents. A template sets the sections once and every new document follows them.

• Set it for the workspace under Settings, then Documents. Workspace administrators can edit; everyone else can read
• Override it for one project under that project’s Settings, then Documents. The project’s SDM or architect can do this
• Each section can carry an intent, points it must cover, standing text to reproduce word for word, and whether it needs a diagram. Sections can be locked
• Every document shows the template that produced it, and a conversation keeps the template it started with
• A template that has produced a document cannot be edited or deleted. To change it, clone it, adjust the copy and activate that

Two honest limits. “Must cover” is an instruction to Conductor, not a check, so review still matters. And with no template set, documents keep Konductro’s built-in structure exactly as before. Technical analysis runs in your AI coding tool, so update your Konductro plugin and re-run its setup: when a template applies, older plugins are refused with instructions.

Teams and access

Inside a project, the project’s team decides

What you could do in a project used to depend partly on your account type. Now every action inside a project is decided by your role on that project’s team.

• SDMs run the project: approvals, assignment and the sprint lifecycle. SDMs and architects shape the plan. Developers and testers work the items
• Administrator is a separate tag on a user, covering the workspace rather than the work inside each project
• Reviewer is a project role switched on per person on the Team page, and shows on story and ticket detail
• The Stakeholder and Client project roles are retired. Anyone who held only those is now a Viewer, who can still read, comment and record approvals
• A refusal names the role you need and who can give it to you

Workspace administrators need to be on a project’s team to work in it. Ask the project’s SDM, or add yourself from the Team page.

Notifications

Fewer emails, if you want them

• Choose Immediately, Hourly digest or Daily digest in your Profile’s email notification settings
• The daily digest arrives at about 07:00 SAST
• Urgent emails, such as billing and account security, always arrive immediately
• Everyone starts on Immediately

Delivery

QA waits for the build to be there

• Story promotion gates: name a QA and a UAT environment under Settings, then Environments, and a story moves into QA or UAT only once a deployment there is recorded. Both start on None
• In Sprint is no longer a status; the sprint itself shows it. Items that showed In Sprint now show Approved and stay in their sprint
• Request a refresh of a technical analysis from the phase workspace, with a message and an assignee. Earlier versions stay in the document’s history
• Tasks from a decomposition are assigned to the developer who decomposed the story

Quality of life

Smaller things, and some fixes

• See who created a work item on its detail and in the Work Items list
• Ticket descriptions and acceptance criteria render formatting, and the Type field shows story, task or bug
• Command Centre attention cards show what is behind each count, and count only active projects
• Edit an environment in place in project settings
• Bulk assign moves tickets to Assigned, the same as assigning one at a time
• Dropdown and layout fixes across the app