Getting started · 4 min read
A free note-sharing workflow with text, links and a project PIN
Start with one free project, text-and-link notes, published versions and recipient feedback while understanding the plan's actual limits.
Written with AI assistance and checked against Draftnod’s product workflow. Examples are illustrative.
A first note-sharing workflow should be small enough to understand completely. You do not need to move every document or invite every collaborator at once. One project, one focused note and one recipient can show whether the structure suits your work.
Draftnod's Free plan provides a way to try the existing brief, draft and review process using text and external links. This guide explains a practical starting pattern and its limits without implying that Free includes unlimited projects, unlimited tasks or new image uploads.
Choose a low-risk first note
Pick information that is useful to share but simple to review: workshop instructions, a study-group plan or a short project handoff. Avoid sensitive material for your first test.
Write the next action in the title. “Review the equipment list” gives the recipient a clear purpose. “My notes” leaves them guessing.
The personal-notes guide helps turn a rough note into a shareable record before you open the workspace.
Understand the Free plan boundaries
Free includes one active project and up to 20 open tasks. It supports text and external-link drafts, project access through a link and PIN, and the existing comments and approval workflow.
Free does not include new image uploads. Linked files remain in their original service, where their access permissions still apply.
Check the pricing section for the current plan presentation before choosing a plan. Existing images remaining viewable after a downgrade should not be confused with permission to upload new ones.
Create the recipient and project
The owner creates a Draftnod account and workspace. Use Add client for the person or group receiving the note, then create a project under that record.
Set the project's six-digit PIN using the existing controls. Keep it private and choose a project name the recipient will recognize.
These labels describe the existing workflow. A recipient can be a collaborator, customer, study group or someone you know; using a broader scenario does not change the underlying records or permissions.
Add a task with a clear brief
Use Add task to record the note's title, purpose and any relevant deadline. Keep the brief focused on what the recipient needs to understand or decide.
If the recipient submits a request from the portal, it remains pending until you accept it. That boundary helps you review the scope before taking on work.
The clear brief guide provides a compact template with audience, scope and acceptance criteria.
Save the text or link as a draft
Use Add draft and enter the note's text or an external deliverable link. Include a caption that explains what the recipient should inspect.
Save draft keeps the version unpublished. Review the wording, dates and links before choosing Publish.
For an external file, name the destination and confirm that the intended recipient can access it. The links and images guide explains why the project PIN does not grant access to that source service.
Publish and invite one recipient
Publish the version that is ready for review. Copy the project's portal link and send it with the note title and the requested action.
Share the PIN privately. The recipient opens the link and enters the PIN without creating a Draftnod account.
A useful invitation says:
Open the equipment project and review “Workshop equipment list”, version 1. Please comment if an item is missing or unclear. I will share the six-digit PIN privately.
The invitation is more useful than a bare link because it tells the recipient where to look and how to respond.
Collect a specific correction or decision
Ask for feedback that identifies a section and desired result. If a detail is missing, the recipient can leave a comment in context.
When a published version is awaiting a decision, the existing portal controls let the recipient approve it or request changes and save the decision. A positive comment does not necessarily mean the whole note has been accepted.
Read the feedback guide and the approval workflow guide to choose the right response pattern for your note.
Publish a revision with a change summary
Create a new version when the note changes substantively. Say what changed and what still needs review.
Keep the task stable so earlier comments remain understandable. The version history guide explains why a new version is clearer than creating a duplicate “final” task for every edit.
For your first test, ask whether the recipient can identify the current version and the next action without help.
Decide whether a paid plan is needed
Choose a paid plan when the actual limits matter: additional active projects, more open tasks or image uploads. Do not upgrade merely because the first workflow feels incomplete; the missing piece may be clearer instructions or better organization.
Standard and Pro have different project, task and storage capacities. Use the displayed plan details to match the choice to your actual usage.
Keep the first workflow readable
Use clear headings, short paragraphs and descriptive links. W3C's accessible writing tips provide useful guidance for the note itself.
Open your workspace and start with one free project and one text-and-link note. The first success is a recipient who can enter the project, understand the note and respond to the intended version.
