Hyperspeed runs as a single workspace per installation. Every person who joins your instance becomes a member of that one organization. You control what each member can do through roles and, optionally, by restricting them to specific spaces.Documentation Index
Fetch the complete documentation index at: https://hyperspeed.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Single workspace model
Each Hyperspeed installation has exactly one organization. The first person to register creates the workspace during the setup wizard. Everyone who joins after that—via invite or open registration—becomes a member of the same workspace. You cannot create a second organization within a single installation.Member roles
Roles are how you grant permissions to members. Hyperspeed ships with system roles that you cannot rename or modify. You can also create custom roles with any combination of permissions.System roles
System roles are created automatically when the workspace is initialized. Their permissions are fixed and cannot be changed.The owner system role cannot be deleted.
Custom roles
Custom roles let you define precise permission sets for your team. You can create as many custom roles as you need, and assign multiple roles to the same member.Creating a custom role
Editing a custom role
You can rename a custom role or replace its permissions at any time. Changes apply to all members who hold that role immediately.Deleting a custom role
You can delete any custom role except the owner role. Deleting a role removes it from all members who currently hold it.Permissions reference
The table below lists every permission available in Hyperspeed.| Permission | What it grants |
|---|---|
org.manage | Manage workspace settings (name, registration mode, etc.) |
org.members.manage | Invite members, approve signup requests, manage roles |
space.create | Create new spaces |
space.delete | Delete spaces |
space.members.manage | Add or remove members from a space |
board.read | View boards |
board.write | Create and edit boards |
tasks.read | View tasks |
tasks.write | Create, edit, and delete tasks |
chat.read | Read chat messages |
chat.write | Send chat messages |
files.read | View and download files |
files.write | Upload and edit files |
files.delete | Delete files |
terminal.use | Open a terminal session |
ssh_connections.manage | Create and manage stored SSH connections |
agent.tools.invoke | Invoke agent tools |
datasets.read | View datasets |
datasets.write | Create and modify datasets |
Assigning roles to members
You need theorg.members.manage permission to assign or change roles.
Space-level access control
Spaces are the top-level containers for projects and work in your workspace. By default, members can access spaces according to their workspace-level permissions, but you can restrict a space so that only explicitly added members can see it. To manage who belongs to a space, you need thespace.members.manage permission.
- Add a member to a space: Go to the space settings and add the member by name.
- Remove a member from a space: Remove them from the space member list. Their workspace membership and roles are unaffected.
Registration modes
You can control how new people join the workspace under Settings → General.Invite-only
Only members withorg.members.manage can generate invite links. No one can register without one. This is the most restrictive mode and is appropriate when your workspace should never be visible to outside users.
Open registration
Anyone who can reach your Hyperspeed URL can submit a registration request. The request enters a pending queue; no account is created until you approve it.Open registration does not grant immediate access. Users are placed in a pending state until an admin approves or denies their request.
Approving signup requests
When open registration is enabled and a user submits a registration form, they appear in the signup request queue. You need theorg.members.manage permission to act on requests.
Approving a request creates the user’s account and assigns them the default member role. You can change their roles afterward from the members list.