Team & Access
Once you share a heap, it has members. This page covers how to see who has access, change what they can do, and remove them.
Where to manage your team
Open Settings → Heaps and select the heap. The Sharing section has five tabs:
| Tab | What you do there |
|---|---|
| Members | See everyone in the heap, change roles, remove people |
| Groups | Bundle people so they get the same role on a block |
| Shared | See every block that has its own access settings |
| Activity | See a log of access and sharing changes |
| Security | Security options for the heap, such as expiring offline access |
Only owners and admins can manage members. Everyone else sees Your access and Shared with you instead.
Members and roles
Each member has a heap role and a heap-wide access level:
- Admin: manages members and sharing, and has full access to everything.
- Member: gets the heap-wide access you choose:
- Shared blocks only: sees nothing except blocks shared with them directly
- Viewer: can read the whole heap
- Commenter: can read and comment
- Editor: can create and edit everything
For a single project or note, you can give someone a different role there. See Sharing a single note or file. No access on a block always wins, so you can keep one area private even from editors.
Groups
Groups give several people the same role on a block. Create one under Groups → New group, add people, then share a block with the group instead of with each person.
Removing someone
Under Members, select the person and choose Remove from heap, then confirm. They lose access to the heap. Pending invites are not changed, so revoke those separately. Files they already exported stay with them.
Expiring offline access
Because Heaper works offline, members keep a copy of the heap on their devices. Under Security, Expire offline access after seven days makes every device, including yours, reconnect at least once a week. A device that hasn't checked in locks the heap until it reconnects. Unsent drafts stay on the device.
New users on your own server
On a self-hosted server, the first person to sign up becomes the admin. Everyone after that needs approval:
- The new person signs in. They see that their account is pending admin approval.
- As admin, open Settings → Servers, select your server and find Server Admin. It shows N awaiting approval.
- Select Approve user or Reject user.
Server Admin also lists everyone on the server, with their plan, storage use and quota. You can override a person's quota there.
On Heaper Cloud anyone can sign up with their email, and you only control who joins your heaps.
AI agents
You can let an AI assistant such as Claude or ChatGPT read and edit your heaps. Each agent gets only the heaps and permissions you approve.
- Open Settings → Agents.
- Add the MCP address shown there to your AI client and start its sign-in.
- The client shows a Pairing code. Enter it under Find request.
- Name the agent, choose its Permissions (Read, Create and edit content, Stay connected) and its Heaps, then select Approve.
You can change an agent's access later, or select Disconnect profile to remove it. Developer details are in Agent and MCP Access.