Use your organisation's Spotilla address or the Spotilla mobile app. You need your own user account, the correct tenant and confirmation of whether to use a Spotilla password or your organisation's Microsoft or Google login. Browser and mobile access require the appropriate user permissions; a browser user account alone does not guarantee mobile access. Ask your administrator for any missing details.
Log in in a browser
Open your organisation's login page. For a standard login, enter Sähköposti and Salasana and select Kirjaudu sisään. The tenant is determined by the Spotilla address you opened.
If your organisation uses Microsoft login, select the Kirjaudu sisään button marked with the Microsoft logo on the login page. For Google login, select the Google button. Follow the identity provider's instructions and select the correct organisational account. The options displayed depend on the tenant's settings.
When organisational login is enabled, the standard password fields are available through the Other logins link. The presence of this link does not mean that your organisational account is allowed to log in with a Spotilla password.
Complete any required password change or additional authentication. Spotilla's multi-factor authentication verification and backup codes are explained in PIN lock and multi-factor authentication.
Log in to the Android or iOS app
Enter your organisation's tenant identifier in the Tenant name field on the login screen. Use the identifier provided by your administrator: an email address or organisation name alone cannot replace it.
For a standard login, also enter your email address and Spotilla password. Select Login on Android and Login on iOS. If the app requires a new password when you first log in, change it before continuing.
When logging in with an organisational account, select LOGIN WITH MICROSOFT or the Google button on the same login screen. Enter the correct tenant in the prompt that opens and follow the identity provider's instructions. The button only works if the corresponding login service is configured for the tenant and your user account is authorised to use it. A mobile account linked to a Microsoft or Google account cannot be used for a standard Spotilla password login.
After logging in, check your profile to see which tenant you are logged in to and make sure the data you need loads successfully. The Spots and tasks you see depend on your user permissions.
Log in to the mobile app with a QR code created in a browser
You can log in to the mobile app without typing a password if you are already logged in in a browser and a mobile user is linked to the same user account.
- Open the user icon in the browser's top bar and select User profile.
- Open the Log in to the mobile application with QR-code section of your profile and select Create QR-code.
- On your phone's login screen, select QR-CODE LOGIN on Android or Sign in with QR-code on iOS and scan the code displayed in the browser with the camera. Allow camera access if your phone requests permission.
- After logging in, check the tenant and that the data loads.
A code created from your own profile is valid for 10 minutes and can only be used once. It also contains the tenant, so you do not need to enter it separately when logging in with a QR code. If the code has expired or has already been used, create a new one. Make sure you use a login code; a Spot's QR tag is not a login code. Do not share the login code with anyone else, as whoever scans it will log in as you.
Reset a forgotten Spotilla password
The reset applies to your Spotilla password. A Microsoft or Google login password must be reset through your organisation's identity provider. An expired session does not in itself mean that you need to change your password.
Send a reset request
In a browser: open the correct organisation's login page and select Forgot your password?. On the organisational login screen, the link is available under Other logins if needed. Enter the email address for your user account and select Resetoi salasana. The tenant is determined by the page's address.
On Android: select Forgot your password? on the login screen. Fill in Email and Tenant name on the reset form and select Recover password.
On iOS: select Forgot your password? on the login screen. Fill in Email and Customer Instance on the form that opens. Send the request using the save button in the top right corner. The button becomes active when the tenant has been entered and the email address has a valid format. Note that the tenant field is labelled Tenant name on the login screen, but Customer Instance on this reset form.
Change your password using the reset email
Open the link in the reset email you receive. The link is valid for six hours. If it has expired, send a new reset request.
Fill in Uusi salasana and Vahvista uusi salasana on the page and select Vaihda salasana. The password must be 8–128 characters long and contain a lowercase letter, an uppercase letter, a number and a special character. A mobile user's new password must differ from their current password. The two fields must match.
Sending a reset request does not yet change your password. Make sure the new password is accepted, then use it to log in to the correct tenant. A successful mobile user password reset invalidates all of that user's mobile sessions in that tenant, so they must also log in again on other phones. The reset does not delete work entries saved on the server.
If the email does not arrive, check your spam folder, email address and tenant. A notification after submitting the reset request alone does not confirm that the email arrived. Ask your administrator to check your account if the problem continues. If you remember your password and simply want to change it, follow Your profile, password and language.
Why does the mobile app ask me to log in again?
A mobile session can expire due to inactivity. Sessions belonging to the same mobile user are ordered separately for each tenant according to their last recorded server activity. Each cleanup applies the following inactivity limits:
- Most recently used session: three calendar months.
- Second most recently used session: one calendar month.
- All other sessions: two weeks.
The order can change as sessions are used. These limits do not refer to the age of the user account or the order in which phones were first used. If a session has no recorded activity time, its creation time is used in the calculation. In a tie, the newer session comes first.
For example, if three sessions were last used 1, 10 and 15 days ago, the third can be removed once it has exceeded the two-week limit. The other two remain according to their respective limits. A session exactly at its limit is not removed.
Activity means an accepted connection to Spotilla's server. The activity time of a standard mobile session is updated at most once an hour. Simply opening the app or unlocking the PIN lock does not therefore maintain the server session by itself. Cleanup is queued daily at 8 a.m. Helsinki time and runs in the background, so a session may not end exactly when its time limit is reached. You cannot change these limits in your own settings. Special accounts used for integrations are excluded from this cleanup.
Expiration removes the login session, not the user, Spots, tasks or work history saved on the server. An expired session is blocked the next time the app uses it to connect to the server.
Android returns to the login screen. The notification may appear in English even when the app is in Finnish: Session has been invalidated and You need to log in again. On iOS, the notification is Session has been invalidated, you need to log in again. If iOS does not return to the login screen, try logging out from your profile. If you cannot access the login screen, contact support.
Log in again to the correct tenant using a login method allowed for that tenant and make sure the data loads. You only need to reset your password if you have forgotten your Spotilla password.
The browser session timeout and the mobile app's PIN or biometric lock are separate features. Their settings do not change the mobile session limits described above. See session timeout and refresh and PIN lock and multi-factor authentication.
Log out
Save and send any unfinished entries before logging out. Local session and form data in the mobile app is cleared during logout, so you should not rely on unfinished work being retained.
In a browser: open the user icon in the top bar and select Log out. This ends that browser session.
On mobile: open My profile in the side menu and select Logout on Android or Sign Out on iOS from the profile page. Confirm the action. The iOS profile page may be titled Profile. Microsoft login may also include logging out of the identity provider.
A successful mobile logout on the server invalidates all sessions belonging to the same mobile user in the tenant you are logging out of. Other phones must then also log in again. This differs from the cleanup of an individual inactive session.
However, Android and iOS can clear the local session and return to the login screen even if the server logout fails. Seeing the login screen alone therefore does not prove that sessions on other devices have been invalidated. To confirm that they have ended, check that the other devices also require a new login when attempting to fetch data from the server. Logging out does not delete work or history saved on the server.
If login fails
Check the tenant or browser address, email address, correct login method and network connection. With a standard password login, five failed attempts can lock the account. Do not keep guessing the password; use password reset or ask your administrator or support for help as directed by the account lock notification.
An inactive user or missing permissions is different from an expired session. Logging in again or resetting your password does not grant new permissions. If login succeeds but the data you need is missing, ask your administrator to check your user's tenant and permissions.