User Management

Administrators manage platform accounts under Admin Panel → Users. The area contains Users, Role presets, Wallets, and Test accounts.

Platform roles and pending accounts

The default registration role under Role presets controls new accounts; it is not always pending. When it is pending, approve a user by opening their settings and assigning user, pro, admin, or super_admin.

Find and review users

The user table supports search, role filtering, and pagination. It shows:

• Display name, email, and inviter.
• Platform role and banned state.
• Inherited role limits or a per-user override.
• Group-creation permission.
• Group, total-seat, user-seat, and co-editor limits.

Select Configure to edit a user. Changes affect what the account can create or manage going forward; do not assume that changing a role automatically transfers ownership of existing assets.

Role presets

Role presets configure all five roles with:

• Total custom-model knowledge-base storage.
• Per-file knowledge-base size.
• Permission to create groups.
• Maximum groups.
• Total members, regular users, and co-editors per group.
• Default platform role for newly registered accounts.

The current UI treats 999999 as Unlimited. Total group seats must accommodate the creator, regular-user seats, and co-editor seats. Invalid child-limit combinations cannot be saved or are normalized by the form.

Per-user overrides

A user inherits the limits for their platform role by default. Turn off Inherit role limits to assign account-specific knowledge-base and group limits.

After a role change:

• An inheriting account uses the current preset for its new role.
• An overridden account keeps its specific limits until inheritance is restored or the override is edited.

Ban, unban, and delete

• Ban account sets the account to banned and prevents normal sign-in and use.
• Unban restores access while retaining the account's role and quota settings.
• Permanently delete removes the account and cannot be undone from Studio.

Manage user wallets

Under Users → Wallets, search or filter accounts and review:

• Free credit accumulated.
• Card top-ups accumulated.
• Current available balance.
• Paginated credit history.

Edit wallet sets a target balance. Studio records the difference as an administrator adjustment; it does not create a Stripe payment. For campaign credit with a redemption trail, use gift codes under Admin Panel → Rewards.

Test accounts

An administrator who is not signed in as a test account can create and maintain test-login accounts and assign either a regular test-user or test-admin role. Use them to verify login, authorization, billing, and core flows, not to store production data.

The Test accounts section is hidden when the administrator is itself using a test account, preventing test accounts from administering other test accounts.

Recommended workflow

1. Configure the registration role and role quotas first.
2. Filter for pending, verify identity, and assign the appropriate role.
3. Use per-user overrides only for genuine exceptions and record why.
4. When an account leaves, ban it first and transfer operational responsibility for its assets.
5. Permanently delete only after confirming that nothing must be retained.

Related documentation

• Admin Guide
• Account Roles and Permissions
• Invite and Gift Codes
• Billing, Wallets, and Metering