Board 2.0 User Manual

Board 2.0 is a lightweight project workspace on CryoSim. Create projects, group people into teams via shareable join codes, classify work into categories, and assign tasks with due dates, recurrences, and per-task privacy.

1. What is Board 2.0?

Board 2.0 lets you:

Create projects that only you own and manage.
Invite other CryoSim users into teams using short, regenerable join codes — no email lookups, no user directory.
Organise work into categories and decide which teams can access which categories.
Create tasks with an assignee, optional due date, recurrence (daily/weekly/monthly/yearly), and a visibility setting.
Let assignees mark tasks complete — one-time tasks close out, recurring tasks auto-advance to the next cycle.

The actors

Owner

The user who created the project. Has full access to teams, categories, members, and all team-visible tasks.

Member

Any user who joined a team via its join code, after approval. Can see and add tasks in categories their team(s) have access to.

Assignee

The single person responsible for a task. Only the assignee can mark a task complete.

2. Getting started

Sign in to CryoSim and open Board 2.0.
Your dashboard shows two areas: My Projects (projects you created) and Shared with me (projects where you're a team member).
Use + Create Project to start your own project, or Join a Team → if someone has given you a join code.

Privacy by design Board 2.0 never exposes a user directory. You cannot search for or browse other users. Sharing happens only via codes that you generate.

3. Projects

Only the person who creates a project can manage it — including renaming, deleting, and configuring its teams, categories, and access.

Create: type a name on the dashboard and click Create Project.
Rename: click Rename on the project card, edit the name inline, click Save.
Delete: click Delete. This is permanent: all teams, categories, members, requests, and tasks are removed.
Open: click Open on a project to manage its teams and categories.

4. Teams & join codes

Inside a project, teams are how you group people. Each team has its own join code (format TES-XXXX) that you share with people you want to invite.

Managing a team

Add a team: in the project, type a team name and click + Add Team. A unique join code is generated automatically.
Rename / Delete: use the buttons on the team header. Deleting a team revokes every member's access immediately.
Regenerate code: click Regenerate next to the code. The old code stops working immediately — use this if a code has been shared too widely.

Approving members

When someone uses your code, they appear under Pending requests on the team. You can:

Approve to add them as a member.
Deny to discard the request.

Approved members are listed under the team's Members section. You can Remove anyone at any time.

You never browse other users The only time you see another user's name is when they have voluntarily submitted a join request — which means they chose to identify themselves to you for that purpose.

5. Joining a team

Get a join code from a project owner (e.g. TES-7H2K).
Open Board 2.0 and click Join a Team →.
Enter the code and click Look up. You'll see the project and team name.
Click Request to Join. The owner will be notified and must approve.

Once approved, the project shows up under Shared with me on your dashboard. Click Open to see the categories your team has been granted access to.

6. Categories

Categories classify work within a project — for example: Backlog, This sprint, Bugs, Marketing. They are managed only by the project owner.

Add: on the project page, type a name under Categories and click + Add Category.
Rename: click the Rename button on the category chip.
Delete: click the × button. All tasks inside the category are removed.

7. Category access for teams

By default, a new team has no category access. You — the project owner — decide which teams can see and contribute to which categories.

Open the project.
Inside each team's panel, find the Category access section.
Tick the categories you want this team to access; untick to revoke.
Click Save access.

Cascade effect When you delete a category, it's automatically removed from every team's access list. No orphan references.

8. Tasks

Open any category — as the owner from the project page, or as a member from your Shared with me entry — to see and add tasks.

Creating a task

The task form has five fields:

Field	What it means
Title	What needs doing. Required.
Assignee	The single person responsible. Choose yourself or anyone with access to this category (the owner plus members of teams that have category access). Only the assignee can mark it complete.
Due date	Optional. Leave blank for "no specific deadline".
Recurrence	One-time, Daily, Weekly, Monthly, or Yearly. Recurring tasks reschedule themselves on completion.
Visibility	Whole team (anyone with access) or only you (private).

Who can create tasks?

Any user with access to the category — that means the project owner plus members of any team whose category access includes this category.

Who can delete tasks?

The project owner can delete any task. Anyone else can delete only the tasks they created.

9. Task status & completion

Every task has one of three statuses: Open, In progress, or Done. Only the assignee can change the status — two buttons are available:

Set In Progress — appears when the task is still Open. Click it when you start working on the task; it switches to In progress and records when you started.
Mark Complete / Complete cycle — appears whenever the task is not already done. Behaviour depends on recurrence:
- One-time task: the task is marked Done, shown struck through, and moved to the bottom of the list.
- Recurring task: the next due date is set to today + one recurrence interval (daily/weekly/monthly/yearly), and the task stays in progress for the next cycle. Each completion is logged for audit.

Cycles are anchored to when you actually complete By default, the next due date is computed from today, not from the previous due date. So whether you finish early, on time, or late, the next cycle starts one interval from now.

"Fix Date" — per-task drift-free schedule Tick the Fix Date checkbox when creating or editing a task to override the default. Cycles on a Fix-Date task advance from due_date + 1 interval, keeping the task on its original calendar grid — useful for things like "submit monthly report on the 1st", where completing on the 3rd should still roll the next due to the following 1st, not the 3rd. If the due date is already in the past, the next due skips forward by whole intervals until it lands in the future.

10. Privacy & visibility

Each task carries a visibility setting chosen by its creator:

Whole team Team-visible (default): anyone with access to the category sees the task.
🔒 Private Only me: only the creator sees the task — not even the project owner. Use this for personal todos you want to track inside the project workspace without sharing.

About private tasks Because private tasks are hidden from everyone except the creator, even the project owner won't see them. If you assign a private task to someone other than yourself, that person can't see it either — so private tasks are best kept self-assigned.

11. FAQ

Can two teams share the same category?

Yes. Multiple teams can have access to the same category. Everyone with access sees the same task list (subject to per-task visibility).

What happens to my requests if the owner deletes the team or project?

Pending requests disappear with the team. Approved memberships are removed automatically — the project will no longer appear in your Shared with me.

Can I leave a team?

Not directly yet — ask the project owner to remove you. The owner can remove any member at any time.

Can a task have no assignee?

No — every task must have one assignee. If you're not sure who should own it, assign it to yourself and reassign by recreating later.

Can I edit a task after creating it?

Not yet. To change a task's assignee, due date, recurrence, or visibility, delete it and create a new one. (Editing may be added in a future update.)

Where is my data stored?

Each user's projects are stored in their own folder under projects/board2/data/users/<your-user-id>/. Join codes are indexed in a small global file so codes can be looked up without scanning every user's data.

Need something this manual doesn't cover? Use the Contact Us link on the CryoSim portal.