Team and Organization Management

Effective governance within Hopsule begins with a robust organizational structure that mirrors your engineering hierarchy. This article provides a comprehensive guide to establishing organizations, managing teams, and configuring the granular access controls necessary to maintain a high-fidelity memory system across your entire engineering department.

By correctly configuring your organization, you ensure that decisions are enforced where they matter and that the reasoning behind your technical evolution—stored as memories—remains accessible to the right people at the right time. Hopsule is designed to scale from solo developers to multi-national engineering teams, providing a consistent layer of organizational judgment regardless of team size.

Prerequisites

Before managing teams or organizations, ensure you meet the following requirements:

• A registered and verified Hopsule account.

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

• Administrative or Owner permissions if you are modifying an existing organization.

• For CLI-based management, the latest version of the Hopsule CLI must be installed and authenticated.

Creating and Configuring an Organization

An Organization in Hopsule is the highest-level entity, serving as the primary container for all decisions, memories, and context packs. It acts as the boundary for billing, security policies, and high-level governance.

1. Log in to the Hopsule Dashboard.

2. Click on the Organization Switcher located in the top-left corner of the interface.

3. Select + Create New Organization from the dropdown menu.

4. Enter a unique Organization Name. We recommend using your company's legal name or primary engineering brand.

5. Choose an Organization Slug. This will be used in the Hopsule API and Hopsule CLI to identify your environment.

6. Click the Create Organization button to finalize the process.

Once created, you will be redirected to the Organization Overview. From here, you can access the Knowledge Graph (also known as the Brain) to visualize how decisions will eventually interconnect across your new entity.

Managing Team Hierarchies

Teams are functional subsets within an organization. They allow you to group developers by project, product area, or specialty (e.g., "Platform Team" or "Frontend Squad"). Decisions can be scoped to specific teams to ensure that enforcement is relevant and not intrusive.

Creating a Team

1. Navigate to the Settings tab in the left-hand sidebar of the Hopsule Dashboard.

2. Click on the Teams sub-menu.

3. Click the Create Team button in the top-right corner.

4. Provide a Team Name and an optional description. Use the description to define the team's scope of authority (e.g., "Responsible for core API architecture and data persistence decisions").

5. Click Save Team.

Adding and Inviting Members

Hopsule utilizes an invitation-based system to maintain security and ensure that only authorized personnel can contribute to the organizational memory.

1. Within the Teams section, select the team you wish to manage.

2. Click the Members tab.

3. Click Invite Member.

4. Enter the email address of the team member.

5. Assign an initial Role (see the "Understanding Roles and Permissions" section below for details).

6. Click Send Invitation.

The invitee will receive an email with a secure link to join the organization. You can monitor the status of pending invitations in the Activity Feed on the main dashboard.

Understanding Roles and Permissions

Hopsule employs a strict Role-Based Access Control (RBAC) model to ensure that while everyone can remember, only authorized individuals can set the direction of enforcement.

Project-Level Access Controls

In Hopsule, "Projects" represent the technical repositories or systems where Hopsule for VS Code and the Hopsule CLI are active. Access control at this level ensures that sensitive architectural decisions are only visible to the relevant teams.

Linking Projects to Teams

1. Go to the Projects section in the Hopsule Dashboard.

2. Select a project from the list.

3. Navigate to the Access Control tab.

4. Use the Associated Teams dropdown to select which teams have authority over this project.

5. Toggle the Strict Enforcement setting. When enabled, Hopsule for VS Code will flag contradictions to accepted decisions as high-priority warnings that require explicit overrides.

Configuring Context Pack (Capsule) Visibility

Context Packs, or Capsules, are portable bundles of decisions and memories. Their visibility can be managed at the organization level to facilitate cross-team learning or to silo specific domain context.

• Draft Capsules: Visible only to the creator and organization Admins.

• Active Capsules: Visible to all members of the assigned teams.

• Frozen Capsules: Read-only bundles used for historical preservation; visible to the whole organization but no longer mutable.

• Historical Capsules: Archived context that remains searchable but is hidden from the primary Hopsule for VS Code sidebar to reduce noise.

Security and Governance Settings

Hopsule prioritizes the preservation of organizational judgment through several security-first features. These are managed within the Security & Compliance section of the Hopsule Dashboard.

Audit Logs

Every change to a decision’s lifecycle (Draft → Pending → Accepted → Deprecated) is recorded in the immutable Audit Log. This ensures full traceability of who made a decision and why. To view these logs, navigate to Settings > Audit Logs. You can filter by user, team, or specific Context Pack.

API and Integration Management

For enterprise teams, managing access via the Hopsule API or Hopsule MCP is essential. In the Integrations tab, you can generate Personal Access Tokens for the Hopsule CLI or Service Tokens for CI/CD pipelines. Note that Hopsule MCP provides read-only access to decisions for AI agents, ensuring that agents can be context-aware without having the authority to mutate your organization's commitments.

Tips and Best Practices

• Enforcement is Remembrance: Use the Strict Enforcement toggle sparingly. It is most effective for critical architectural constraints (e.g., security protocols or core data patterns) rather than stylistic preferences.

• Naming Conventions: Establish a clear naming convention for teams (e.g., dept-team-function) to make the Knowledge Graph easier to navigate as your organization grows.

• Utilize Hopper: When setting up a new team, use Hopper to draft initial decisions based on your existing technical documentation. Hopper can identify potential conflicts between the new team's goals and existing organizational decisions.

• Regular Reviews: Schedule a monthly review of "Pending" decisions. Decisions that stay in "Pending" for too long can lead to organizational drift.

• Solo Mode Transition: If you started as a solo developer, you can transition your personal decisions into a team-based structure by creating an Organization and importing your existing Context Packs.

Troubleshooting

Related Articles

• Understanding the Decision Lifecycle

• Creating and Sharing Context Packs

• Configuring Hopsule for VS Code Enforcement