Review, Notifications, and Sharing
AiNecto collaboration uses projects inside a workspace as shared work units. Review documents and Kanban cards through comments, questions, replies, and mentions. Use notifications and your work queue to follow up, then apply reviewed results to the document body.
Collaboration boundaries
- Workspace — groups projects operated together
- Project — holds the actual documents, Kanban, and results
- Folder — organizes project materials
- Document or card — the object where review and discussion occur
Do not assume that every workspace member sees every project and document in the same way. Check the sharing settings and the connected user's actual permissions.
Comments, questions, and replies
Use comments for proposals, factual checks, review feedback, decision rationale, and completion notes. Comments record discussion; the body records the reviewed current standard.
Use a question when an answer is required. A question can move from unanswered to answered and then resolved. A reply alone does not resolve it. Verify the answer, apply any necessary change, and then resolve the question.
Use replies to continue the existing thread. Start a new comment or question for a different topic.
Read the comments and replies on this document and list the feedback that has not been handled.
Find evidence in related project documents that can answer the first question.
Mentions
Mention a person when their review or decision is specifically required. State what to review, which decision is needed, and which document or work item is relevant. Mention only people who need to act.
Work with comments through an Agent
An Agent can read accessible comments on documents and Kanban cards and can add comments, questions, and replies.
Summarize the open questions and review feedback on this document.
Show me a proposed revision first. After I approve it, update the document and leave a comment describing what was handled.
An Agent's revision is not official until a person reviews it.
Notifications and your work
Mentions, replies, question handling, and Kanban activity can create notifications. Ask for a summary across all accessible work or within a workspace or project.
Tell me which AiNecto notifications and work items need my attention.
In [project name] in [workspace name], tell me what I need to review or do.
Reading a notification is not the same as completing the requested action. Open the relevant document, comment, or card and finish the work.
Notifications tell you what happened. Your work queue contains items that still require action. Assigned Kanban work has its own state and acceptance, progress, and review flow. The same event can appear in more than one place.
Activity
Activity shows recent actions by people and Agents in a workspace, project, document, or Kanban card.
Summarize recent comments, questions, and Kanban changes in this project.
Activity is not a guaranteed once-only notification feed. Reopen the original item to determine its current state.
Decide where to add a person
| Collaboration needed | Add the person to |
|---|---|
| Several projects | Workspace |
| One initiative | Project |
| Selected materials only | Folder or document |
Grant the smallest practical scope instead of opening a broad parent scope and attempting to restrict many children.
Manage workspace members
Use workspace sharing or member management in the AiNecto web app. Confirm the person, email, project participation, and required role before adding them.
Changing or removing a workspace member can affect access below it. Review active work, assigned Kanban cards, open questions, and review requests first.
Manage project members
Use project sharing when a person needs only one project. Confirm the workspace and project when names are similar.
After adding someone, confirm they can open the project, see required folders and documents, participate in comments and Kanban, and do not have unnecessary edit rights. Before removing them, hand off assignments and preserve decisions and progress.
Permission roles
- Owner — ownership and full administration
- Admin — member and sharing management
- Editor — create and edit materials; share with Viewers
- Viewer — view and participate through comments
There is no separate Commenter role. A review-only participant can use Viewer access and comments or questions.
If sharing differs between a parent scope and a closer item, confirm the effective permission. The level at which the person was added matters.
Role changes and removals are performed in the AiNecto web app. A connected Agent can invite people to a project when you ask (Team plan, project owner or admin) — see Connect the Agent You Already Use. An Agent works within the connected user's permissions and cannot gain a higher role through a prompt.
Public links
A public link is different from giving a member a role. Before enabling one, remove sensitive information and verify the exact public scope. Disable the link when it is no longer needed.
Do not assume that a project or folder has the same public page behavior as a document. Confirm the result of the current sharing action.
Operating principles
Use workspaces for project boundaries, projects for shared work context, bodies for current standards, comments and questions for review, Kanban for owners and execution state, and notifications or your work queue for follow-up. Agents use these records only within the user's permissions.
A review is complete when the correct project was used, questions have the needed answers, decisions and evidence are reflected in the body, comments record the outcome, required people have reviewed it, follow-up actions are complete, and the next person or Agent can read the current standard.
Continue to Manage Work with Kanban.