BasisAssistant + Projects & Tasks
Start with a conversation. Continue the work in BasisPanel.
When a request comes up in a conversation, the next step does not have to depend on notes or manual follow-up. BasisAssistant can collect the required information according to a defined structure and turn the request into one or more tasks in BasisPanel.
The task can be assigned within the organization’s approved roles and permissions, then tracked as work progresses. Project Managers and Operations Managers can also review overall project status, overdue tasks, tasks approaching their deadline, unassigned work, and items that need attention through a concise management summary.
This integration is designed for requests that begin in a conversation but need to continue as specific, trackable work.
The primary ready destination is Projects & Tasks in BasisPanel. BasisAssistant can collect the required information according to the structure defined for the use case, create a task, and move the next step into BasisPanel. This keeps the request connected to a clear project and task workflow instead of leaving follow-up outside the working system.
The integration is currently available as an Add-on. It is not part of the base-plan capability set and can be enabled on eligible plans according to the applicable commercial terms.
A clear path from conversation to action
The information stored in each task can be structured around the needs of the organization. The same fixed fields do not have to be collected in every scenario. The defined schema determines what information is extracted from the conversation and recorded in Projects & Tasks in BasisPanel.
The user describes the required action or need in the conversation.
BasisAssistant identifies the intent and extracts the information required by the defined schema.
A request can create one task or, when the scenario is designed for it, several independent tasks.
The assistant can assign the responsible person according to the project structure, defined roles, and business rules, provided the required permission exists.
The task is created in Projects & Tasks so the work can continue in a trackable operational context.
BasisAssistant can review project status and surface overdue tasks, tasks approaching their deadline, unassigned work, or items that need attention in a management summary.
Projects & Tasks in BasisPanel

Every action remains subject to user permissions and organizational policy
Within Projects & Tasks in BasisPanel, BasisAssistant can perform the approved task and project actions through the API. Each action is executed only within the user’s permitted Role, project Scope, and configured Policy.
Your rules define what the assistant can decide and what it can record
BasisAssistant can record or update a deadline and priority, but it does not currently determine those values autonomously. The value must come from an explicit user instruction, a defined schema, or a clear system rule.
Responsibility can be assigned according to the project structure, roles, and configured rules, but only when the user and assistant are operating within their authorized scope.
This separation allows AI to support execution without automatically taking management decisions that have not been defined by the organization.
Access, approval, and activity history are part of the action flow
BasisAssistant can only view or change tasks and projects that the current user is allowed to access. Role-Based Access Control, project Scope, and organizational policies define that boundary.
Each action can be configured in one of three ways: direct execution, execution after human approval, or suggestion only. Organizations can apply approval policies to sensitive operations according to their own requirements.
Actions performed by the assistant and their related changes are recorded in the Activity/Audit Log. The change history of each task can also be reviewed, giving the organization a traceable record of what happened and how the action was handled.

Third-party connections depend on the destination API and individual integration review
The ready Integration covered by this page connects BasisAssistant with Projects & Tasks in BasisPanel. Third-party project-management systems are assessed individually rather than presented as pre-connected integrations.
If another system provides a suitable API, the connection can be assessed as an Integration project. Data mapping and supported actions are then designed around the destination API. An action available in BasisPanel should therefore not be assumed to be available in every external system.
For a third-party Integration, appropriate API access and credentials or permissions are required. Whether a Webhook or administrative access is also needed depends on the design of that Integration. The API & Webhooks page covers the approved ecosystem path for custom system connections.
Project structure and access rules should be defined before the Integration is activated
For the internal Integration, BasisAssistant and Projects & Tasks must be active. The project, Roles, access structure, and required schemas also need to be defined before the use case is configured.
The Manzoomeh team configures the Integration in cooperation with the customer’s system owner or manager. For an external Integration, the technical team responsible for the destination system must also participate where required.
Support for the internal connection is handled by the Manzoomeh BasisPanel team. For external Integrations, support responsibilities are defined according to the boundary between the Manzoomeh Integration and the destination system owner.
The Integration works within a defined scope and controlled access model
The Integration has a defined operating scope. Some behaviors are intentionally outside the current generally available capability set.
Yes. The task schema can be configured around the organization’s needs and can define which information should be extracted from the conversation and recorded in the task.
Yes. A single conversation or request can create multiple independent tasks when the defined Intent and Schema are designed for that scenario.
No. Recording and changing deadlines and priorities is supported, but AI does not currently determine those values autonomously. They must come from an explicit user instruction, a defined Schema, or a clear system rule.
Yes. Responsibility can be assigned according to the project structure, roles, and defined rules, provided the user and assistant have the required permission.
No. BasisAssistant can only view or change tasks and projects that the current user is permitted to access under the applicable RBAC and project Scope.
Yes. An action can be configured for direct execution, human approval before execution, or suggestion-only behavior. The organization can define the appropriate Policy for different actions.
The action is not executed, and the user is informed that permission is missing or the operation cannot be completed. The request is not currently escalated automatically to another authorized person.
Yes. Assistant actions and related changes are recorded in the Activity/Audit Log. The record includes at least the requesting user, time, action type, previous and new value or status, approver when applicable, and execution result. The change history of each task can also be reviewed.
The ready Integration on this page is with Projects & Tasks in BasisPanel. A third-party system can be assessed for Integration when it provides a suitable API. The actions that can be supported depend on the destination API and the mapping defined for that Integration project.
Yes. The BasisAssistant Integration with Projects & Tasks in BasisPanel is currently available as an Add-on. A working demo of the Integration is also available.