Actual SuprOS Home screen in private staging, with navigation and an idle composer.
SuprOS in private stagingA captured Home screen showing navigation and an idle composer. Available capabilities are confirmed for each organization.
  1. Start in SuprOS

    Name the task and bring the goal, sources, and constraints into a workspace.

  2. Prepare work to review

    Choose an available template or assignment. Inspect the proposed steps and the approval policy that applies.

  3. Move into the right area

    Prepare a content revision in SuprCMS or a reply in SuprInbox when those capabilities are enabled for your organization.

  4. Choose the next action

    Review the draft before deciding to send, publish, or approve further work. Opening a workspace and approving a task are separate steps.

  5. Keep the actual state visible

    Return to saved output and review the work, approval, and usage records. A draft or a pending record is not a completed result.

Private rollout

Access starts with an invitation.

Public signup is disabled. Request access through Support so we can discuss your work and confirm which workspace, publishing, and inbox capabilities are available to your organization.

Existing members continue through the dashboard login. A request for access does not enable an account or a feature.

One product shell

SuprOS, SuprCMS, and SuprInbox share the work's context.

The workspace keeps the project context nearby while you move between available work areas. Check the actual draft, approval, output, and usage state before continuing.

SuprOS

Keep project context, Knowledge, Documents, and saved output together as you plan the next task.

SuprCMS

Prepare site content and review the revision and its approval state before publication.

SuprInbox

Keep a message, its context, and a draft reply close to the work that prompted them.

Other work areas

Spreadsheets, Presentations, PDF, Web Artifacts, Applications, Computer, and Media are available according to your organization's rollout.

What Supr carries into the work

The work starts with context, not guesswork.

Useful help needs more than a message. Supr packages the run with the account, project, plan, autonomy, approval, and context needed to do useful work inside the right boundary.

The right project

The account, project, and team context needed to keep work in the right place.

What is included

Your plan, available work, and the limits that apply before a run begins.

Your guardrails

What Supr can do on its own and when it must pause for you.

The useful context

Your project description, relevant history, chosen template, and the details you provide.