Ask
Ask questions across approved company knowledge and see the answer in the same work thread.
Product
From question to useful outcome.
Glaux helps employees ask, research, write, analyze, browse, and create artifacts with approved company knowledge and approved tools. When work needs access or approval, the request stays in the task.
Ask Glaux
Compare the top customer requests with the approved roadmap and draft the launch brief.
Created artifactQ3 launch brief
Source notes, open decisions, and approval-ready next steps.
What employees can do.
The work starts like a normal request and ends with a brief, plan, table, or next step someone can use.
Research
Collect source notes, compare options, and keep open questions visible for the team.
Write
Draft briefs, replies, summaries, and handoffs from the context your team has approved.
Analyze
Turn notes, documents, and work history into clear patterns without hiding the source trail.
Browse
Use approved browsing paths when the task needs fresh external context.
Create artifacts
Leave with the memo, plan, table, or checklist the work actually needs.
Access and approval
Ask without leaving the work.
If a task needs a new tool, source, or sensitive action, Glaux keeps the request attached to the work so the approver sees the reason and the user sees what happens next.
Approval requested
Send external customer summary
Reason: share the final launch brief with the account team after review.
1. Request stays with the task2. Approver reviews the reason3. Work continues or stops with an explanation
Approved tools, skills, and automations.
Teams can make useful capabilities available without implying every tool is open to every person.
Approved tools
Approved before useUse the tools an administrator has approved for the workspace and task.
Enterprise SkillHub
PreviewShare trusted ways of working.
Enterprise connections
PreviewConnect the tools your company depends on.
Automations
Governed workflowRun repeated work with the same boundaries as one-off requests.
What administrators can manage.
Administrators get a plain operating view of who can use what, how work is changing, and where attention is needed.
PeopleGroupsToolsModelsSkillsUsageActivity
Recent decisions in everyday language.
See what moved ahead, what needs a person, and what stopped before action.
continued
Renewal-risk brief
The request matched the rules, so work carried on.
approval requested
External customer email
The next step needs the right person to approve it first.
stopped
Unapproved data export
The request crossed a boundary and was blocked before action.
needs attention
Automation source changed
A person should review the change before the workflow continues.
For evaluators
Technical detail is available, not the main story.
Security and platform reviewers can go deeper into controls and evidence when they need it. The main flow stays focused on what employees and administrators can do.