Organize AI work and review proposals

A conversation contains exchanges. A project groups personal conversations, shared instructions and reference documents around a topic. A proposal is an action prepared by the AI assistant in the chat, such as creating a visualization or updating an asset. You review it before applying or dismissing it.

A proposal can lead to a direct change or send a suggestion for review, depending on the action and your permissions. Sending a suggestion does not apply the underlying change.

An AI project belongs to its author in the organization. It is not a shared collaboration folder. Use the catalog and sharing tools for content intended for colleagues.

Create and resume a project

1. Open the assistant and select Open in full page.
2. In Projects, select New project.
3. Enter a name and Instructions explaining the task and relevant context.
4. Add reference documents if needed, checking the accepted formats below.
5. Select Create and check any file errors before leaving the dialog.
6. Use New conversation in this project to begin work with that project's context.
7. Return through the project and conversation history to continue the work.

You can have up to five projects per organization and six documents per project. When you select more documents than the remaining places, Boldo takes the first files that fit and ignores the others. If one of those uploads fails, do not assume an ignored file replaced it; inspect the list and add the intended file again. Instructions accept up to 5,000 characters. If project creation succeeds but some document uploads fail, retry the failed files in the existing project instead of creating another project.

For example, a project for application rationalization can contain evaluation criteria and reference material. Its instructions can ask the assistant to distinguish known information from assumptions.

Manage project documents

Open the project's menu and choose Configure to change its instructions or manage documents. Save instruction changes with Save.

Document additions and removals take effect as you perform them. Cancel in the configuration dialog does not undo files already added or removed. It can discard unsaved instruction changes while leaving the document list changed.

Read the document count, extraction result and any truncation notice. A document with the same content can be rejected even if its filename differs. At the six-document limit, remove an unnecessary document before adding another.

Removing a document requires confirmation. It removes that source from the project's document collection, but does not rewrite answers already generated from it. Deleting a project removes the project and its documents; its conversations remain, detached from the project.

Attach suitable material

A document attached to a message supplies context for that message. You can later ask the assistant to reread it in the same conversation, naming the file. This uses the extracted text retained for that document, within the limits below. To inspect an image again, attach it again.

A conversation attachment does not become a project document. Project documents can supply relevant excerpts to the project's conversations. The assistant does not necessarily read every project document in full for every answer.

Format	Maximum file size	Use
TXT, MD, CSV, JSON, XML, HTML, YAML	1 MB	Text attachment or project document.
PDF, DOCX, XLSX	10 MB	Text extracted from the document.
PNG, JPEG, WebP, GIF	1 MB	Chat image with a compatible model; not a project document.

A message accepts up to three attachments, including images. The size limits use 1,048,576 bytes for 1 MB and ten times that value for 10 MB.

Older DOC and XLS files, and PPT/PPTX presentations, are not accepted through this document workflow. Convert them to a supported format first.

Text extraction keeps up to 40,000 characters for a message document and 120,000 characters for a project document. Check the retained percentage when a document is truncated. File acceptance alone does not mean all its content is available to the assistant.

PDF and Word extraction does not guarantee that scanned pages, images or layout will be understood. Check the extracted content or the answer's supporting details. A textless scan may need to be converted to readable text first. PDF extraction reads at most the first 500 pages, and can stop earlier at the text limit.

For XLSX documents, the assistant's extraction can use multiple worksheets. This differs from data import, which reads the first worksheet. Attaching a spreadsheet to a conversation does not import its rows into the knowledge base.

Review a proposal

A proposal card should be reviewed as a pending action, not as proof of a completed change. Check the target, previous and proposed values, relationships and warnings.

1. Confirm the organization and the conversation's real data or scenario context.
2. Read the target and changes. For a parallel relationship, verify the intended instance, not just its endpoint names.
3. If Edit in form is offered, open it and correct the proposed values.
4. Use the card's final action, such as Create, Update or Apply changes, only when the result is appropriate.
5. Read the recorded success or error state. If the action submits suggestions, review their status through the suggestion workflow.
6. Open the affected asset or visualization and verify the actual result.

A card that creates one asset also offers its Icon, its Access domains when your plan offers them, and its Owners, which the assistant does not propose. Owners starts with you when you are allowed to assign owners. The domains offered are those where you can create the type, and one is required when you cannot create it without a domain; the card then shows and writes only the properties those domains let you edit. A card that updates one asset offers Owners once you open Edit in form, starting from the current owners. Applying the card changes only the owners you added or removed, so an owner someone else added meanwhile stays.

A card listing several assets has a single Owners and access domains of the new assets block for all its creations. Owners starts with you when you may assign owners for every type created. Access domains, when your plan offers them, lists the domains every created type accepts, and requires one when any of these types does. Each creation writes only the properties those domains let you edit, and its row names the ones they leave out. A batch card does not choose an icon.

Not every proposal has an editable form. A relationship-property proposal offers Update relationship properties, or Suggest the correction when using the suggestion workflow. If the proposed values are wrong, ask for a revised proposal or edit the instance yourself before considering another change.

If you ask the assistant to correct a proposal for the same target, a newer proposal can replace the earlier pending one. Boldo marks the old card as replaced and prevents its application. Review the latest card. This does not undo a change you already applied.

An Open link on a successful relationship proposal can lead to its source asset. Use the relationship inventory to verify the precise instance when necessary.

A stale proposal or changed underlying data may prevent application. Recheck the current values and request a new proposal rather than repeatedly applying an old card. If only some suggestions succeed, inspect each result.

Dismiss or restore a proposal

Use Dismiss proposal when you do not want to act on a pending proposal. Its dismissed state can remain when you reopen the conversation. Restore makes that pending proposal available again.

Restoring a dismissed proposal does not restore old business data. Neither dismissal nor restoration undoes a change already applied. For a correction, edit the affected data or use the applicable scenario workflow.

Likewise, deleting a conversation removes its messages; it is not an undo operation for assets, relationships or visualizations created through it. Check the recorded business result separately from the conversation's presence.