Managing an organization's user directory can feel like a never-ending cycle of manual tasks. Onboarding new hires, updating roles, and offboarding departing employees involves a cascade of clicks, tickets, and cross-departmental communication. It's slow, prone to human error, and a significant drain on your most valuable resource: your team's time.
At directory.do, we believe there's a better way. Our philosophy is simple: manage your organizational directory as code. By defining your org chart, teams, and user roles in simple configuration files, you unlock a new level of automation and consistency.
But how does a change in a code file translate into a new user getting access to Slack, Google Workspace, and their specific GitHub repositories? The magic lies in our agentic workflows. Meet the autonomous agents working tirelessly behind the scenes to make it all happen.
Think beyond traditional scripts. A script is a rigid set of instructions: "Do A, then B, then C." If step B fails, the whole process often grinds to a halt.
An agent, on the other hand, is an autonomous program given a goal. Instead of telling it how to do something, you tell it what you want to achieve.
Goal: "Onboard Charlie Brown as a Senior Software Engineer."
An agent then intelligently determines the necessary steps to achieve that goal. It can handle errors, retry operations, and interact with multiple systems to ensure the final state matches your intent. At directory.do, our agents are specialists, trained to be experts in identity management and directory synchronization.
To bring this concept to life, let's introduce the core agents that power your directory.do automation.
When a new user is added to your directory code, the Provisioner agent springs into action. Its sole purpose is to get new hires set up correctly from day one, without any manual intervention.
Roles and responsibilities change. The Access Guardian ensures that a user's permissions always reflect their current position in the company, enforcing the principle of least privilege automatically.
Improper offboarding is one of the biggest security risks for any company. The Offboarder agent ensures that when an employee leaves, their access is terminated completely and systematically.
Let's see how this plays out with a practical example. Diana Prince has been promoted to Engineering Manager, reporting to Alice Johnson.
Step 1: The Commit
A manager updates the organization's configuration file, changing Diana's role and placing her under Alice in the hierarchy. This change is committed to your Git repository.
{
"user": {
"id": "usr_1a2b3c4d5e6f7g8h",
"name": "Alice Johnson",
"title": "Director of Engineering",
"direct_reports": [
{
"id": "usr_z9y8x7w6v5u4t3s2",
"name": "Diana Prince",
"email": "diana.p@example.com",
"title": "Engineering Manager" // <-- Title Updated
}
],
"groups": [
"engineering-leads",
"all-employees"
]
}
}
Step 2: The Trigger
directory.do detects the change in your version-controlled directory, which serves as the "source of truth."
Step 3: The Agentic Workflow
All of this happens in seconds, triggered by a single git push.
Using an agent-driven platform like directory.do goes beyond simple automation. It provides:
Stop managing users. Start defining your organization. Let our agents handle the rest.
Ready to put your directory management on autopilot? Explore our user management API and see how agentic workflows can transform your IT and HR operations.