The organization's shared default language, timezone and browser settings for Google SSO sign-in are managed in the admin portal. You need administrator privileges for the organization. Each user's personal interface language is selected separately.
Check the shared language and timezone
- Open Settings from the admin portal navigation.
- Select the Settings tab on the page and click Time and Language Settings in the table.
- Check Default language (e.g. emails). The available options are Finnish, English, Swedish, German, Danish and French.
- Check Default timezone (affects e.g. task reminders). Select a timezone suitable for the organization's operations from the list; you can search by typing its name in the field. The default timezone is Helsinki.
- Select Save on the form. Wait for the success notification and reopen the same form to confirm the saved selections. Cancel closes the form without saving changes.
What do the language selections change?
Default language (e.g. emails) is a shared setting for the organization. It does not determine the language of every message. An email notification's own default language takes precedence over the organization's default language. A Spotilla user's personal language affects which language version is selected for the recipient. If the notification has no message version in that language, the notification's default language is used. A recipient without a Spotilla user account receives the message in the notification's default language or, if no notification-specific default is set, in the organization's default language.
The browser's Admin portal language is a personal user setting. Changing it also updates the user account's language, which can be used when selecting the language of email notifications. The language of the Android and iOS mobile apps is selected separately in each app's own profile. Saving the shared default language does not change these personal interface selections or translate names or descriptions you have written yourself.
For the personal settings steps, see changing your profile, password and language. Checking a notification's language versions and sending conditions is covered in configuring email notifications.
What does the timezone affect?
The timezone determines the local date and time for reminders and scheduled processing that use the organization's timezone. Daily task push reminders and checks for email notifications related to due dates are started at 8 a.m. local time. Actual delivery may occur later because of processing and message transmission.
When an email notification is checked, the date calculated from the task's due date and the notification's day offset is compared with the organization's local date. The daily repetition selection also affects sending. Selecting a timezone does not trigger a reminder on its own: the task's status, notification settings and recipients still affect it.
The timezone also affects, for example, the scheduling of overnight runs for automatic contract status changes, contract invoices and the creation of contract-based tasks, as well as evening processing of inventory values, when those features are in use. Not all background processing uses this setting.
Saving changes the organization's setting, not the timestamps of events already saved or task due dates. Task due dates are still treated as dates in Helsinki time, and the admin portal uses the Helsinki timezone when handling times. Do not use this setting to correct an individual event with an incorrect time.
Check the Google SSO browser settings
Google SSO must be enabled for the organization. Open the Integrations tab on the Settings page, select its Integrations subtab and click Google SSO in the table. If the row is missing, discuss enabling it with your Spotilla contact.
Configure the settings together with the person responsible for the organization's Google authentication. You need access to the SAML app settings in the correct organization's Google Admin Console.
- Copy the ACS URL and Entity ID shown on the Spotilla form into the SAML app's Service Provider Details section in Google Admin Console. These are read-only values provided by Spotilla. Use the form opened from your own organization's Spotilla address.
- Enter the organization's allowed domain in Google Domain. The domain of the signing-in user's email address must match this value.
- Enter the sign-in URL provided by Google in Google SSO URL and the identity provider's PEM certificate in Google IdP Certificate (PEM). The domain and URL are required. The certificate is also required unless it has already been saved.
- If the certificate is masked and you are not replacing it, leave the masked value unchanged. Saving will then preserve the previous certificate. To replace the certificate, replace the masked value with a complete new PEM certificate.
- Select Save and reopen the settings. Check the domain and URL, and confirm that the certificate is masked again.
The In use status in the table indicates that the URL and certificate have been saved. It does not confirm that they are correct or that sign-in has succeeded.
User accounts and separate mobile requirements
For browser sign-in, Spotilla checks the SAML response and the email address's allowed domain. A successful first sign-in can create a user account and an active manager user. If a user account or manager user with the same email address already exists, it is reused; a missing manager user can be added to an existing user account. Signing in does not itself grant administrator privileges. Check the required permissions using the guide to configuring manager user permissions.
Android and iOS also need their own customer-specific Google sign-in client IDs. Android uses the Android client ID provided for the customer account. iOS uses the app's own client ID together with the server client ID provided for the customer account. Saving this Google SSO form does not configure the mobile client IDs. Confirm their setup separately with your Spotilla contact.
On mobile, Spotilla checks the Google token, the email domain and the Google Workspace domain verified by Google. An email address that merely looks correct is not enough. The first successful mobile sign-in can create an active mobile user or reuse an existing user and link them to the Google account. Regular password sign-in is blocked for a mobile account linked to Google: the user must sign in with Google. Changing the regular password does not correct incorrect Google sign-in settings.
Verify operation on the platforms in use
Test browser sign-in using the Sign in with Google button on the organization's sign-in page. On the Android sign-in screen, select Sign In with Google; on iOS, select the sign-in button marked with the Google logo. On mobile, enter the correct customer account and use an account belonging to the allowed Google Workspace organization.
Test the browser, Android and iOS separately, depending on which platforms the organization uses. After signing in, confirm that the customer account is correct and that the information and functions the user needs are visible. Successful browser sign-in does not confirm the mobile configuration. For the other sign-in steps, see signing in and resetting your password.
After changing the language and timezone, also check the next message or reminder generated using those settings. If the result differs from what you expected, check the message's own language, the recipient's language, the notification conditions and the sign-in platform used before changing the shared settings again.