Skip to main content

Getting Started

Praxsys helps teams plan project work, coordinate execution, and review outcomes in a shared workspace.

This documentation covers the current closed-alpha product surface. It focuses on the workflows users can see in the app and leaves private engineering details out of the public docs.

First Steps​

  • Accept your workspace invite, or follow the guided signup path when it is available to your account.
  • If you are joining from an invite, sign in with the email address that received the invitation and open the linked workspace or project.
  • If you are creating a new workspace, provide the required workspace details, skip optional business context if you do not need it, and enter Project Work when setup completes.
  • Use Plan for requests and planning documents.
  • Use Work for active tasks.
  • Use Review for ready and approved work.
  • Use comments, Quick Replies, mentions, watchers, attachments, and Journal entries to keep context close to the work.

Current Docs​

  • About Praxsys explains the product philosophy, context model, and where Praxsys fits among other work software categories.
  • Workspaces covers workspace entry, invites, switching, and account settings.
  • Projects explains the Plan, Work, and Review model.
  • Plan Documents covers planning documents and document details.
  • Plan Requests covers guest work requests and manager request handling.
  • Work covers active task execution.
  • Review covers validation and approval.
  • Team covers project access, Project Leads, and member types.
  • Collaboration covers comments, Quick Replies, mentions, bookmarks, watchers, attachments, and Journal entries.
  • Notifications covers in-app notifications and project/task email notification controls.
  • Branding covers workspace identity and branded transactional emails.

Documentation Style​

Public docs should stay short, plain-language, and focused on what users can do. Private engineering notes belong outside this site.