Question 1

What happens when I create a workspace?

Accepted Answer

When a signed-in user creates their first workspace, Wardenry assigns that user’s existing operating records to it, including customers, locations, technicians, inventory, jobs and their labor, parts, expenses, revenue, invoice and payment references, time entries, and import templates. This is an application data assignment; it does not establish legal ownership of those records.

Question 2

Who can read and change workspace records?

Accepted Answer

A workspace member can read workspace data. The owner, admin, manager, and dispatcher roles can write through the workspace APIs. Other member roles are read-only. These are the permissions implemented in this checkout.

Question 3

Who can invite people, and how is an invitation accepted?

Accepted Answer

Only the workspace owner can list, create, or revoke invitations. To accept one, the person must be signed in with a verified account whose email matches the invited email, and the invitation must still be pending, valid, and unexpired. An account that already belongs to a workspace cannot accept an invitation to another workspace.

Question 4

What information does a job connect?

Accepted Answer

A job connects a customer and location, an optional technician, status, priority, SLA details, and schedule details. Workspace-scoped job records can include labor, parts, expenses, revenue, invoice references, payment references, and time entries. When a job status changes, its history records the previous and new status plus the acting user’s id and name.

Question 5

Do job financial summaries confirm that money was collected?

Accepted Answer

No. Summaries are calculated from the revenue, labor, parts, expenses, invoice references, and payment references entered in the workspace. They do not prove collection, settlement, reconciliation, or processing by a payment provider. Example metrics and import mappings shown in marketing material are examples, not live company records.

Question 6

What do Current, Beta, and Planned mean?

Accepted Answer

Current means the workflow is implemented in this code checkout; it does not mean production behavior was checked. Beta means code is wired but activation or delivery is unverified. Planned means the capability is not available in this checkout, and no delivery date is promised.

Question 7

Which import workflows are available in this checkout?

Accepted Answer

CSV import is Current. XLSX, QuickBooks, PDF, and general API imports are Planned and are not available in this checkout. Sample mapping values are examples, not live mappings or imported company data.

Question 8

What is still in Beta?

Accepted Answer

War Room AI, proxy-backed email, and conditional Google sign-in are Beta: code is wired, but provider activation, deployment credentials, and delivery have not been verified here. Beta is not evidence that any external service succeeded in production.

Question 9

What is Planned?

Accepted Answer

XLSX, QuickBooks, PDF, and general API imports, offline field tools, and payment processing are Planned. They are not available in this checkout, and no delivery dates are promised.

Question 10

Can visitors see customer or workspace records on this page?

Accepted Answer

No. This public Help page contains general product information and does not read or expose workspace records. Workspace APIs require an authenticated workspace membership.

A clear guide to your workspace and jobs.

What each status means

In this checkout

Wired, activation unverified

Not available here

Common questions

Ask about a pilot or demo.