Nia documentation · Latest
Sharing and households
Understand personal ownership, direct invitations and household ownership for projects, shopping lists and cookbooks.These instructions describe sharing in the Nia V4. Nia uses the same ownership model for Tasks projects, Shopping lists and Recipes cookbooks. Workspaces remain personal Tasks organization.
Choose a way to share
| Arrangement | Owner | Who gets access |
|---|---|---|
| Personal container | One person | The owner and accepted direct recipients |
| Household container | One household | The household’s accepted participants, plus any independently retained access sources |
| Personal workspace | Its account | A personal view of Tasks, not a shareable container |
A project, shopping list or cookbook has exactly one owner: a person or a household. Transferring a personal container into a household changes ownership. It does not add a household share alongside continued personal ownership.
Invite someone directly
For a personally owned project, list or cookbook that you manage:
- Open its details and sharing controls.
- Invite an existing user by username or an eligible verified email address.
- The recipient accepts or declines the invitation in their account.
- After acceptance, the container appears with their accessible content.
A pending invitation is not permission to read the container’s content. Removing a recipient ends that direct access source.
Direct invitations are managed for personally owned containers. A household-owned container gets household access through membership; you cannot add new direct shares to it through these controls.
Existing task-project shares remain usable when upgrading to V4.
Create or join a household
Open Household in account settings. Create a household, or accept an invitation sent by its leader.
A household has one leader and accepted members. An account can have only one active household relationship, including a pending invitation. Decline or resolve an existing relationship before joining another household.
The leader can invite or remove members and transfer leadership. A member can leave. The leader must transfer leadership or dissolve the household instead of simply leaving it.
Joining a household does not publish all your existing content. Personal projects, lists and cookbooks stay personal until you deliberately transfer ownership or share them directly.
Create or transfer household content
Household participants can create content owned by the household where the module offers that choice. The household leader manages the resulting containers.
If you own a personal project, list or cookbook, use its ownership control to transfer it to an available household. Check the confirmation: the entire container and its children will follow the new access boundary.
For Tasks, a transferred project subtree is kept together and detached from an incompatible personal parent. The special Inbox cannot be transferred to a household.
Household-owned projects appear in each participant’s default personal workspace. They cannot be relocated to another personal workspace. Shopping lists and cookbooks do not use workspaces at all.
Editing is different from management
| Action | Accepted participant | Personal owner or household leader |
|---|---|---|
| Read permitted content | Yes | Yes |
| Add or edit tasks, shopping items or recipes | Yes | Yes |
| Manage container name and appearance | No | Yes |
| Manage direct access or container ownership | No | Yes |
| Delete the container | No | Yes |
Content editing includes the module’s permitted child operations. It is not a read-only sharing mode. The owner-only management boundary applies to the top-level project, list or cookbook, rather than making each child independently owned.
Tasks, subtasks, comments and attachments inherit their project access. Shopping items, sections and stores inherit their list access. Recipes, ingredients, steps and images inherit their cookbook access. Moving content across containers can therefore change who can see it.
Nia does not offer public recipe discovery or a cookbook archive lifecycle in this version.
Personal workspaces are separate
A Tasks workspace is not a household. Inviting someone to a project does not invite them to your other projects or workspace. A recipient’s placement of a directly shared project is their own organization choice.
The Inbox belongs to its personal workspace. It cannot be deleted, moved to another workspace or transferred to a household. Use a regular project for shared household organization.
Leaving, removal and dissolution
Leaving a household or being removed revokes that membership’s access. Household-owned data remains with the household; it is not deleted because its original creator leaves.
Access sources can overlap. For example, someone may retain a compatible independent project share after their household membership ends. Removing one relationship does not revoke another relationship that still grants access.
If the leader dissolves the household, its owned containers transfer to the leader’s personal ownership. The data is not simply discarded. This operation also removes existing direct grants and legacy project memberships on those household containers. Former participants lose access to them; the new personal owner can invite people again afterward.
An ownership change is different from copying data. Review it carefully before confirming.
Files, images and copied ingredients
An accessible task attachment can be read by participants even if their own account cannot upload files. The uploader’s allowance is charged only while they retain access; no replacement charge is assigned to other participants when that access ends. Reacquiring access makes their retained uploads count again.
Recipe title images are private recipe data and do not use the task attachment allowance. They follow cookbook access.
Ingredients copied to a Shopping list become list content. Their copied names, quantities and notes can remain visible to list participants who cannot access the source cookbook. A source-recipe link is only available when source access permits it.
Offline access changes
Sharing, invitations and ownership changes need a server connection. When a client reconnects, it reconciles permissions and removes inaccessible cached content and pending operations as appropriate.
An offline copy is not a separate permission grant. If access has changed, saved destinations in Memory cannot restore access or authorize a write.