Getting started
Before you sign in
Ask your SpaceRivers administrator to confirm that you have:
- an active user account and the correct organization (tenant);
- the roles needed for your work;
- an employee record linked to your account if you use time, schedule, or mobile features;
- access to the correct jobs and cost codes; and
- the correct web or mobile environment for your organization.
Sign in
- Open the SpaceRivers web application or mobile app.
- Enter the email address associated with your account.
- Enter your password. A passcode may also be available for supported field workflows.
- If your email belongs to more than one organization, select the tenant you want to enter.
- If prompted, replace the temporary password before continuing.
Sessions expire for security. Save incomplete work before leaving a device unattended and sign in again when prompted.
Learn the workspace
The web sidebar is permission-aware. Its primary areas are Home, Analytics, Time, Schedule, WBS, Budget, Setup, Integration, and More. More contains settings, administration, and configuration pages when your role permits them.
The header provides profile, notification, recent activity, and pending-approval entry points. Availability depends on tenant configuration.
Recommended setup order
For a new tenant, configure shared records before entering transactions:
- Create divisions, branches, departments, employee classifications, and rate codes as needed.
- Add employees and link each application user to the correct employee.
- Create jobs, phases, cost codes, and business partners.
- Configure work periods, overtime rules, shift rules, and pay groups.
- Configure WBS codes, item groups, and items if cost control is enabled.
- Assign job and cost-code access.
- Create roles and grant only the required module permissions.
- Configure integrations, message templates, notification rules, and approval workflows.
Continue with End-to-End Workflows for the operational sequence.
Need help?
Use Troubleshooting for common access, synchronization, and workflow issues. Do not include passwords, passcodes, API keys, or full customer records in a support request.