Department support (internal chat)
Give employees a simple “ask your workspace” page they reach from your intranet, SharePoint or Teams — answers from your own documents, with sources.
What it is
Department support is a focused, sign-in-protected page —
/team_chat.php — where employees pick a department (IT, HR, Legal…) and ask a
question. Answers come only from that department's documents, with citations, and the
assistant says “I don't know” rather than guessing. Employees reach it from a button
on your internal portals; there's nothing to install.
It reuses everything the rest of the workspace already does — Microsoft sign-in, tenant isolation, project access controls and the same grounded answering engine. The only new idea is which agents an admin chooses to publish to all employees.
A “department” is just an agent. Each department is an existing agent scoped to that department's project(s). Publishing a department = ticking that agent as visible to staff. So set up your projects and agents first (see Agents and Projects & uploads), then publish them here.
Who can do what
| Action | Admin | Member |
|---|---|---|
| Open the “Ask your workspace” page and ask published departments | ✓ | ✓ |
| See the “Manage departments” panel | ✓ | — |
| Publish / unpublish a department (mark an agent staff-visible) | ✓ | — |
| Copy a department's portal link | ✓ | — |
Members only ever see and query the departments an admin has published. A member cannot reach an unpublished agent here, even with a direct link — the page refuses it.
Publish a department (admin)
- Go to Settings → “Department support (internal chat)” and click
Manage departments & get links →. (Or open
/team_chat.phpdirectly.) - Expand Manage departments at the bottom of the page.
- Tick each agent you want employees to use. It's published immediately and shows a green Live badge.
- Click Copy link next to a live department to copy its portal URL, e.g.
https://ask.olyteck.com/team_chat.php?dept=12. - Untick to unpublish at any time.
Only publish all-staff knowledge. Anyone signed in to your workspace can read a published department's documents through this page. Keep sensitive or team-only content (individual HR cases, salaries, restricted policies) in the normal in-app chat with project access controls — don't publish it as a department.
Put it on your intranet, SharePoint or Teams
Add a button that links to the department's URL. Paste this into a page or web part and
replace the dept id and label:
<a href="https://ask.olyteck.com/team_chat.php?dept=12"
style="display:inline-block;background:#4262ff;color:#fff;text-decoration:none;
padding:10px 16px;border-radius:10px;font-weight:600">
Ask the IT department →
</a>
When an employee clicks it, they sign in once with Microsoft (if they aren't already), land
on the page with the right department pre-selected, and start asking. The dept
value can be the agent id (from the Copy link button) or its name, e.g.
?dept=IT.
What an answer looks like
- A grounded reply drawn only from that department's documents.
- A Source: line listing the documents it used.
- An honest “I don't know” when the documents don't cover the question — so employees never get a confident wrong answer.
Good practices
- One clear department per agent. Name agents the way employees think — “IT”, “HR”, “Facilities” — so the picker and deep-links read naturally.
- Keep each department's project well-curated. Answer quality is the quality of the documents behind it. Remove stale policies; the assistant can't out-think its sources.
- Start small. Publish one or two departments, share the portal button, and expand once people are using it.
Security in short: the management panel is admin-only (hidden for members and enforced on the server); only published departments answer; every query runs under the employee's own signed-in session and your tenant's isolation; and answers stay grounded and cited. Sensitive content belongs in the normal chat with project roles, not here.