Changing the Initial Password (Commissioning Required)

After installation, Studio has a single bootstrap admin account created. Since every installation shares the same value, be sure to change it before handing the system over to the field.

Item	Value
ID	admin
Password	admin123!

Only created when the user table is empty

This account is seeded only when there are no users at all on first startup. It is not created again on installations that already have accounts in use. So restarting will not bring the default password back.

---

How to Change It — From the Screen

This is the easiest route. After logging in to Studio:

1. Open the bottom-left gear icon Settings → User Management.
2. Reset the password for the admin account.

If there are multiple operators, this is a good time to create a separate account for each person and keep the shared admin for admin use only.

---

Cannot Be Changed on the Server

The Studio admin account is managed by the app. There is no reset path on the server side.

Editing .env has no effect

On login, the server checks in the order ①database → ②environment variable. Once an account is recorded in the DB, it stops there, so changing the value of .env is just editing a dead value. Be especially careful here — it's easy to believe you've changed something when you haven't.

Not the target of bin/passwd.sh

passwd.sh manages two AI keys. The app login account is not on the list, and passing it will be rejected exactly like a typo → Changing Passwords · API Keys.

⇒ If you lose the admin password, you must log in with another admin account to reset it. On installations with only one admin, losing that account makes recovery difficult, so we recommend creating two or more admin accounts during commissioning.

---

AI Keys

Unlike the app login account, AI keys are changed by bin/passwd.sh.

cd /opt/kopens/plantpulse-studio/bin

./passwd.sh --list          # 무엇을 바꿀 수 있는지 (현재값은 마스킹)
./passwd.sh --list --show   # 현재값 전체
./passwd.sh PI_LLM_API_KEY   # 값은 프롬프트로 입력

Key	What	Where
PI_LLM_API_KEY	OpenAI-compatible gateway key	.env — loaded when agent-server starts
PS_ANTHROPIC_API_KEY	Anthropic key	.env — loaded when agent-server starts

The DB password cannot be changed with this tool

🔴 There is no key named PG_PASSWORD. Studio only uses an external PostgreSQL, and the connection info lives in a single DATABASE_URL line in .env. Change the account on the PG side first, align DATABASE_URL, then bin/restart.sh.

Don't attach the value to the command line

It will remain in ps output and shell history. Omitting the value and entering it via the prompt is the recommended route.

The Platform's PP_* is not on this list

Only what Studio owns is listed here. Since the Platform password does not belong to Studio, passing it will be rejected exactly like a typo — change it at Rotating Platform Credentials.

---

Things to Check Together

Besides the password, Studio uses several keys. Go through them all at once during commissioning.

Target	Where
Platform · AI · Git · registry keys	Secrets Management
Key rotation procedure (bin/passwd.sh)	Changing Passwords · API Keys
PostgreSQL connection (DATABASE_URL)	Installation — must be changed together with the role in the DB

---

Verification

Log out and confirm that you cannot log in with admin123!. If you can, it hasn't been changed.

---

Related Documents

• Getting Started — First login and screen layout
• Secrets Management — Where keys are stored
• Changing Passwords · API Keys