Journee uses one marketplace for guests, customers, and vendors. A signed-in party can act as a customer by posting work and as a vendor by bidding; these are activities, not separate account types.
The public About page explains Journee's marketplace model and provides the same entry points to browse work, post a job, sign in, or create an account. It does not expose additional marketplace data or controls.
Browse available work
Open the Marketplace from the main navigation. Guests can browse without an account. Only jobs that are currently public, open, and unexpired appear.
The filter bar can narrow results by:
location or current location;
distance radius;
service category;
search text;
newest or oldest order.
On the marketplace page, use List or Card view. Apply saves the current selection for that browser surface. Clear removes it. If Journee cannot resolve the location, or an earlier location reference has expired, results are blocked and the page asks for a new location instead of silently searching from the wrong place.
Job rows and cards show a summary, the job's bounded set of category tags, and coarse location. A map link uses the displayed coarse postal or ZIP location. Journee does not disclose the service street address in the public marketplace.
Post or open a job
Post a Job starts the guest continuation flow when signed out and the authenticated job flow when signed in. Opening a marketplace job shows only the public projection. Exact address, private contact details, bid pricing, and private party data are not part of that projection. When you are signed out, job detail also does not show the poster's identity or rating.
Available service categories, property choices, policy deadlines, and provider availability come from the running Journee environment. The labels shown in the application are authoritative; this guide deliberately does not freeze those mutable values.
Use the signed-in dashboard
After sign-in and onboarding, Home opens the dashboard. Its tabs are the canonical workspaces:
Jobs — drafts and jobs owned by the party, including incoming bid and completion actions that are valid for the current job state.
Bids — bids the party submitted, with the job's categories, pricing, submitted time, and a link to the currently available workflow.
Subscriptions — service-category subscriptions and matching open jobs.
Archive — eligible completed work. Customer jobs can appear after completed closure; vendor work has additional review-based eligibility.
Empty and filtered-empty states are normal. Expired, cancelled, incomplete, or otherwise ineligible work is not presented as completed archive history.
Configure subscription matches
Subscription matching uses the party's Head office as its private origin. From the Subscriptions tab:
Set or correct the Head office from My Profile if the page requests it.
Set a matching radius from 1 km through the current policy maximum.
Add one or more current service categories.
Remove an unwanted saved category with its individual tag action.
When browser enhancement is available, a committed valid radius, category selection, or tag removal saves automatically and reports its progress. Typing or focusing a field alone does not save. The ordinary Save radius, Add subscription, and per-tag remove forms remain the no-JavaScript path.
A subscription can wait for location processing, become active, or be blocked when the origin cannot support distance matching. Clearing Head office pauses matching without erasing the saved category configuration. Journee never shows the private origin coordinates in marketplace results.
When a control is missing
Controls are state- and persona-aware. A customer action does not appear to an unrelated viewer, a vendor action does not appear before a qualifying bid, and terminal jobs lose editing controls. Refresh the canonical dashboard or order page before repeating a request after an error; a serious mutation error can leave the outcome uncertain.