Managing Your Account Settings

Your Hopsule account serves as the foundational identity for your contributions to your team’s decision layer and collective memory. Managing these settings correctly ensures that your organizational judgment is accurately preserved, your authority is verified across all product surfaces, and your access to critical context remains secure and seamless.

By configuring your account preferences, you establish how you interact with the Hopsule Dashboard, Hopsule CLI, and Hopsule for VS Code, while maintaining the high security standards required for engineering governance. This article provides an exhaustive guide to every configuration option available within your personal account space.

Prerequisites

Before modifying your account settings, ensure you have the following:

• An active Hopsule account (Free, Pro, or Enterprise).

• Access to the Hopsule Dashboard via a supported web browser.

• Verification of your primary email address to unlock security and notification features.

• If using Hopsule CLI, ensure you have your terminal environment ready to test newly generated access tokens.

Accessing the Account Settings

To begin managing your profile and preferences, log in to the Hopsule Dashboard. In the bottom-left corner of the sidebar, click on your profile avatar or username. From the resulting pop-up menu, select Account Settings. This will navigate you to the centralized management interface where your identity and security parameters are governed.

1. Profile Management

Your profile is more than just a digital business card; it is the primary identifier linked to every Decision and Memory you create. In Hopsule, attribution is a core component of authority and remembrance.

Updating Personal Information:

1. Navigate to the Profile tab within the Account Settings.

2. Locate the Full Name field. This name will appear in the "Author" section of any Decisions you draft or Memories you append. Ensure this matches your professional identity within your organization.

3. Update your Professional Title. This provides context to other team members regarding the perspective from which a decision was made.

4. Click the Update Profile button at the bottom of the section to commit your changes to the Hopsule memory layer.

Avatar and Visual Identity:

Your avatar is displayed in the Knowledge Graph (Brain) and the activity feed. To change it, click the Upload New Avatar button. Hopsule supports standard image formats. A clear avatar helps teammates quickly identify the source of a decision when scanning the Knowledge Graph for historical context.

2. Security and Authentication

Security is a baseline guarantee in Hopsule. All data, including your account credentials, is protected by AES-256 encryption at rest and TLS 1.3 in transit. Managing your security settings is vital for maintaining the integrity of your organization’s governance.

Changing Your Password:

1. Select the Security tab.

2. In the Change Password section, enter your Current Password.

3. Enter your New Password and confirm it in the following field. Hopsule requires high-entropy passwords to ensure the preservation of your authority.

4. Click Save Password. You will be logged out of all other active sessions except for the current one to ensure account synchronization.

Multi-Factor Authentication (MFA):

For engineering leaders and those with high-level authority over Context Packs, MFA is strongly recommended. Click Enable MFA and follow the on-screen instructions to link your preferred authenticator application. Once enabled, Hopsule will require a time-based one-time password (TOTP) for every login attempt on the Hopsule Dashboard and when authenticating the Hopsule CLI for the first time on a new machine.

3. Managing Access Tokens

Access tokens are the bridge between your account and the external Hopsule ecosystem, including the Hopsule CLI, Hopsule API, and Hopsule MCP. These tokens allow these tools to read and interact with your decisions and memories without requiring your primary password.

Generating a New Token:

1. Navigate to the Access Tokens tab.

2. Click the Create New Token button in the top-right corner.

3. Provide a Token Name that describes its purpose (e.g., "Home Office CLI" or "Production CI/CD").

4. Select the Scope of the token. You can choose between Read-Only (ideal for Hopsule MCP and AI agents) or Full Access (required for Hopsule CLI to create decisions).

5. Set an Expiration Date. For maximum security, Hopsule recommends rotating tokens every 90 days.

6. Click Generate.

7. Important: Copy the token immediately. For your security, Hopsule does not store the raw token and it will never be shown again.

Revoking Tokens:

If a device is lost or a token is compromised, locate the token in the Active Tokens list and click the Revoke button. This immediately terminates the token’s authority to access your context and memories.

4. Notification Preferences

Hopsule is designed to keep you informed of the evolving decision landscape without overwhelming you. Enforcement is remembrance, and notifications ensure you remember when a decision moves through its lifecycle.

Configuring Alerts:

1. Go to the Notifications tab.

2. Toggle Decision Lifecycle Changes to receive alerts when a decision you authored or follow moves from Draft to Accepted or Deprecated.

3. Enable Memory Appended alerts to stay informed when new reasoning is added to a decision you are involved in.

4. Configure Conflict Warnings. These are triggered when Hopsule for VS Code or Hopsule CLI detects a contradiction between current code and an accepted decision.

5. Choose your delivery method: In-App Activity Feed, Email, or Real-time Desktop Notifications.

5. Session Management

The Sessions tab provides a transparent view of every device currently accessing your Hopsule account. This includes the Hopsule Dashboard, active Hopsule CLI logins, and Hopsule for VS Code instances. Each entry displays the IP address, approximate location, and last active timestamp. If you notice unfamiliar activity, use the Terminate All Other Sessions button to secure your account immediately.

6. Interface and Experience Settings

Customizing how you view your team's context can improve your ability to internalize organizational judgment.

• Theme Selection: Choose between Light, Dark, or System Default. The Knowledge Graph (Brain) adjusts its contrast based on this setting for optimal visualization of decision relationships.

• Default Project: Select which project the Hopsule Dashboard should load by default. This is particularly useful for senior developers managing multiple organizational context packs.

• Language and Locale: Set your preferred regional formatting for dates and timestamps, ensuring that the timeline of memories is always clear.

Tips and Best Practices

• Audit Your Tokens: Regularly visit the Access Tokens tab to revoke any tokens that are no longer in active use. This minimizes the attack surface for your organizational context.

• Use Detailed Profiles: In large engineering organizations, adding your professional title and a clear avatar helps Hopper provide better context when other users ask, "Who is the authority on this decision?"

• Enable Conflict Notifications: By enabling real-time conflict warnings, you ensure that you are the first to know when a code change contradicts an established decision, allowing for immediate enforcement or healthy debate.

• Leverage Read-Only Tokens for AI: When connecting Hopsule MCP to third-party AI agents, always use a Read-Only token. This allows the AI to gain context and remembrance without the ability to mutate your team's accepted decisions.

• Session Regularity: Check your active sessions once a month to ensure that your account isn't logged in on forgotten public terminals or old hardware.

Troubleshooting

If you encounter issues while managing your account, refer to the table below for common causes and solutions.

Related Articles

• Understanding Decision Lifecycles: From Draft to Deprecated

• Configuring the Hopsule CLI for Team Governance

• Managing Organization and Project Permissions

• Best Practices for Creating Enforceable Context Packs