Skip to main content
Profiles are encryption namespaces inside an organization. Each profile carries its own root key.

​
abadge profile add

The CLI calls POST /v1/orgs/{orgId}/profiles and prints the new profile ID. Bootstrapping a zero-knowledge profile (generating the KEK, wrapping the root key) is a dashboard operation in v1 — create it in the CLI and finish the bootstrap at abadge.io before adding items. Personal accounts are capped at a single profile: profile add returns PROFILE_LIMIT_EXCEEDED when the active organization is a personal account that already has a profile. Team organizations are uncapped.

​
abadge profile list

Lists profiles in the active organization.
Output columns: ID, Name, Storage Mode, Created, Active (checkmark for the active profile).

​
abadge profile use <name-or-id>

Set the active profile. Persisted to ~/.abadge/config.json as activeProfileId. Subsequent item add commands target this profile.
Accepts either the profile name or ID. If the name isn’t unique, use the ID.

​
Vault operations

For unlock, lock, status, and change-password, see Profile security commands. Those commands are also exposed as abadge profile unlock|lock|status|change-password.