Auggy

Every user gets a separate chat session with its own memory. A follow-up like "move it to Friday" resolves against that user's earlier messages, and conversations from different users never mix.

Every user gets a separate chat session with its own memory. A follow-up like "move it to Friday" resolves against that user's earlier messages, and conversations from different users never mix.

LangGraph orchestrates the workflow. It coordinates the specialist agents and carries each task across the connected systems, using the session memory so follow-ups make sense.

Role-based access control sits inside the orchestration. Before an agent runs, the user's role is checked against it. If the role is not allowed, the request stops here and an error comes back.

Access denied. Generating an invoice is HR work, so for an employee the request stops at the role check and an error comes back instead of reaching the agent.

Creates and looks up Jira tickets on the user's behalf.

Finds free time and books meetings on Google Calendar.

Drafts approval emails and other messages in Gmail.

Handles the employee side of PaddyField, such as logging time entries.

Answers questions with RAG over internal company documents, which live in Vertex AI Search, Google Cloud's search platform.

The HR agent covers the HR side of the workplace tools, such as invoice management and other HR work. It is restricted, so only the HR role gets through the role check.

Retrieval uses the document metadata. The user's country filters which documents are searched, so a leave-policy question returns the policy that applies to them.

Vertex AI Search is the Google Cloud platform where the internal documents are stored and searched.

The retrieved passages ground the generated answer, which returns through the orchestrator into the same user session.

Signed in as an employee: every agent opens except HR, which stays locked behind the role check.

Signed in as HR: the role check lets this user through to the HR agent as well.