HackMD team visibility is broader than a single note link
HackMD organizes notes and collaboration into personal and team workspaces. The team workspace has roles, note permissions, default permissions, API tokens, and public note links. A review that focuses on one shared note can miss the fact that team members may have read access to every note in the workspace.
The official team documentation says all members in a team workspace have read access to every note in it. A note can separately allow people outside the team to read it when the reading permission is set to Everyone. The two controls answer different questions: workspace membership grants a baseline, and a note link can extend access beyond that baseline.
What the measurement shows
On 2026-11-21 between 06:47 and 06:49 CST, a bounded SDK query used sub_type=all, page 1, and page size 1. title="HackMD" returned 138 index matches. The exact app="HackMD" query returned 0. The title count is a reasonable discovery list for owners, but it is not proof of a HackMD server or a public note.
The query is available through the ZoomEye search link.
Inventory workspace roles
List teams, owners, members, guests, and API tokens. Record the default note permission and whether a Prime or Enterprise feature changes the defaults. Test a member who should read a note but not edit it, and a guest who should see only an explicitly shared note. Remove a member and confirm that the session and token lose access.
HackMD API tokens inherit the user's account permissions across the teams the user belongs to. A token created for a reporting script can therefore be broader than the script's label. Give each integration a named account or a narrowly governed token, store it outside the note content, and revoke it when the owner leaves.
Review public note links
A note's Everyone permission can expose it beyond the team. Check expiration, password, comment, edit, and view settings where the deployment supports them. A public note can include embedded images, uploaded files, links to internal systems, or code that reveals an infrastructure path.
Review the team domain and any custom link that resolves to a note. A team URL may be public while the notes remain private, and a personal note may be shared with a broad link. Test the link in a logged-out browser and inspect the rendered content as well as the HTTP status.
Operate the collaboration service
Use TLS and a maintained reverse proxy. Keep the database, object storage for uploads, and administrative interfaces on private networks. Back up notes and attachments together. If the service supports OIDC or another identity provider, verify the issuer, callback, and group mapping.
For an owned team, test a role change, a token revocation, a public-link removal, and a workspace export. For a discovered title, identify the owner and avoid guessing note IDs or trying to join a team.
HackMD makes collaboration fast because access is shared across a workspace. That same convenience requires a clear team membership list and a separate review for every link that leaves it.
Top comments (0)