Inviting Team Members to Your Project

Introduction

Collaborative governance is the cornerstone of a resilient engineering organization. This article provides a comprehensive guide on how to invite team members to your project within the Hopsule Dashboard, ensuring that your collective organizational judgment is preserved and enforced across every developer's environment. By bringing your team into Hopsule, you transform individual insights into a shared, enforceable memory layer that protects the integrity of your technical decisions.

Effective team management in Hopsule is not merely about granting access; it is about establishing a hierarchy of authority and a culture of remembrance. Whether you are scaling a startup or managing a large enterprise division, understanding how to distribute roles and manage permissions is vital for maintaining the continuity of your context packs and the reliability of your decision-making processes.

Prerequisites

Before you begin inviting members to your Hopsule project, ensure that the following conditions are met to provide a seamless onboarding experience for your engineering team:

• Administrative Authority: You must hold either the Owner or Admin role within the specific project to manage team memberships and permissions.

• Active Project: You must have at least one active project created within the Hopsule Dashboard.

• Verified Email Addresses: Ensure you have the professional email addresses of the individuals you wish to invite. For Enterprise customers using SSO, ensure the users exist within your identity provider's directory.

• Seat Availability: Verify that your current plan tier has sufficient available seats. While Hopsule offers flexible scaling, reaching your seat limit may require an upgrade to accommodate additional team members.

Detailed Step-by-Step Instructions

1. Accessing the Team Management Interface

To begin the invitation process, you must navigate to the centralized management hub for your project's personnel and permissions.

1. Log in to the Hopsule Dashboard using your secure credentials.

2. Select the project you wish to manage from the project switcher located in the top-left corner of the sidebar.

3. Click on the Settings icon (represented by a gear) at the bottom of the sidebar navigation.

4. Within the Settings menu, locate and click on the Members & Permissions tab. This view provides a comprehensive overview of all current project participants, their active roles, and any pending invitations.

2. Initiating a New Invitation

Hopsule allows you to invite individuals or multiple team members simultaneously to streamline the growth of your memory layer.

1. Click the Invite Member button located in the top-right corner of the Members & Permissions screen.

2. In the modal that appears, enter the email address of the team member you wish to add. If you are inviting multiple people with the same role, you can enter multiple email addresses separated by commas.

3. Select the appropriate Role from the dropdown menu. It is crucial to choose the role that aligns with the individual's level of authority within your engineering organization (see the "Understanding Roles" section below for details).

4. Click Send Invitation. Hopsule will immediately dispatch a secure, tokenized invitation link to the provided email addresses.

3. Understanding Roles and Authority Levels

Hopsule utilizes a sophisticated role-based access control (RBAC) system to ensure that enforcement is balanced with appropriate levels of governance. Each role defines how a user interacts with decisions, memories, and context packs.

• Owner: The highest level of authority. Owners have full control over project settings, billing, and the ability to delete the project. They can manage all other members and have unrestricted access to the Hopsule API and Knowledge Graph.

• Admin: Responsible for day-to-day governance. Admins can accept or deprecate decisions, manage member roles (except for the Owner), and configure Context Packs. They are the primary curators of the organizational memory.

• Contributor: The standard role for senior developers and architects. Contributors can draft new decisions and append memories. However, they cannot move a decision to the "Accepted" state without Admin or Owner approval. They have full access to Hopsule for VS Code and the Hopsule CLI for enforcement.

• Viewer: A read-only role designed for stakeholders or junior members who need to understand the context without altering it. Viewers can browse the Knowledge Graph, search decisions, and use Hopper for inquiries, but they cannot create or modify any entities.

4. Managing Pending Invitations

Once an invitation is sent, it remains in a "Pending" state until the recipient accepts it. You can manage these invitations from the same interface.

1. Locate the Pending Invites section at the bottom of the Members & Permissions page.

2. To remind a team member, click the Resend button next to their email address. This will generate a new secure link.

3. If an invitation was sent in error, click Revoke to invalidate the link and prevent the user from joining the project.

5. Onboarding via Hopsule CLI

For organizations that prefer terminal-based workflows, team members can also be managed via the Hopsule CLI. This is particularly useful for automating onboarding scripts.

The Hopsule CLI provides a streamlined TUI (Text User Interface) to view the status of your team and ensure that everyone is correctly synchronized with the project's decision layer before they begin their first sprint.

6. Modifying and Removing Members

As your organization evolves, you may need to adjust permissions or offboard individuals to maintain security and data sovereignty.

1. To change a user's role, locate their name in the Active Members list and select a new role from the dropdown menu in their row. Changes take effect immediately across the Hopsule Dashboard, Hopsule for VS Code, and Hopsule MCP.

2. To remove a member, click the Remove (trash can) icon. This action immediately revokes their access to the project's decisions and memories. Note that any memories or decisions they authored will remain in the system to preserve historical context, as Hopsule memories are append-only and never deleted.

Tips and Best Practices

• The Principle of Least Privilege: Assign the Viewer or Contributor role by default. Only grant Admin status to those responsible for the final validation of architectural and procedural decisions.

• Utilize Hopper for Onboarding: Encourage new team members to use Hopper, the built-in AI assistant, to ask questions about why certain decisions were made. This reduces the burden on senior engineers and speeds up context acquisition.

• Audit Regularly: Periodically review your member list in the Hopsule Dashboard to ensure that former employees or contractors no longer have access to your organizational memory.

• Sync with Context Packs: When inviting members to a specific project, consider which Context Packs (Capsules) are active. New members will automatically inherit the enforcement rules defined in these packs within their Hopsule for VS Code environment.

• CLI for Automation: Use the Hopsule API or Hopsule CLI to integrate your employee onboarding process with Hopsule, ensuring that every new hire is automatically added to the relevant memory layers on their first day.

• Leverage the Knowledge Graph: Show new members the Knowledge Graph (The Brain) during their first week. Visualizing how decisions and memories interlink helps them grasp the complexity and reasoning of the system they are entering.

Troubleshooting

If you encounter issues while managing your team, consult the table below for common causes and resolutions.

Related Articles

• Understanding Decision Lifecycles: From Draft to Deprecated

• Creating and Distributing Context Packs (Capsules)

• Configuring Hopsule for VS Code for Team Enforcement

• Using Hopper to Navigate Organizational Memory