Skip to content

Manage app users

These commands manage users inside an owned app. They use your platform key. Protected business requests use a separate app session. User roles apply only to the selected app.

Terminal window
bfast users create --app my-counter --email tester@example.invalid \
--name "Test User" --verified
bfast users list --app my-counter --limit 10 --offset 0
bfast users get --app my-counter --user '<user ID>'

Creation prompts for an app password of 12 to 128 bytes. The --verified flag records your owner attestation and sends no mail. Without that flag, the user is unverified and cannot log in until verification succeeds.

Terminal window
bfast users verify --app my-counter --user '<user ID>'

Use immutable IDs in later commands. Equal emails in different apps do not share an identity. Paginate long lists; inspect truncation indicators instead of assuming one response contains every user.

Terminal window
bfast users role --app my-counter --user '<user ID>' --role admin
bfast users revoke-sessions --app my-counter --user '<user ID>'

Role changes revoke applicable sessions. The admin role applies inside the app; it grants no platform, operator-console or other-app access.

Terminal window
bfast users disable --app my-counter --user '<user ID>'
bfast users enable --app my-counter --user '<user ID>'
bfast users delete --app my-counter --user '<user ID>'

These actions change access and revoke sessions as applicable. User deletion does not imply a cascade through every business model row or saved File. Design your application’s data retention explicitly.

Read scope permits inspection. Write scope permits changes, including user deletion. App-delete permission alone does not grant user or SMTP changes. Run bfast help for the current command list.