> For the complete documentation index, see [llms.txt](https://wiki.solids.group/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.solids.group/tools-and-resources/termin.md). # Termin Termin is the Solid Mechanics Group's project management system. It is designed for academic work, where one person may be coordinating research projects, papers, students, classes, proposals, reviews, travel, and administrative tasks at the same time. Use Termin for work that needs to be tracked, assigned, discussed, or revisited. It is especially useful when a task has an owner, a due date, a dependency, a collaborator, or a record of discussion that should not disappear into email or chat. {% hint style="info" %} Termin is available at [termin.solids.group](https://termin.solids.group). Use your group account or a connected Google, GitHub, or Microsoft account if those login options have been enabled for you. {% endhint %} ## The Basic Model Termin is organized around a few core objects:


Projects	Large units of work, such as a paper, code project, proposal, student research effort, class, or administrative responsibility.
Groups	Subsections inside a project. Groups are useful for milestones, paper sections, experiment batches, class modules, or categories of related tasks.
Tasks	Specific work items. Tasks can have due dates, assignees, status modes, descriptions, comments, links, attachments, prerequisites, and calendar behavior.
Teams	Reusable sets of people. Teams can be invited to Termin and shared onto projects so that access management does not have to be repeated one user at a time.
Direct Spaces	One-on-one spaces for work shared between two people. These are useful for advisor-student task lists, private follow-up, and lightweight direct collaboration.

The most important habit is to put work in the smallest useful container. A paper should usually be a project. Major paper components can be groups. Individual actions should be tasks. ## Main Views Termin has two main working views.


Tree	The structured project view. Use this when creating projects, arranging groups, editing task details, reviewing discussions, moving work around, or planning a project from top to bottom.
Todo	The personal action view. Use this when deciding what to do next. It collects tasks across projects and lets you filter by project, group, assignee, and completion state.

In practice, use Tree to organize work and Todo to execute work. ## Projects, Groups, and Divisions Projects are the main containers in Termin. A project can stand alone or be placed inside a division. Divisions are sidebar organization labels, such as research areas, teaching, administration, or sponsor categories. Use groups when a project has meaningful internal structure. For example: * A paper project might have groups for `Simulations`, `Figures`, `Manuscript`, `Coauthor Review`, and `Submission`. * A student research project might have groups for `Onboarding`, `Literature`, `Implementation`, `Validation`, and `Writing`. * A class project might have groups for `Lectures`, `Assignments`, `Exams`, and `Grading`. You can drag projects, groups, and divisions to reorganize the sidebar and tree. Right-click project, group, or division headers for actions such as rename, duplicate, delete, move, color, share, or promote. {% hint style="warning" %} Deleting a project, group, or task removes its working context. Prefer renaming, moving, completing, or archiving through project organization unless you are sure the item is no longer needed. {% endhint %} ## Creating Work Create work directly where it belongs: 1. Open Tree. 2. Create or select the relevant project. 3. Add groups if the project has structure. 4. Use the `New task...` row in a project or group table. 5. Add a due date, assignee, status mode, description, links, or comments as needed. For quick capture, it is acceptable to create a task first and refine it later. Do not wait for a perfect project structure before recording real work. ## Tasks A good Termin task should be specific enough that the assignee can tell when it is done. Prefer task names that start with an action verb: * `Draft introduction paragraph on loading protocol` * `Run mesh convergence case for 128 x 128 grid` * `Send travel reimbursement receipt` * `Review Figure 3 caption` Avoid vague task names: * `Paper` * `Simulation` * `Look at this` * `Stuff for Friday` Each task can include:


Title	The short action statement that appears in tables and todo lists.
Due	No date, a specific date, ASAP, or a date relative to another task.
Status	Open, critical, complete, percentage complete, multi-user status, or poll response state.
Assign	One or more users or email collaborators responsible for the task.
Description	Longer instructions, context, Markdown, and MathJax when useful.
Links	URLs related to the task, project, or group.
Attachments	Files that need to stay with the task context.
Discussion	Comments, decisions, questions, and update history.

## Task Settings Open the task settings drawer with the button beside a task. This is where most advanced task behavior lives. Use settings for: * changing task type between a normal task and a poll task; * choosing a status mode; * assigning users, collaborators, project members, or group members; * adding prerequisites; * setting start dates and due behavior; * locking a task after it should no longer be edited; * changing calendar and notification behavior. The drawer also contains the task discussion and, for poll tasks, poll configuration. ### Setting an Assignee and Status Mode


Single Status	The entire task is either open, critical, or complete. If there is more than one assignee, any of them may change the status of the task.
Multi-Status	Each user individually sets a personal status for the task. This makes sense for tasks like "Review and approve manuscript" or "Submit travel authorization".
Percentage	Similar to single status but allows any user to specify a percentage rather than a discrete status. This makes sense when working on tasks in the Gantt chart view.
Poll	The task asks assigned users to choose from a configured set of options. This makes sense for scheduling, approvals, preferences, and lightweight decisions.

Use the simplest status mode that accurately describes the work. Most tasks should be Single Status. Use Multi-Status only when each assignee must independently finish the task. ## Dates and Planning Termin supports several due-date patterns.


No Date	The task is tracked but not scheduled. Use sparingly, because undated work is easy to ignore.
Date	The task is due on a specific calendar date.
ASAP	The task should be treated as urgent even without a precise date.
Relative	The task is due a specified number of days before or after another task.

Relative dates are useful for project plans with dependencies. For example, `Send draft to coauthors` might be due two days after `Finish first complete manuscript draft`. If a project has a start date and end date, Termin can show a Gantt-style planning view. Percentage status works well in that view because it communicates progress without forcing a binary complete/not-complete state. ## Assignments and Collaborators Tasks can be assigned to Termin users or to outside collaborators by email. When an outside collaborator is assigned, Termin can send a link that lets them view and update their assigned task without needing full project access. Assignment badges show who is responsible and whether an emailed assignment link has been sent, accepted, or denied. Use assignees intentionally: * Assign a task to the person who is expected to act. * Use followers when someone needs awareness but is not responsible. * Use group or project-member assignment when everyone in a defined group must respond. * Avoid assigning a task to many people if only one person owns the next action. ## Teams and Sharing Teams are reusable groups of Termin users. Create a team when the same people need access to several projects. Projects can be shared with individual users or with teams. Shared users can see the project in Termin and participate according to the access they are given. Use teams for stable groups, such as: * a research subgroup; * a class staff team; * a proposal writing group; * a recurring collaboration. Do not use teams as a substitute for task assignment. Sharing gives access. Assignment creates responsibility. ## Direct Spaces Direct spaces are one-on-one project spaces. They are useful when two people need a private shared task list without creating a full research project. Common uses include: * advisor-student follow-up; * weekly one-on-one action items; * private reminders between two collaborators; * small administrative exchanges that still need tracking. Direct spaces can contain the same kinds of tasks, due dates, comments, and statuses as regular projects. ## Discussion and History Use the discussion button to keep task-specific conversation attached to the work. Comments support Markdown-style writing and user mentions. Discussion is better than email when: * the comment only matters in the context of the task; * a decision should remain visible to future project members; * the task status depends on a question or clarification; * you need a record of what changed and why. Termin also records update history for many changes, such as status, assignment, due date, title, project, group, and description edits. This makes it easier to understand how a task reached its current state. ## Notifications Termin can notify users about comments, assignments, task updates, project sharing, and related activity. Notifications appear inside the app, and browser push or email notifications may be available depending on your account settings. Use notification settings to control how much Termin interrupts you. A reasonable default is: * keep assignment and mention notifications enabled; * keep comment notifications enabled for active projects; * reduce email frequency if you already check Termin regularly; * use pinned notifications for items that should remain visible until handled. If notifications seem missing, check browser permission settings, account notification preferences, and whether you are assigned to or following the relevant task. ## Poll Tasks A poll task asks assignees to choose from a set of options. Polls can allow one response or multiple responses. Results can be visible to everyone or limited depending on the poll settings. Polls are useful for: * scheduling a meeting time; * choosing between manuscript title options; * collecting approval from multiple people; * asking group members to select a preferred task, date, or resource. Use a poll task when the real work is a decision or response. Use a normal task when the real work is an action. ## Prerequisites Prerequisites define task dependencies. If a task depends on another task, add the earlier task as a prerequisite. Termin can show dependent tasks as blocked until prerequisites are complete. Good prerequisite examples: * `Plot final stress-strain curves` depends on `Finish production simulations`. * `Send paper to coauthors` depends on `Complete Figure 2`. * `Submit reimbursement` depends on `Receive hotel receipt`. Do not create dependencies for every small ordering preference. Use prerequisites when completing the later task before the earlier one would be genuinely wrong or confusing. ## Locked Tasks Lock a task when its content should no longer change casually. This is useful for finalized decisions, completed review records, or tasks that are being used as stable prerequisites. Locked tasks should still be understandable from their title, description, links, and discussion. Add any missing context before locking. ## Links and Attachments Projects, groups, and tasks can store links. Use links for resources that live elsewhere: * Overleaf projects; * GitHub repositories, issues, and pull requests; * Google Drive folders; * manuscripts, forms, or shared documents; * HPC job pages or dashboards; * relevant papers and references. Attachments are better for files that should be preserved with the task itself. Links are better for living resources that will continue to change. ## GitHub Sync If your GitHub account is connected, Termin can sync assigned GitHub issues and pull requests into a Termin project. GitHub items are grouped by repository and include links back to GitHub. This is useful when code review, bug fixes, and software tasks should appear beside research and writing tasks. Treat the GitHub-linked Termin task as a tracking mirror; use GitHub for the technical discussion that belongs in the issue or pull request. ## Calendar Integration Termin can create calendar events for tasks with due dates when calendar integration is enabled. This is most useful for deadline-driven work and external collaborators who rely on calendar invitations. Calendar behavior depends on account connection and opt-in settings. If a task does not appear on a calendar, check: * whether the task has a due date; * whether the relevant user or collaborator opted in to calendar events; * whether a Google account is connected; * whether the task was created before calendar settings were enabled. ## Group Templates Group templates let you reuse common task lists. They are useful for recurring workflows, such as onboarding a student, preparing a paper submission, setting up a simulation campaign, or running a class module. Use templates for repeated structure, not for one-off plans. A good template contains tasks that are likely to appear every time the workflow occurs. ## Finding Work Use the Todo view and filters to narrow the active task list. Useful filters include: * only tasks assigned to you; * only tasks in a selected project, group, direct space, or team area; * incomplete tasks; * tasks by due date or urgency. In the Tree view, use project and group structure to find the source context. In the Todo view, use filters to decide what to do next. ## Suggested Workflows ### Weekly Research Meeting 1. Open the student's direct space or research project. 2. Review incomplete tasks from the previous week. 3. Mark finished work complete. 4. Add new tasks during the meeting. 5. Assign each task and give it a due date when appropriate. 6. Use comments for decisions that should remain attached to the task. ### Paper Management 1. Create a project for the paper. 2. Add groups for major work areas, such as simulations, figures, manuscript, coauthor review, and submission. 3. Link the Overleaf project, repository, Drive folder, and important references. 4. Use prerequisites for tasks that block later work. 5. Use multi-status tasks for coauthor review and approval. 6. Use comments to record decisions about scope, figure choices, and submission plans. ### Proposal or Deadline-Driven Project 1. Set project start and end dates. 2. Add groups for major deliverables. 3. Use due dates and relative due dates for backward planning. 4. Use the Gantt view when the schedule matters. 5. Assign each deliverable to a clear owner. 6. Review the Todo view regularly for overdue and ASAP work. ### Group Request or Decision 1. Create a poll task. 2. Assign the relevant users or group members. 3. Add a clear question and options. 4. Choose whether multiple responses are allowed. 5. Use the discussion for context or follow-up. ## Good Termin Hygiene Termin works best when the group keeps tasks clear and current. * Create tasks for real work, not vague intentions. * Put tasks in the right project or group before they become hard to find. * Assign a task only when someone is responsible for action. * Use due dates for work that is actually time-sensitive. * Close the loop by marking completed tasks complete. * Add links instead of asking people to search old messages. * Use comments for decisions and context that future readers will need. * Avoid using one giant task as a substitute for a project or group. ## Troubleshooting

Problem	What to check
I cannot see a project.	Confirm that the project was shared with your Termin account or with a team you belong to. Also check whether you are looking in Tree, Todo, Direct, or Teams.
A task is not in my Todo view.	Check filters, assignee selection, completed-task visibility, project selection, and whether the task is assigned to you or only shared with you.
I cannot edit a task.	The task may be locked, you may not have permission for that project or group, or you may be viewing a shared project with limited access.
A due date looks wrong.	Check whether the task uses a fixed date, ASAP, or a relative due date. Relative dates depend on another task.
Notifications are missing.	Check browser notification permission, Termin notification preferences, assignment/follower state, and whether the relevant task or project is shared with you.
A calendar event did not appear.	Check that the task has a due date, the user or collaborator opted in to calendar events, and the relevant Google account is connected.
A collaborator cannot open a link.	Resend the assignment link and confirm that it was sent to the correct email address. If the collaborator has a Termin account, make sure the email matches their account or verified email.

## When Not to Use Termin Termin is not meant to replace every tool.

Use this instead	When
GitHub	For code review, technical issue discussion, pull-request history, and repository-specific decisions.
Overleaf or Docs	For writing the actual manuscript, proposal, lecture notes, or document text.
Data repositories	For storing simulation data, publication results, and reproducibility artifacts.
Chat	For ephemeral conversation that does not need to remain attached to a task.
Email	For formal external communication, official notices, and communication with people who cannot use Termin links.

The useful pattern is to use Termin as the coordination layer: it should point to the right repository, document, data location, or external conversation and make clear what action is needed next. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://wiki.solids.group/tools-and-resources/termin.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.