user

1ctl user is for managing your own account. It covers the things that are scoped to you personally: your profile, your password, the permissions your role grants you, and the active sessions across your devices.

This is not for managing other users in your organization — that lives under 1ctl org.

The backend for all user commands is GET/PATCH /v1/cli/users/profile.

Commands

`1ctl user me`

1ctl user me

Prints your current profile: name, email address, role, and the organizations you belong to. This is a read-only view of who you are from the platform’s perspective.

$ 1ctl user me
Name:     Jane Smith
Email:    [email protected]
User ID:  usr_01j9x7k3p2
Role:     member

Organizations:
  org_04k2  acme          (role: admin)
  org_09z1  acme-staging  (role: member)

`1ctl user update`

1ctl user update [--name <name>] [--email <email>]

Updates your profile fields. You can change your display name, email address, or both in a single call. At least one flag is required.

Flags

Flag	Description
`--name <name>`	New display name.
`--email <email>`	New email address. The platform may send a verification email to the new address.

# Update display name
1ctl user update --name "Jane Smith"

# Update email
1ctl user update --email [email protected]

# Update both at once
1ctl user update --name "Jane Smith" --email [email protected]

`1ctl user password`

1ctl user password

Opens an interactive password change prompt. You will be asked for your current password, then your new password twice for confirmation. The prompt does not echo input.

$ 1ctl user password
Current password: ••••••••
New password:     ••••••••
Confirm:          ••••••••
Password updated.

There is no --password flag. Passwords are never accepted as command-line arguments to avoid them appearing in shell history and process listings.

`1ctl user permissions`

1ctl user permissions

Lists the effective RBAC permissions for your account. Satusky has two permission layers: your platform role (set on your user account) and your organization role (set per-organization membership). The output shows both.

$ 1ctl user permissions
Platform role: member

Organization roles:
  acme          admin
  acme-staging  member

Effective permissions:
  deployments     create, read, update, delete
  secrets         create, read, delete
  domains         create, read, update, delete
  organization    read, update
  billing         read
  users           read

Use this when you get an unexpected 403 Forbidden and want to understand what your current role allows before contacting a platform admin.

`1ctl user sessions revoke`

1ctl user sessions revoke

Revokes all active sessions for your account across every device and browser. Any tab or client that was logged in with a session cookie is forced to re-authenticate. Your current CLI session using an API token is not affected — API tokens are separate from browser sessions.

$ 1ctl user sessions revoke
All active sessions revoked. Other devices will require re-login.

Use this if you suspect unauthorized access to your account, after logging in on a shared or untrusted machine, or as a general security hygiene step after a password change.