Spaces
Learn about Bindly Spaces: personal, team (public/private toggle), and official. Organize knowledge with member roles and access control.
A Space is a workspace that owns Bindings and Sets. It defines the access boundary for your knowledge.
Space Types
Personal Space
- Created automatically when you register
- Always private — only you and your LLM can access
- Cannot be converted to team or public
- Every user has exactly one personal Space
Team Space
- Created by any user
- Invite members with roles: owner, admin, member
- Private by default — only invited members can access
- Can be toggled to public — content becomes visible at
bind.ly/@your-space - Public team Spaces allow member auto-join
Official Space
- Created by Bindly (admin only)
- Permanently public — cannot be made private
- Verified by Bindly (trust signal)
- Prioritized in llms.txt and sitemap
- Anyone can join as a member
Member Roles
| Role | Read | Create | Edit Own | Edit All | Delete All | Manage Members | Delete Space |
|---|---|---|---|---|---|---|---|
| owner | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| admin | Yes | Yes | Yes | Yes | Yes | Yes | No |
| member | Yes | Yes | Yes (own) | No | No | No | No |
Public Spaces and SEO
When a team Space is set to public (or for official Spaces):
- All Bindings are accessible at
bind.ly/@space-slug/binding-slug - Content is included in sitemap.xml for search engine indexing
- JSON-LD structured data is generated for each Binding
- Content negotiation: append
?format=mdfor markdown
Creating a Team Space
Via Web
Via MCP
mcp_create_space({ name: "My Team", type: "team", isPublic: true })Example: Official Spaces
Bindly maintains two official Spaces you can explore:
- @bindly — A public Team Space with official docs and guides
- @bindly-feedback — An Official Space where anyone can join and share feedback, feature requests, or bug reports. Uses Labels (
question,feature-request,bug,showcase) to organize content.