Understand where Workdesk fits.

Workdesk fits organizations where maintenance supports the operation rather than being the product sold to customers. It is especially useful when many locations or reporters depend on a smaller group of coordinators and technicians, and the organization needs ownership, evidence, costs, and service history to survive beyond calls and group chats.

Open requests are easy to lose, people repeatedly ask who is handling an issue, photos and receipts become separated from the work, supervisors need different queues, technicians revisit equipment without useful history, or management reconstructs activity manually from messages. Workdesk gives those events one attributed record.

No. A single technician, a small internal team, mixed employees and contractors, or several category supervisors can use the same workspace. Roles, locations, and responsibility profiles limit clutter without charging per ordinary member.

Choose a full CMMS or EAM when regulated asset hierarchies, warehouse valuation, procurement, production-line integrations, or mandatory complete asset records are central requirements. A field-service business may need a service ERP when quotations, customer contracts, route optimization, payroll, and invoicing are its primary workflow. Workdesk is also not an emergency dispatch system or a substitute for qualified safety procedures.

Location staff report faults and see local progress. Category coordinators separate general facilities from specialized equipment, technicians record each visit and expense, and authorized managers approve completion. Owners compare open work and spending across locations without reading every conversation.

A landlord or property manager creates an expiring request link or lobby QR code so tenants can report without installing the app. Requests enter the building's normal queue, where staff or contractors are assigned. The link can expire or be replaced without deleting existing tickets.

Staff use location-specific links or member accounts to report facilities and service-equipment problems. The maintenance team receives location, access, contact, and evidence context while supervisors retain oversight. Safety-critical and clinical emergencies must continue through the organization's dedicated emergency procedures.

A small facilities team can coordinate repairs across many sites, preserve vendor or technician evidence, schedule repeat inspections, and build lightweight equipment history as reliable details become available. Occasional reporters can use request links while regular managers retain ongoing visibility.

Yes. Use the same verified email and choose the needed workspace after signing in. Membership, role, and location access are separate in each workspace.

No. Owners can generate location-specific, expiring request links or QR codes for occasional reporters. Registered members should use the app or desktop mode when they need ongoing visibility.

Your role or owner-assigned locations limit what you can access. This keeps large organizations useful and protects unrelated operational records.

A healthy authenticated session persists. A new code may be required after sign-out, session expiry, security changes, account removal, app-data clearing, or a new device.

When workspace rules and the ticket state allow it, an authorized owner or supervisor can record a confirmed remote resolution. The action and actor remain in the history.

Yes. Postpone it with a reason, then repeat On the way and arrival on the next visit. The original report and every visit remain together.

Authorized removal deletes its media and leaves an audit entry naming who removed it, when, and why. Use removal only for wrong or obsolete records, not completed work.

Yes. Responsibility profiles route selected categories to a primary and backup coordinator, evidence reviewer, and eligible field team.

No. If location logging is enabled, Workdesk stores snapshots for shift and ticket events such as arrival. The daily map displays those recorded points, not a continuous route.

The original remains in the device photo library. Workdesk uploads an optimized WebP copy so details remain useful without consuming unnecessary hosted storage.

Some actions can wait locally and sync after reconnection. The app shows pending changes. Do not clear app storage or uninstall while evidence is waiting to upload.

No. Equipment memory is optional and can begin with only a location and recognizable name. Add details during future service when they help decisions.

Yes. The first workspace of an eligible verified owner automatically receives one free 30-day introductory month. It includes every workflow and 1 GB of shared file storage. No payment method is required, and it does not renew or charge automatically. After it ends, the workspace is parked for 30 days so the owner can subscribe or export before scheduled deletion.

Owners and billing administrators use Settings or the owner portal. Android purchases use Google Play Billing; web subscriptions use Stripe.

The workspace may become restricted while data is retained for the period described in the Terms and Privacy Notice. Current policy provides three months before scheduled deletion, subject to legal obligations.

Verified deletion enters a one-month retention window with an export option before scheduled deletion, subject to audit, legal, fraud-prevention, and tax obligations described in the policies.

No. The Android app can host a desktop-friendly session on the local network for managers who prefer a PC. The phone remains the host and indicates that state.