manage-users
Skill2 starsChanged 7 months agoApache-2.0Archived repositoryView on GitHub
Manage Harness users, user groups, and service accounts via MCP. List and search users, create and manage user groups for team-based access, create service accounts for API automation, and view available permissions. Use when asked to list users, create a user group, manage service accounts, check who has access, or set up team permissions. Do NOT use for role assignments or resource groups (use manage-roles instead). Trigger phrases: list users, user group, service account, who has access, team permissions, add user to group, create service account.
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 108
Create a service account:
- Distinctive: line 123
Delete a service account:
- Distinctive: line 171
Verify user email addresses and group identifiers before making changes.
- Distinctive: line 184
Use user groups and service accounts for programmatic access
- Very specific: line 188
Use /manage-roles to assign a role to the service account
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Manage Users
Manage users, user groups, and service accounts via MCP.
Instructions
Step 1: List Users
Call MCP tool: harness_list
Parameters:
resource_type: "user"
search_term: "<name or email>"Users are account-scoped. Use search_term to filter by name or email.
Step 2: Get User Details
Call MCP tool: harness_get
Parameters:
resource_type: "user"
resource_id: "<user_id>"Step 3: Manage User Groups
List groups:
Call MCP tool: harness_list
Parameters:
resource_type: "user_group"
org_id: "<organization>"
project_id: "<project>"
search_term: "<group name>"Get group details:
Call MCP tool: harness_get
Parameters:
resource_type: "user_group"
resource_id: "<group_identifier>"
org_id: "<organization>"
project_id: "<project>"Create a group:
Call MCP tool: harness_create
Parameters:
resource_type: "user_group"
org_id: "<organization>"
project_id: "<project>"
body:
identifier: "backend_team"
name: "Backend Team"
description: "Backend engineering team"
users:
- "<user_id_1>"
- "<user_id_2>"Delete a group:
Call MCP tool: harness_delete
Parameters:
resource_type: "user_group"
resource_id: "<group_identifier>"
org_id: "<organization>"
project_id: "<project>"Step 4: Manage Service Accounts
List service accounts:
Call MCP tool: harness_list
Parameters:
resource_type: "service_account"
org_id: "<organization>"
project_id: "<project>"Create a service account:
Call MCP tool: harness_create
Parameters:
resource_type: "service_account"
org_id: "<organization>"
project_id: "<project>"
body:
identifier: "ci_bot"
name: "CI Bot"
description: "Service account for CI pipeline automation"
email: "ci-bot@harness.io"Delete a service account:
Call MCP tool: harness_delete
Parameters:
resource_type: "service_account"
resource_id: "<service_account_identifier>"
org_id: "<organization>"
project_id: "<project>"Step 5: List Available Permissions
Call MCP tool: harness_list
Parameters:
resource_type: "permission"This returns all platform permissions. Use this to understand what permissions can be assigned via roles.
Resource Types
| Resource Type | Scope | Operations | Description |
user | Account | list, get | Platform users (read-only) |
user_group | Project | list, get, create, delete | User groups for RBAC |
service_account | Project | list, get, create, delete | API automation accounts |
permission | Account | list | Available permissions (read-only) |
Relationship to /manage-roles
This skill manages principals (users, groups, service accounts). Use /manage-roles to assign roles and resource groups to these principals:
/manage-users-- Create the user group or service account/manage-roles-- Assign a role + resource group to that principal
Examples
- "List all users in the account" -- List users with no filter
- "Find user john.doe" -- List users with search_term "john.doe"
- "Create a user group for the platform team" -- Create user_group with member user IDs
- "Create a service account for CI automation" -- Create service_account
- "What permissions are available?" -- List permissions
- "Delete the old test-bot service account" -- Delete service_account
Performance Notes
- Verify user email addresses and group identifiers before making changes.
- List existing groups and service accounts before creating to avoid duplicates.
- For service accounts, confirm the token expiry and scope match the intended usage.
Troubleshooting
User Not Found
- Users are account-scoped -- no org/project needed
- Try searching by email address instead of display name
- User must be invited to the account before they appear
Cannot Create User
- Users cannot be created via API -- they must be invited through the Harness UI or SCIM provisioning
- Use user groups and service accounts for programmatic access
Service Account Has No Access
- Creating a service account alone does not grant permissions
- Use
/manage-rolesto assign a role to the service account - Generate an API key for the service account via the Harness UI
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- harness/harness-skills★ 12799% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/harness.mdcCursor rule
- analyze-costsSkill
- audit-reportSkill
- chaos-experimentSkill
- create-agentSkill
- create-agent-templateSkill
- create-connectorSkill
- create-environmentSkill
- create-infrastructureSkill
- create-pipelineSkill
- create-pipeline-v1Skill
- create-policySkill
- create-secretSkill
- create-serviceSkill
- create-templateSkill
- create-triggerSkill
- debug-pipelineSkill
- dora-metricsSkill
- gitops-statusSkill
- manage-delegatesSkill
- manage-feature-flagsSkill
- manage-rolesSkill
- migrate-pipelineSkill
- run-pipelineSkill
- scorecard-reviewSkill
- security-reportSkill
- template-usageSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

