Conductor User Management API
You manage accounts and roles through the conductor user management api using standard web calls. This tool lets you create users, set up groups, and assign workflow rights. Most teams link this system to their central login provider. Then they map job titles to broad workflow groups. Still, broad roles often give developers too much power in live systems. A user who needs to read one log might gain full write rights. How the conductor user management api works The conductor user management a
API Key Management + User Provisioning (SCIM): the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
You manage accounts and roles through the conductor user management api using standard web calls. This tool lets you create users, set up groups, and assign workflow rights. Most teams link this system to their central login provider. Then they map job titles to broad workflow groups. Still, broad roles often give developers too much power in live systems. A user who needs to read one log might gain full write rights.
How the conductor user management api works
The conductor user management api controls who can view, run, and change workflows. Admins send web requests to add new team members or service accounts. Each account gets a role or joins a group with set rules. These rules point to specific workflow names or task queues.
Service accounts use key pairs to log in and run tasks. Human users log in with their normal work email and password. When a request hits the server, the system checks the user token. It reads the group rules and allows or blocks the call. You can also update or delete accounts when people leave the team.
Managing groups and service keys at scale
As teams grow, managing single accounts by hand takes too much time. Platform teams use groups to bundle permissions for different squads. For example, a billing squad gets rights to run payment workflows. A data squad gets rights to read analytics tasks and logs.
Apps and scripts also need keys to start workflows and poll tasks. You create these bot accounts through the same user API endpoints. Each bot gets its own key to talk to the engine. Teams must rotate these keys often to keep the system safe. If a key leaks, an attacker can run tasks or read data.
What native roles solve and where gaps remain
Native roles do a good job of sorting users into basic buckets. They stop guests from deleting workflows or changing system rules. They also help admins track which groups own which workflows. For simple apps, these built-in checks work well enough.
API Key Management + User Provisioning (SCIM): architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Still, native setup only checks who logs in at the start. It does not inspect what each request or payload does in flight. A user with run rights can pass bad data into a workflow. Task outputs can also return sensitive fields like emails or card numbers. Native roles cannot rewrite matched fields in results before users see them. Teams also struggle to approve single high-risk actions without granting permanent admin rights.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev sits inline in the protocol beside each supported service as an open-source proxy, a sidecar for your database or API. For every query or command an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human approval.
First, hoop.dev guardrails block banned queries before they run or hold risky ones for review, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
How do I remove a user with the API?
You send a delete request to the user endpoint with the account ID. This action revokes their active tokens and blocks future calls right away.
Can service accounts share the same role as human users?
Yes, both account types can use the same roles and permission rules. Still, it is safer to give bots narrow rules for specific tasks.
How do I stop workflows from leaking private data in task logs?
Native roles cannot filter payload fields inside task logs on the fly. You need data masking that rewrites matched fields like phone numbers in results.
Teams that document these role rules and review logs each month catch config drift early. Clear ownership for each role keeps live systems simple to run and easy to audit across the whole team.