Users for your app are primarily created using the [Human Connect](🔗) flow. Once you have users you can manage them with either the Developer Portal or the Application API.
Both methods are described in detail below.
## Managing Users via the Developer Portal
One way to manage users is via the [Developer Portal](🔗). From your app homepage, click the 'Users' section to see a list of your app's users.

From this page, you can see the `humanId
`, `ExternalId
`, `accessToken
`, and `publicToken
` for a user.
Under the Options column, you can do two things:
See or connect data sources for a user (blue bar icon)
Delete that user (red X icon)
# Managing User Data Sources
By clicking on the user's humanId, you will be able to see what data sources that user has connected. Additionally, there will be a Human Connect button preconfigured for the specific user to allow you to connect directly in the Developer Portal.

# Viewing User Data
By clicking any of the available data sources for a user, you can also view a graphic representation of the current data.

## Manage Users via the Application API
Another way to manage users is via the [Application API](🔗)'s `/users
` endpoint:
# Retrieve a Single User
You can retrieve a single app user by using this URL:
Replace the `{clientId}
` with the Client ID for your application, and `{humanId}
` with the assigned Id for the specific user.
Using curl command line:
Example User Payload
appId == clientId
The returned payload will return the attribute "appId". `
appId
` is equivalent to `clientId
` and is a prior naming convention that will be changed in the next major API release.
# Retrieve All Users
To retrieve all users, you can just query the `/users
` endpoint itself:
# Delete a User
You can delete a user by using this URL:
Replace the `{clientId}
` with the Client ID for your application, and `{humanId}
` with the assigned Id.
# Example
The response code for this is `204
`
It is only recommended that you only delete a user when that user account is also deleted on your system. This will avoid potential Connect errors later on.