kloudedocs
Browse documentation
On this page

PRODUCT GUIDE

Settings

Manage account profile, password and 2FA, notification channels, personal API keys for Terraform, and organization members from the Kloude Settings panel.

Settings covers your profile and how your organization works in the portal: security, notifications, API keys for automation, and members. Open Settings from the portal navigation when you need account-level changes rather than a product page.

Inside Settings you switch between User account, Security, Notifications, API keys, and Organization.

User account

Update your display name and review your verified email. Save when you change the profile.

Security

Under Password, enter the current password, the new password, and confirmation. A Two-factor authentication tab sits next to password for stronger sign-in.

Notifications

Choose how account notifications are delivered, email and, after verifying an Iranian mobile number with a one-time code, SMS. SMS stays disabled until the number is verified.

API keys

Create personal keys for Terraform and scripts with + Create key. The key works only in the organization selected while you create it. Switching the organization switcher later does not move that key; create another key there. Prefer least privilege and a separate key per pipeline. Revoke keys you no longer use. Interactive cluster access still prefers kubeconfig; see API reference.

Organization

Rename the workspace, Invite member, and review roles (owner vs member) and permission tags (clusters, VPCs, registry, billing, and similar). Owner permissions cannot be edited away; use Edit permissions for members.

Tutorial: common settings tasks

Open Settings

Select Settings in the portal navigation.

Update profile or password

Use User account for name and email display, or Security → Password to rotate credentials. Enable 2FA when your org requires it.

Configure notifications

Verify a mobile number if you need SMS, then pick email and/or SMS channels.

Create an API key

Open API keys, create a key scoped for the tools you run, and store the secret in your secret manager, not in git or tickets.

Invite teammates

On Organization, invite members and assign only the permissions they need.