· 1 min read · agents · google adk
An RBAC agent for developer onboarding
New developers kept interrupting senior ones with "who can access this dataset?". A Google ADK agent now answers first.
In the first weeks after onboarding, new developers kept asking senior programmers the same kind of question: which roles have access to this dataset? or why can’t my job run in this environment? Every one of those questions was a context switch for someone experienced, and a wait for someone new.
So we built an RBAC agent as the first line of answer. Instead of waiting for a person in chat, a new team member asks in plain language and gets an explanation of the roles, the permissions, and the access logic behind them, immediately.
It is built on Google ADK. The agent holds the role and permission model as structured context and is instructed to explain why an access decision comes out the way it does, not only what the answer is, so the person asking learns the model instead of learning to ask again.
- Demo: video walkthrough
- Source: github.com/zhuhongd/adk_agent_rbac
This was my first agent in production use, and the pattern it taught me carried straight into the platform I run now: keep the authoritative data structured and outside the model, let the model do the explaining.