Skip to content

Account Settings

Account settings control your personal profile, authentication, and API access. These settings apply to your individual account across all teams you belong to.

Profile Settings

Update your basic account information:

  • Name -- Your display name shown in team member lists and activity logs
  • Email -- Your login email and the address used for notifications and invitations

To update your profile:

  1. Click your profile in the Appliku dashboard
  2. Go to Account Settings
  3. Update your name or email
  4. Save changes

Password Management

Change your account password:

  1. Go to Account Settings
  2. Navigate to the Password section
  3. Enter your current password
  4. Enter and confirm your new password
  5. Save

Tip

Use a strong, unique password. Consider using a password manager to generate and store complex passwords.

Two-Factor Authentication (2FA)

Add an extra layer of security to your account with two-factor authentication. When enabled, you must provide a time-based one-time password (TOTP) from an authenticator app in addition to your password when logging in.

Enabling 2FA

  1. Go to Account Settings
  2. Navigate to the Two-Factor Authentication section
  3. Click Enable 2FA
  4. Scan the QR code with your authenticator app (e.g., Google Authenticator, Authy, 1Password)
  5. Enter the verification code from your app to confirm
  6. Save your recovery codes in a secure location

Warning

Store your recovery codes safely. If you lose access to your authenticator app and do not have recovery codes, you will be locked out of your account.

Disabling 2FA

  1. Go to Account Settings > Two-Factor Authentication
  2. Click Disable 2FA
  3. Confirm with your current password or TOTP code

API Token Management

API tokens allow programmatic access to the Appliku API. They are used by the Appliku CLI and for custom integrations.

Creating an API Token

  1. Go to Account Settings
  2. Navigate to the API Tokens section
  3. Click Create Token
  4. Give the token a descriptive name (e.g., "CLI access", "CI/CD pipeline")
  5. Choose an access level:
  6. Full access -- read and write everything: manage apps, deployments, and servers
  7. Read-only -- view logs, configuration, and status only; any write request is blocked with a 403
  8. Custom -- pick exactly what the token can do, per resource
  9. Copy the token immediately -- it is only shown once

The same three options are offered during CLI browser login, so you can create any of them directly from the dashboard or from the terminal login flow. See Giving AI agents read-only CLI access for what restricted tokens can and cannot do.

Custom permissions

Choosing Custom reveals a permission matrix with one row per resource type (Applications, Deployments, Servers, Datastores, Domains, Logs, and so on) and four checkboxes each: Read, Create, Update, and Delete.

  • Full access is a shortcut that ticks every box; Read-only ticks Read on every resource.
  • A custom token can grant, for example, Read + Create + Update on Deployments and Read on Logs while granting nothing on Servers or Team members. This lets an agent deploy and inspect logs without being able to delete or reconfigure infrastructure.
  • Every API request is checked against the token's grants for the specific resource and action it touches. A request the token does not cover is rejected with a 403 that names the missing permission, for example This API token is missing the deployments:update permission.
  • The token list shows each token's effective permissions: a simple chip for Full and Read-only, and a Custom chip (hover for the full per-resource summary) for custom tokens.

Existing Full and Read-only tokens keep working exactly as before; a token created without any permission selection defaults to Full access.

Using Your API Token

With the Appliku CLI:

# Set as environment variable
export APPLIKU_TOKEN=your-token-here
appliku apps list

# Or save to config file
appliku auth login

The CLI resolves tokens in this order: 1. Explicit parameter passed to the command 2. APPLIKU_TOKEN environment variable 3. Config file at ~/.config/appliku/config.toml

With the API directly:

curl -H "Authorization: Bearer your-token-here" \
  https://api.appliku.com/api/v1/teams/

Revoking a Token

  1. Go to Account Settings > API Tokens
  2. Find the token you want to revoke
  3. Click Delete
  4. The token is immediately invalidated

Note

Revoking a token immediately breaks any integrations using it. Update your CLI configuration or CI/CD pipelines before revoking tokens that are in active use.

Notification Settings

Use Account Settings > Notifications to connect personal notification channels. Telegram deployment notifications are configured here because they are attached to your user account, not to a single team.

After connecting Telegram, choose whether to receive deployment notifications for all teams, selected teams, or no teams while keeping the bot connected. You may also see a dismissible banner on application overview pages that links directly to this Notifications tab.

Deleting Your Account

You can delete your own account from Account Settings > Delete Account. Deletion is not immediate: it is scheduled with a 24 hour recovery window so an accidental or unauthorized request can be undone.

When you confirm deletion:

  1. Your account is scheduled for deletion 24 hours in the future.
  2. A recovery email with a recovery link is sent to your email address.
  3. A persistent warning appears in Account Settings while the deletion is pending.

After the 24 hour window passes:

  • Your personal data is removed and your account is deactivated.
  • You are removed from every team you belong to.
  • Any empty team you are the sole owner of is deleted.

Cancelling or recovering a deletion

  • Cancel: While the deletion is pending, open Account Settings > Delete Account and click Cancel Deletion.
  • Recover by email: Open the recovery link from the email at any time before the scheduled deletion.
  • Support: If you did not request the deletion or need help, contact support@appliku.com.

When deletion is blocked

Account deletion is blocked when you are the sole owner of a team that still has other members or active resources (applications, databases, or servers). The dashboard shows which team is blocking the deletion. To proceed, delete those teams first or add another owner to them. Appliku does not shut down or destroy resources on your servers during team or account deletion; it only removes Appliku's records and stops managing/monitoring them.

Next Steps