On the page where work already happens
On an employee profile, ask “What are the promotion rules?” The assistant answers from policy — no extra site, no retelling. You can also add a specialist module to the workbench.
Embed first on the page where work happens, then connect knowledge and permissions by workspace. Chat, skills, plugin apps, and workflows stay inside the same bounds.

On an employee profile, ask “What are the promotion rules?” The assistant answers from policy — no extra site, no retelling. You can also add a specialist module to the workbench.
Give HR its own workspace. Put policy in knowledge documents so assistants in that space share it. Personal memory stays private by default.
Ask the help assistant “How do I create a workspace?” After you pick one, use a work assistant for real tasks. Mark what matters with “remember”.
Give HR a consistent role. Turn “check remaining annual leave” into a reusable skill. You can also improve skills and app UI through conversation.
HR, compliance, email, warehouse, and cameras show up as one family of apps. Tell the app assistant “list departments”, “write a meeting follow-up”, or “who clocked in today”; it acts within your permissions. If people still work in a legacy system, embed the assistant there instead.
Create an approval, onboarding, or on-site check from a template. Wire the steps on a canvas; colleagues handle todos on the web or a phone. Completing an HR move can start a flow automatically; publish to the app desktop when you want an icon.