Skip to content
DocsOpen Para

Getting started

Get your first result, show Para what you would change, and build an approach you can use again.

Updated October 2026
On this page

You can give Para useful work before you have taught it your preferences. Start with a real assignment, then reply with what you would change. Para can carry saved guidance into later work; a configured schedule lets it take on a recurring responsibility. This guide gets you set up, and Working with Para over time explains what carries forward.

1. Create your account

Go to Sign up and create your account with your work email. Open the verification link in your inbox within an hour; it verifies your address and signs you in.

2. Name your organization

On Onboarding, give your organization or team a name. Para creates your organization and sends you an introduction by email.

3. Meet Para

The welcome screens introduce Para and let you send a first assignment on your own documents: add them and say what you need. The files go to your Desk. If your organization has no plan yet, the screens first ask an administrator to choose one on the Plan page. With the case.dev plugin, Para files them in the project they concern before doing the work. No document handy? Ask Para a question instead. Para's result appears on the same screen, where you can send a revision. The last step shows where to send your next assignment: the Work page, email, Slack, or Teams. To see the screens again later, open Welcome. You can also start with your own documents using the status update guide.

4. Build on the first result

  1. Request a status update

    Name the work and the documents to use. Ask for a short update with sources and questions that need your judgment. Review the result against the source material before relying on it.

  2. Change the emphasis

    Reply: “Lead with deadlines and decisions I need to make, then explain what changed.” Ask Para to revise the update. If this is how you want future updates handled, ask it to save that method for your future status updates and show you what it saved. A revision alone is not confirmation of saved guidance.

  3. Give Para a recurring responsibility

    Once the approach works, ask for a weekday update by email. Specify the time, timezone, source documents, and what counts as a material change. Check the saved assignment and next run in Automations; discussing a schedule does not activate one. The status update guide follows this through to the next update.

Documentation