Skip to Content

An AI assistant for team knowledge and everyday work

We help employees find the right materials and prepare answers, summaries and working drafts. The assistant uses agreed sources within each user's permissions. Its purpose is to reduce repetitive work while preserving human review and accountability.

Discuss a team assistant

What people and teams gain

Find approved answers faster.

The team spends less time looking for the right document version.

A draft instead of manual copying.

The assistant prepares an email or summary for review.

Different roles, different data.

Users see only sources they are allowed to access.

A clear limit on action.

An authorised person approves sending, data changes and professional decisions.

Reading, drafting and sending are different permissions

Reading, drafting and approved actions

Read

Only approved information the employee may access.

Prepare a draft

An answer or draft changes no external record and sends no message.

Approved external action

Separate rights and required employee confirmation come first.

Missing, outdated or forbidden source → clarify

Do not replace a missing fact with an invented answer.

A draft does not send a message or change a record. If a source is missing or outdated, we request clarification. We do not use materials the employee is not permitted to access in the answer.

When the answer exists but is hard to find

An instruction is in another folder, terms have changed in a new edition, and each employee writes a similar answer again. We start with one area where knowledge is genuinely reused and define a useful result: find a source, explain a difference or prepare a draft.

What we set up

A selected knowledge area

We gather current procedures, service descriptions and permitted working materials. We identify owners, versions and information that must be excluded. Connecting the whole company “just in case” is not the first step.

Role-based access

Permissions are checked before material is delivered or passed into a model's context. An employee must not receive someone else's document through a paraphrase, even if the interface does not show the file itself. Departures, role changes and project closure must be reflected in access.

A useful output format

We agree what the employee needs: a short answer with a source, a document comparison, a list of questions or a draft email. Confirmed information is separated from assumptions and missing details. The person can see what must be checked before use.

Review and improvement

We collect real tasks and examples of errors. We check currency, permissions, contradictions and missing information. After launch, feedback helps correct sources and instructions, not merely reword the prompt.

An administrator's result: rule, draft and review

Illustrative record · not a completed client project
Permitted rule
Find the academy's current rule with a link to its source
Draft
Prepare an answer without sending or changing a record
Unknown
Request clarification when the source is absent or outdated
Reviewer action
Check facts and recipient; sending needs separate rights and confirmation
Boundary
Closed materials, revoked access and another organisation's data remain inaccessible

Two practical uses

An academy administrator looks up the rules for rescheduling participation and prepares a reply. The assistant shows the current document and creates a draft; an authorised employee approves any individual exception or refund.

A supplier's manager prepares an equipment response. The assistant finds approved specifications and documents and identifies what is unknown. Compatibility, price and warranty terms do not become automatic decisions by the model.

Reading and drafting are not sending

An employee asks a question. They describe the work task without sharing unnecessary data.

The assistant finds material. It uses a version available to that employee and identifies the source.

It prepares a draft or list of actions. It does not treat an answer as an operation already performed.

A person checks and decides. Only after review do they send or change something in the appropriate system.

The same user may have permission to read a document but not to publish it or send it to an outside recipient. These boundaries are defined explicitly.

An academy administrator looks up the current registration rule for a selected course; a supplier's employee finds an approved equipment specification; a salon administrator finds service information. An answer should refer to the permitted material, its edition and owner, not combine documents from different customers in one search.

pNet defines user groups, sources and the draft format. Sending an email, changing an order or confirming a service remains a separate permitted action. For predictable rules without uncertainty, ordinary automation is simpler than connecting a language model.

Such an assistant complements knowledge and search and Odoo processes but does not replace an employee's responsibility for professional, financial or legal decisions.

Important: Connecting AI to documents does not grant permission to distribute them to all staff or change records without review.

All AI and automation services.

pNet's work and the result for the team

We select users, a task and sources, then check access and the chosen provider's terms. We prepare the assistant, examples and instructions and test the results with staff. We hand over a clear process for updating knowledge and handling errors.

After launch, we help maintain the selected scope, assess usefulness and expand only confirmed scenarios. Model, storage and external-service costs are agreed separately from preparing the solution.

Frequently asked questions

No. We first select a useful area and assess access to existing sources. Migrating the entire archive is not mandatory.

No. Quality depends on the sources, task and model. That is why references, explicit limits, review and a clear refusal when information is insufficient are needed.

Only with appropriate permissions and isolation. A shared assistant must not mix customer contexts or disclose confidential information.

That is a separate scenario. It is useful to test reading and drafts first, then define permissions, approval and controls for external sending.

Find a recurring task for the team

Tell us what employees regularly look for or prepare and where the source information lives. We will select a limited area where the result can be checked.