Giving a User Access to Restore a Snapshot in MYOB Acumatica
This article explains how to assign the correct roles and permissions so a user can restore a snapshot in MYOB Acumatica.
Required Roles
To restore a snapshot, the user needs the following roles:
Snapshot User – Allows the user to perform snapshot operations during system lockout and access snapshot options.
Lockout Manager – Allows the user to log in while the site is locked for snapshot work, and unlock it when finished.
Access to Tenants screen (SM203520) – Required to use the Import Snapshot and Restore Snapshot actions.
This access is typically included in the Administrator role or a custom role configured with these permissions.
Steps to Grant the Roles
Go to Users (SM201010).
Open the user’s record.
On the Roles tab, add the following roles:
Snapshot User
Lockout Manager
Click Save.
If your site has multiple companies or tenants, assign these roles for each tenant the user will need during the restore. If not assigned across all relevant tenants, the user may lose access during or after the restore and be unable to log in while the site is locked.
Using a Custom Role
If you’re using a custom role instead of the standard Administrator role:
Ensure the custom role has access to the following screens:
Tenants (SM203520) – required for Import Snapshot and Restore Snapshot.
Delete Snapshots and Tenants (SM503000) – optional, only needed if the user needs to delete or clean up snapshots.
Test the User’s Access
To confirm the setup:
Have the user log in and open Tenants (SM203520).
Check that the user can see and access the Import Snapshot and Restore Snapshot options.
Test restoring a snapshot on the target tenant (while logged into a different tenant).
Common Issues and Troubleshooting
Issue | Cause | Resolution |
|---|---|---|
User can’t log in during lockout or after restore | Snapshot User and Lockout Manager roles not assigned for all relevant tenants | Assign both roles to the user across all required tenants. |
Access Denied on import or restore | May be caused by storage/S3 configuration issues | If roles are correct, contact Support who will contact Platform and confirm S3 configuration. |
Users appear unlicensed after restore | Licensing or user associations not updated post-restore | Verify user licensing and associations before handing the site back to the client. |