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. Answer three questions
On Onboarding, answer three questions about you and your work. Para then creates your organization, named after you, and sends you an introduction by email. Rename it and change its address in Settings.
3. Meet Para
After signup, Para opens on the Work page. Ask a question, or attach your own documents and say what you need. The files go to your Desk; with the case.dev plugin, Para files them in the project they concern before doing the work. Para's result appears in the same conversation, where you can ask for a revision. You can also send work by email, or through Slack or Teams once your organization connects them in Integrations. To start from your own documents, use the status update guide.
4. Build on the first result
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.
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.
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.