Skip to content
All documentation

Client guide

Using Sufrone Client Workspace

Detailed guidance for navigating the workspace, understanding statuses, responding to work, and keeping the client record accurate.

10 minute readClient · Operator

Account creation and sign-in

A new organisation can create a controlled prospect workspace from Get Started. The account owner verifies access through a single-use email link. Registration never joins an existing client automatically and never activates products, hardware, hosting, billing, or production access.

Returning users request a fresh passwordless sign-in link using their account email. The link is valid for 15 minutes, can be redeemed once, and is exchanged for a separate 12-hour browser session. The public response does not disclose whether an address is unknown, duplicated, revoked, or attached to an existing workspace; contact Sufrone when reconciliation is required.

Overview and attention

Overview deliberately summarizes rather than duplicates every record. Counts and balances link to the workspace that owns the underlying data. Needs attention is the recommended queue for a returning client because it prioritizes decisions, responses, payments, and delivery dependencies.

A zero value means no current record requires that type of action; it does not mean the account has never contained that record type.

Products, systems, and operational health

Within Products & systems, requested products and capabilities remain separate from active subscriptions and managed systems so registration or intake cannot become an accidental purchase. A product is active only through the controlled commercial and delivery workflow.

Product state and health state are separate: an active subscription can still have a stale health signal, and a fresh health signal is evidence of the last observation rather than a promise of uninterrupted availability.

  • Use version and drift information to understand whether the observed system matches the desired release.
  • Treat stale health as unknown current state, not as an outage and not as proof of availability.
  • Open Support when a product needs investigation; do not use an invoice dispute to report a technical incident.

Support

Support requests should describe the impact, affected users, when the problem began, what changed, and any safe evidence available. Priority reflects operational impact and entitlement rules; it should not be inflated to obtain faster handling.

The workspace records replies, attachments, state transitions, service-level clocks, time entries, escalation evidence, and satisfaction feedback. Waiting for client means Sufrone needs information or action before work can continue.

Billing and documents

Commercial documents explain what is offered and accepted. Billing records explain what is invoiced, paid, credited, refunded, disputed, or still outstanding. Keeping these domains separate prevents a later price change from silently rewriting an accepted proposal or issued invoice.

Delivery

Delivery contains the controlled handoff from accepted proposal to kickoff, onboarding, work orders, projects, milestones, tasks, risks, changes, approvals, and completion. A task may be client-visible without exposing internal-only operational notes.