# Manage Users

> >-

- **Type:** Skill
- **Install:** `agentstack add skill-harness-harness-skills-manage-users`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [harness](https://agentstack.voostack.com/s/harness)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [harness](https://github.com/harness)
- **Source:** https://github.com/harness/harness-skills/tree/main/skills/manage-users
- **Website:** https://developer.harness.io/docs/platform/harness-ai/harness-skills/

## Install

```sh
agentstack add skill-harness-harness-skills-manage-users
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# 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: ""
```

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: ""
```

### Step 3: Manage User Groups

List groups:

```
Call MCP tool: harness_list
Parameters:
  resource_type: "user_group"
  org_id: ""
  project_id: ""
  search_term: ""
```

Get group details:

```
Call MCP tool: harness_get
Parameters:
  resource_type: "user_group"
  resource_id: ""
  org_id: ""
  project_id: ""
```

Create a group:

```
Call MCP tool: harness_create
Parameters:
  resource_type: "user_group"
  org_id: ""
  project_id: ""
  body:
    identifier: "backend_team"
    name: "Backend Team"
    description: "Backend engineering team"
    users:
      - ""
      - ""
```

Delete a group:

```
Call MCP tool: harness_delete
Parameters:
  resource_type: "user_group"
  resource_id: ""
  org_id: ""
  project_id: ""
```

### Step 4: Manage Service Accounts

List service accounts:

```
Call MCP tool: harness_list
Parameters:
  resource_type: "service_account"
  org_id: ""
  project_id: ""
```

Create a service account:

```
Call MCP tool: harness_create
Parameters:
  resource_type: "service_account"
  org_id: ""
  project_id: ""
  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: ""
  org_id: ""
  project_id: ""
```

### 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:

1. `/manage-users` -- Create the user group or service account
2. `/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-roles` to assign a role to the service account
- Generate an API key for the service account via the Harness UI

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [harness](https://github.com/harness)
- **Source:** [harness/harness-skills](https://github.com/harness/harness-skills)
- **License:** Apache-2.0
- **Homepage:** https://developer.harness.io/docs/platform/harness-ai/harness-skills/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-harness-harness-skills-manage-users
- Seller: https://agentstack.voostack.com/s/harness
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.