Uncategorized

How to Use Gimmer’s Security Center to Review Identity and Update Your Password

Share this post

If you’re already signed in to Gimmer and need to confirm which account you’re using, update the name shown in the app, or change your password, the current Security Center already gives you that path. The useful habit is to stay inside Identity & access and the Security card, not drift into separate wallet backup and recovery tasks on the same page.

Gimmer dashboard in dark theme showing the Identity & access section with Account and Security cards, fields for Username, Display name, Wallet address, Current password, and New password, and Save changes and Update password buttons

Why This Route Needs A Narrow Read

Gimmer’s current profile route brings more than one trust boundary into the same place. It shows routine account-maintenance panels, but it also leads into wallet backup and recovery surfaces lower on the page.

That is why this article stays narrow. It is only about signed-in identity and password maintenance inside Security Center. It is not a tour of every control on the route, and it is not a guide to account recovery or secret handling.

This article covers routine identity and password maintenance only. Private-key export, keystore backup, and recovery actions remain separate wallet-protection tasks and should not be treated as part of normal account upkeep.

Start With Identity & Access

Open Gimmer, sign in, and go to Security Center. The section that matters for this workflow is Identity & access.

That section keeps the visible account-maintenance work in one place. The Account card shows the context around the signed-in account, and the Security card handles the current password-update flow.

If your goal is routine account upkeep, that is the right stopping point. You do not need to keep scrolling into backup or recovery surfaces to complete this workflow.

Review Username Context And Update Display Name

The first useful distinction on this route is simple: some fields are there to confirm context, and one field is there to change.

Username is visible context, not an editable control. The current route lets you review it so you can confirm you are working in the expected account, but it does not present it as something to change.

Display name is the field you can edit. If the name shown in the app needs to be updated, change it there and use Save changes.

The same card also shows Wallet address as visible account context. That does not turn this workflow into a wallet-secret task. It is simply part of the account card the route currently displays.

When the update succeeds, the current route confirms it with Profile updated. If you clear the display name and try to continue, the route responds literally with Display name is required.

Use The Security Card For In-Session Password Maintenance

The adjacent Security card is the current signed-in path for changing a password.

It asks for Current password and New password, then completes the change through Update password. That is a routine maintenance path for someone who is already inside the product, not a recovery flow for someone who is locked out.

If either field is missing, the route says Current and new password are required. If the new password is too short, it says New password must be at least 6 characters. When the change completes, it confirms the result with Password updated.

Security Center shows the signed-in password update form; it is not proof of a lockout-recovery or password-reset workflow.

What This Workflow Does Not Cover

A narrow workflow is useful because it reduces the chance of inventing a capability the current product is not showing.

This article is not about changing a username. It is not about resetting access by email. It is not about recovering a locked account from the sign-in screen. And it is not about exporting a private key, downloading a keystore, or treating backup tasks as part of normal account upkeep.

Those boundaries matter because the route name can sound broader than the specific workflow you are doing. The better reading is practical: use the visible identity and password controls for identity upkeep, and treat wallet protection and recovery as separate decisions.

A Practical Routine Before You Move On

A short routine keeps the route useful:

  • Open Security Center and stop at Identity & access.
  • Confirm the visible Username matches the signed-in account you expect.
  • Update Display name only if needed, then use Save changes.
  • Use Current password and New password only when you intend to change the current sign-in password.
  • Leave wallet export, backup, and recovery tasks for a separate, deliberate workflow.

That routine is calmer than treating the whole page as one generic security checklist. It keeps routine account maintenance literal to the controls the product is currently showing.

Final Thoughts

Good account maintenance is usually straightforward when the route is read honestly. Confirm the account context. Update the visible display name if it needs to change. Change the password while you are signed in. Stop there unless you intentionally need a separate wallet-protection task.

Open Gimmer, sign in, go to Security Center, review Identity & access, confirm the visible Username, update Display name if needed, and use Current password plus New password to update your password.

— The Gimmer Team

Leave a Reply

Your email address will not be published. Required fields are marked *

*

Related stories

Dark-theme Gimmer Docs Errors view showing a structured failure payload with error ‘Forbidden’ and message ‘insufficient permissions: requires scope bots:control’, followed by a status matrix for 400 invalid request, 401 authentication required, 403 insufficient permissions, 404 resource not found, 409 state conflict, and 500 internal error.

Crypto Trading API Errors in Gimmer: How to Tell Authentication, Scope, and Rate-Limit Signals Apart

Dark-theme Gimmer AI Runtimes settings view showing Local HTTP API connection and authentication fields, a loopback server endpoint, an API key placeholder labeled "Stored in this device's OS keychain", model and limit fields, a checked "Profile enabled" control, the diagnostic "Connection ready. No secret is shown in this view.", capabilities, and Delete, Test connection, Studio default, and Save changes controls.

How to Test an AI Runtime Before Making It Gimmer’s Strategy Studio Default

Gimmer dark-theme AI Strategy Studio showing an AI strategy proposal dialog titled “BTC guarded momentum proposal,” with the context “Indicators · Spot · Binance · 1h,” the thesis “Use confirmed momentum signals while keeping allocation and protective exits explicit for review,” BTC/USDT market, 10 percent allocation, market order, 4% stop loss, indicator stop recovery, 5% trail activation, 10% trail pullback, indicator trail recovery, a backtest window from 2025-01-01 to 2025-06-30, executable setup indicators ema:20,rsi:14, safeties stop-loss:4,trailing-stop:5/10, and the footer “Nothing changes until you create the draft.” with Create draft and Backtest draft actions.

AI Crypto Strategy Design in Gimmer: From Prompt to a Reviewable Backtest Proposal

Gimmer dark-theme optimizer review screen showing Search space with the Jan 01, 2025 to Jun 30, 2025 period, initial balance 10000, EMA buy and RSI buy parameters, and Risk-adjusted return, beside a completed Candidate ranking with Baseline, #1, and #2; Candidate #1 is open to Parameter comparison showing EMA buy / period 20 versus 24, RSI buy / period 14 versus 21, the note "The saved strategy remains unchanged until you apply this candidate.", and Backtest combination and Apply combination actions.

Crypto Trading Strategy Optimization in Gimmer: How to Review a Candidate Before You Apply It