Revoke a user's access in the browser as an administrator. Mobile and admin portal access are separate: disabling one does not disable the other. Locking the shared user account blocks server access for both applications. Before making a change, check which applications and login methods the user uses and who will take over their unfinished work.
Choose the appropriate change
- Account locking blocks server access for the shared account and retains application credentials, role memberships and work responsibilities. It also works for administrators.
- Not in use prevents use of the selected application but retains its credentials, the user account and role memberships. This is suitable for suspending or ending access to a specific application.
- Removing a role membership limits the permissions granted by that role and may change the workers assigned to work that follows the role's membership. It does not prevent login. Other roles and work-specific responsibilities may still grant access to data.
- Delete credentials deletes the selected application's credentials and their role memberships. The shared user account and any credentials for the other application remain.
- Delete user deletes the shared user account and its associated application credentials. Deletion also changes links to retained data, so some historical information changes.
Locking an account or disabling access does not transfer work to a successor. Deleting application credentials or the entire account does not, by itself, prevent credentials from being recreated through the organisation's login service.
Lock the shared user account
- In the browser's main menu, open Manage user accounts → List of users and click the user's name.
- In the form's User information section, turn on the Account locked switch.
- Click Save at the bottom of the form.
A locked user is logged out of the browser when the next server request that checks the lock is made. On mobile, server access is blocked, and a request that checks the lock deletes the user's mobile login tokens. Locking the account also triggers an email notification to the email address on the user's account.
The status switch and application-specific delete button for an administrator's admin portal credentials are hidden, but the shared account can still be locked. Make sure another administrator has working access before locking your own account, so that the account can be unlocked and user accounts managed later.
Unlock the account by turning off Account locked in the same section and saving. Unlocking does not activate application credentials that are Not in use or restore deleted mobile login tokens. The user must log in again on mobile.
Locking is not a separate permanent deletion state. A browser password reset clears the lock if the reset creates a logged-in browser session. When permanently ending access, also check the application statuses and the access granted through the organisation's login service.
Block only mobile or admin portal access
- On the open user form, find Mobile credentials or Admin portal credentials.
- Change the Active switch at the top of that section to Not in use. To disable both applications separately, change both switches.
- Click Save at the bottom of the form.
Disabling mobile access deletes login tokens on the server and prevents both normal login and content retrieval using a token. Disabled admin portal credentials are logged out on the next server request, and normal login is blocked. To block an administrator's browser access, use the shared account lock described above.
Not in use does not remove the user from roles or resourcing. If access must be blocked immediately, save the status change and arrange the transfer of work responsibilities separately. You can restore access later by using the Active switch in the same section and saving. If the shared account is locked, it must also be unlocked. On mobile, the user must log in again.
Consider Microsoft and Google login
When Microsoft or Google login is enabled for your organisation, an accepted external login can recreate a user account deleted from Spotilla or missing application credentials. New application credentials are created as active. This applies to both browser and mobile login flows; the credentials created depend on the login method used.
Microsoft login also updates Spotilla role memberships linked to external groups or roles. A manually removed membership may therefore return on the next login. A membership change may also trigger an update to the workers assigned to work that follows the role's membership. Coordinate permanent access removal with the access and role mapping configured in the organisation's login service.
If mobile credentials remain Not in use, access to content is blocked. However, QR or external login may first restore a login token. Success on the login screen alone therefore does not demonstrate working access: verify the result by retrieving content while connected to the network.
How does blocked access appear on mobile?
Android switches to the login screen when it detects the server's notification that the session has been invalidated. The notification texts are Session has been invalidated and You need to log in again. iOS displays Session has been invalidated, you need to log in again and starts unsubscribing from notifications.
The screen or locally stored data on an offline device may not change immediately. Revoking access does not remotely wipe the device's data. Verify that access is blocked by making a request that retrieves data from the server.
Limit permissions by changing roles
The access sections of the user form contain the fields Permissions (roles) in the mobile application and Permissions (roles) in admin portal. Remove the unnecessary role from the selections in the relevant field and click Save. You can also remove a role membership using the trash icon on the role's row in the form's User's roles section; save after doing this as well.
Removing the last member may be blocked if the role is needed for responsibilities in work or other configurations. Add a suitable successor to the role or change the responsibility causing the dependency before removing the membership. Simply setting access to Not in use or locking the account does not empty the role or resolve these dependencies.
A role change saved on the user form updates, in the background, the workers assigned to tasks and group tasks that follow the role's membership, along with their associated resourcing. The update also covers hour-based maintenance templates, offer settings, basic resourcing for task templates and contract resourcing that follow the role's membership. Changes to task workers may extend to completed tasks. Changing only the status switch or account lock does not trigger a worker update if memberships remain unchanged.
You can also change a role's members by opening the role under Manage user accounts → User roles. The task worker update triggered from this view excludes completed tasks. After the change, check both the memberships and the workers assigned to the relevant work. More detailed instructions for defining permissions are provided in mobile roles and folder permissions and admin portal user permissions.
Check the successor's scheduled working hours separately
When a role change adds a new worker to a task, they receive the service's default resourcing. Removing the departing worker's assignment deletes the task's associated time reservations. Existing reservations are not copied to the successor. Resourcing means planned working time, not recorded hours worked.
Check the default values on the Settings page in the browser's main menu: open Task settings and click the name of the Default resourcing values row. The date of a new reservation is the task's due date minus the value of Advance (days before due date). If there is no due date, the reservation's creation time is used as the starting point. Start time determines the time of day when the reservation starts, and the end is calculated by adding the configured duration.
Without saved default settings, the start time is 08:00, the duration is 60 minutes and the advance is 0 days. For example, with these values, a due date of 12 October 2026 produces a reservation for 12 October 2026 from 08:00 to 09:00. With an advance of two days, the same reservation starts on 10 October 2026 at 08:00.
For basic resourcing configurations that follow a role's membership, the new person's values are instead taken from the item's first existing basic resourcing row. These must not be confused with a task time reservation created from the service defaults. Updates to these task-specific basic resourcing configurations exclude completed tasks; contract updates exclude archived and deleted contracts.
After the background update, check the successor's actual scheduled start and end times and correct them if necessary. Responsibilities assigned directly to a person must be handled separately: a role change updates configurations that follow the role's membership. To review and adjust times, see resourcing in the Gantt view.
Delete access to only one application
Click Delete credentials at the bottom of the relevant access section on the user form. The section is hidden from the form, but deletion only takes effect when you click Save at the bottom of the form. This does not delete the entire user.
The delete button may be disabled, and the section may display a warning about the user's responsibilities in tasks or service requests. Also review resourcing and signature configurations before deleting. The presence of the button alone does not guarantee that saving will succeed.
Deleting application credentials removes their role memberships. Deleting mobile credentials also removes login tokens, login service associations and mobile usage logs. Author references in messages and comments, as well as task responsible-person references, are cleared for the deleted application credentials. Deleting admin portal credentials also clears the user reference in reservations. This action does not delete time entries linked to the shared user account.
If access is needed again later, it is added as new application credentials. See adding a user and access permissions. Also take into account the possibility of recreation through external login described above.
Prepare to delete the entire user
Arrange a successor and check for obstacles before final deletion:
- Ongoing time entries: end general working time entries and entries started for tasks and service requests that have no end time. If necessary, correct an entry using the instructions for recording working time and correcting a time entry.
- Work Alone Protection: the user's protection configuration and active work alone sessions prevent deletion. End the sessions and remove the user's protection configuration.
- Unfinished tasks: check work where the user is the only worker, as well as work that uses their single-member role or follows its membership. The check is not limited to the Open status: it treats all tasks other than completed tasks as unfinished.
- Resourcing for templates and recurring work: check task templates, recurring task resourcing and hour-based maintenance templates where the user is the only directly assigned worker or the only member of a required role.
- Offers: a worker assignment for the user in an offer's task settings prevents deletion when the offer is in the Opportunity, In Progress or Offer Sent status. Leaving a role may also be blocked if the user is the last member needed by these settings.
- Contracts: check resourcing in task settings where the user is the only directly assigned person or the only member of a role being used. Archived and deleted contracts are excluded from this deletion check.
- Signatures: check signatures assigned to the user in tasks, service requests, task templates and service request types. If deletion displays a signature warning, address the items named in it before trying again. Do not infer from the work's status alone that a signature dependency has been removed: the different deletion checks do not handle all statuses consistently.
If a deletion attempt opens a dependency view, expand the relevant reason group and click the item's Name link. A Role link, if present, opens that role. Change the responsibility or configuration in the details of the item that opens, then save it. In addition to adding a new person, you may need to remove the old user from the configuration. Blocking access does not replace these changes.
Delete the user and consider the effects on data
Click Delete user at the bottom of the user form and confirm deletion. Alternatively, use the trash icon on the user's row in the user list. Both start deletion of the entire user account.
In addition to application credentials, full deletion removes the user's working week and weekly resource settings, usage logs, worker assignments and resourcing rows. It does not mark tasks as completed or automatically transfer responsibilities to another user.
Time entries, signatures and signature configurations remain, but their links to the deleted user account are cleared. User associations in some inventory data and other costs are also cleared. A retained time entry may therefore no longer display the user's name. In the working time calendar, user details are retrieved from the current user account, and an entry without a user reference is not included in data filtered by the former user's identifier. Deletion therefore affects how personal information is displayed and how data is filtered by person, even if the entry itself remains. An account recreated through external login does not restore the person associations cleared during deletion.
To delete multiple users, select the checkboxes on their rows in the user list. Open the Actions menu in the checkbox column header and select Delete selected rows. Confirm deletion. The action processes users one at a time: some may be deleted while others remain because of dependencies. Check the number deleted and the separate dependency view for users whose deletion failed.
Check the result
- Reload the user list. A locked or disabled user will still be listed; open the form and check the lock and both application statuses. When one application's credentials have been deleted, the user account should remain and only the deleted access should be missing. After full deletion, the user account should no longer be found.
- Check that access is blocked by retrieving fresh content while connected to the network and attempting a new login. Also use the user's actual Microsoft, Google or QR login method, if applicable. After external login, check that the account, credentials or deleted role membership have not been recreated.
- If you disabled only one application's access, also check that access to the other application works as intended. Locking the shared account should block both.
- Check the workers assigned to transferred work and the start and end times of resourcing. After the role change's background update, also verify templates and other configurations that follow the role's membership. A default reservation does not demonstrate that the previous working time was transferred to the successor.
- Check a representative time entry and any required view filtered by person. A deletion success notification alone does not demonstrate that historical data is displayed in a way that meets your needs.
If access or visibility does not match the change you made, see investigating a user's access.