Users

Portal accounts live in Configuration → Users. That is where administrators create people, assign workspaces, block or delete accounts, and sync developers with Apigee. Teams do not create portal users.

Where to find it

Open Configuration → Users. The section is visible to users with the Read Users permission (assigned to Administrator by default).

The screen has four tabs: Users List, Roles Management, Permissions, and User Fields (User Fields appears only with Manage User Fields). This page covers accounts. See Role-Based Access for roles and permissions, Custom User Fields for profile fields, and Teams for adding existing users to a team.

How accounts are created

A person must already have a portal account before they can be invited to a team. Accounts come from one of these paths:

Add User on Users List — an administrator creates the account. Requires Create Users.
Self-registration — when Configuration → General allows it (Open or Domain Restricted). Invite Only and SSO only block public signup. See Portal Setup.
Sync Developers — missing portal users are created from developers already in the selected Apigee organization.

Invite Member on a team’s Members tab does not create an account. It looks up an existing user by email. If nobody in the portal has that address, the invite fails with “User not found. Only existing users can be invited to teams.”

Users List

The table shows name, email, portal role, status, workspaces, and created date (in the portal timezone). Search by name or email, filter by workspace, and refresh the list.

Status — Active or Blocked. With Update Users, you can change status from the table without opening the editor.
Workspaces — the Apigee organizations the user is assigned to. A user with none cannot build apps or teams in an org. Assign them when you add or edit the user.
Edit and delete appear when you have Update Users and Delete Users.

Add User

Click Add User. The modal is titled Add User — Create a new user account.

First name and Last name — required.
Email — required. Must be lowercase and a valid address. This is the identifier used for login, teams, and Apigee developers.
Workspace — required. The user is provisioned as a developer in that Apigee organization.
Role — a portal role from Roles Management (for example Administrator or Developer), not a team role.
Password setup — Set password now (you enter a password they can change later from Profile), or Send reset password email (the account is created and they set their own password from a link).

Creating the portal account also creates the Apigee developer when that step can run. Failure to create the developer does not undo the portal user — use Sync Developers if they are missing in Apigee.

Edit a user

Open the pencil on a row. You can change name, email, portal role, and status. With Update Users you can also set workspaces and fill Profile Fields (including admin-only custom fields).

Save is disabled until at least one workspace is selected.

Billing type

Holders of Manage Billing Type see a Billing Type dropdown on the same editor: Not set, Prepaid, or Postpaid. Prepaid requires credit before usage. Postpaid bills after consumption. Billing type is per developer per workspace.

The portal default for newly provisioned developers is set under Configuration → API → Monetization Defaults, not on this tab. See Monetization.

Delete a user

Delete asks which workspaces to remove the user from. Selecting every workspace (or deleting a user with none) permanently deletes the portal account. The confirmation lists what that includes: the user’s apps, membership in every team, and optionally teams they own and Page Builder pages they created (those last two are checkboxes when they apply).

Sync Developers

On Users List, click Sync Developers. Choose one active Apigee organization and Start Sync. Sync affects only that organization.

Portal users who are not yet developers in that org are created there.
Apigee developers in that org who are not yet portal users are created in the portal.

You need at least one active Apigee organization. If none is connected, the modal asks you to configure a workspace first. See Apigee Integration.