Skip to content
Gleyk/Team workflows
Team workflows

Company knowledge becomes common ground.

Give people access to shared knowledge bases and configured assistants. Work from common source material and prepare outputs that colleagues can review.

GleykTeam workflowsA
A

Prepare an onboarding guide using the team’s material.

Shared policiesTraining material

The team’s workspace

Support knowledge base

Read · support team

Team assistant

Sources and instructions configured

Employee guide.docx

Prepared for the team lead’s review

Within configured permissions and connections
Illustrative workflow · sample data
01Team workflows

Shared knowledge and assistants. Access on your terms.

Give your team access to the relevant knowledge base and a configured assistant. People work from common material and hand documents and findings to the responsible reviewers.

GleykTeam workflowsA
A

Prepare an onboarding guide using the team’s material.

Shared policiesTraining material

The team’s workspace

Support knowledge base

Read · support team

Team assistant

Sources and instructions configured

Employee guide.docx

Prepared for the team lead’s review

Within configured permissions and connections
Illustrative workflow · sample data
02Answers with evidence

An answer, right next to the evidence.

Nobody needs to remember a file name. Ask a question, read an explanation and inspect the relevant policy passage. Connected knowledge becomes a tool for everyday work.

GleykAnswers with evidenceA
A

How do I get a new server purchase approved?

Purchasing policy.pdfIT standards.docx
Answer from your knowledge

First agree technical requirements with IT, then send the request to the budget owner.

1. Technical review

Check hardware requirements and compatibility. [1]

2. Budget approval

Attach a business case and a supplier proposal. [2]

Section 4.2 · Purchasing policy
“Equipment requests are reviewed by the IT lead and the budget owner.”
Illustrative workflow · sample data
03Create and refine

From meeting notes to a document ready for review.

Give your assistant source files and a brief. Create a Word document, refine the wording in conversation and revisit previous versions. Preview the result before handing it to a colleague.

GleykCreate and refineA
A

Prepare a proposal from the meeting notes. Include pilot stages and acceptance criteria.

Customer meeting.txtProposal template.docx
DOCXVersion 2 · preview
PROJECT / PROPOSAL

Pilot proposal

01 / Project objective

Evaluate search and answer preparation using the support team’s material.

02 / Pilot stages

Connect sources → configure the assistant → evaluate real questions.

03 / Acceptance criteria

Answers include sources. Access boundaries are checked. The process owner reviews the outcome.

Prepared from the meeting notes01
Acceptance criteria added. Previous version retained.
Illustrative workflow · sample data
The path to an outcome

A clear sequence of work.

Define sources, permissions and review checkpoints before the workflow runs.

  1. 01

    Gather team material

  2. 02

    Configure knowledge access

  3. 03

    Prepare an output with the assistant

  4. 04

    Hand it to a colleague for review

The outcome

For example: an onboarding guide based on shared policies, prepared for a team lead to review.

Deployment considerations

Configured for your data and rules.

Knowledge base and assistant access are configured separately. Documents and findings follow your team’s review process.

Explore controls
Start with your work

Bring us a workflow. Let’s see what AI can do.

Tell us about your team’s task and systems. Together we’ll scope a pilot and decide how to evaluate the result.