Content ownership
Every item created in Abyss (a board, a draw, a memo, a cloud, a form…) belongs to exactly one level out of three:
| Level | Internal fields | Owner | Default visibility |
|---|---|---|---|
| Personal | userId | You | You only |
| Organization | organizationId + createdByUserId | The organization | Members with the visibility permission chosen at creation |
| Project | organizationId + projectId + createdByUserId | The project | Members with project access |
The author (createdByUserId) is a history marker. It's not an access control mechanism — a project is owned by the project, not by its author.
Picking the level at creation
When you create an item, you pick its scope:
- Personal: available only if you're not in an active organization, or if you explicitly mark it private
- Organization: all organization members get access according to the default permission (VIEW, EDIT, or MANAGE)
- Project: restricted to members with access to the selected project
Default permission for organization content
When you create organization content, you pick the default permission for other members:
- VIEW — can see but not edit
- EDIT — can see and edit
- MANAGE — can see, edit, and reshare
The creator always has MANAGE, regardless of the default permission.
Lifecycle
| Action | Consequence |
|---|---|
| Member leaves the org | Their organization content stays; personal shares are removed |
| Team deleted | Shares targeting that team are removed; content stays |
| Project deleted | All project content is deleted |
| Organization deleted | Everything is deleted |
Teams don't own
Teams only serve for sharing and filtering. Content is always owned by a user, an org, or a project — never by a team.