Axsy Config Scopes can be configured to allow different groups of users to sync different data and config settings that are specific to their use case. By using Persona Users, Config Scopes can be easily tested and modified.


Users can be assigned to Axsy Config Scopes individually, or via profiles. Using profiles as scope drivers is the recommended approach; making assignment automatic and easier to maintain. Users can also be assigned to scopes individually if needed.


For a general overview of Axsy Config Scopes, see the following knowledge article: Working With Config Scopes.


Using Persona Users to Configure Config Scopes

One effective way to ensure Config Scopes are set up correctly is to use Persona Users that represent different user types or roles in your org. The steps below show how you can use Persona Users together with the Axsy Config Tool to configure and validate Config Scopes.


Step 1 - Configure Persona Users

Create standard Salesforce Users that will represent the different user types or roles in your org. These will be your Persona Users. For example, this could be an Inspector, or a Supervisor. These users will be used to validate the Sync Config and test logging into the Axsy Mobile app.


Figure 1 - Example Inspector and Supervisor Users


Each Persona User should have:

  • The same permission sets assigned as the users they represent.
  • The correct Axsy permission sets assigned.
  • (Optional) A dedicated Salesforce profile. Profiles are recommended for scalability, but not required.


Note: Any user logging into the Axsy Mobile app should have the correct Axsy permission sets assigned. These can be found in the following article: Assign Permission Sets.


Step 2 - Create Axsy Config Scopes

Next, where applicable, create a Scope for each Persona. Follow naming conventions to ensure that each Scope has a clear, descriptive name. As multiple profiles can be assigned to a Scope, you should only create Scopes for when data, or settings, differ for each Persona User.

Figure 2 - Example Inspector Scope


All Scopes must be based on an existing Scope. In most cases, this will be Org Default, which provides a baseline for all users, and is the Scope that all users use by default. If a Scope already exists that is similar to what you need, you can base the new Scope on that instead.


Figure 3 - Creating A Supervisor Scope Based On Inspector's Scope



Once created, assign the appropriate Persona Users (or profiles) to the Scope. Repeat Steps 3 and 4 for each Persona User.


Step 3 - Configure Permission Check

Configure the Permission Check tool to check object permissions against the Persona User. Ensure that you:

  • Click "Check Permissions Now"
  • Click "Update Permitted Objects"


Figure 4 - Configuring Permission Check Against Persona User


Note: The name of the Persona User should be shown for the object permission issues, and permitted objects as highlighted in Figure 4. If not, in Settings, you may have to click "Save" and run the Permission Check again.


Whilst working on the Config Scope, the Permission Check tool will highlight in red any objects in the Scope that the Persona User cannot access. If no objects are highlighted in red, then all objects are accessible, and you can proceed. If any objects are red then you should either:

  • Remove the object from the Config Scope, or
  • Grant access to this object using Permission Sets or Profiles.


More information on how to configure the Permission Check tool, and on configuring implicit object access, can be found in the following article: Permission Check


Step 4 - Define Scope Contents

With your Scope created, define what data and settings it should include. For example:

This will ensure that each user receives the data they need when working offline.


Step 5 - Publish and Verify via Login Testing

Once you have completed Steps 3 and 4 for all Persona Users, you can publish the config version. This will ensure that all changes will be picked up when the Persona Users log in.


More information on publishing Config Versions can be found in the following article: Config Versions and Publishing.


Figure 5 - Publish Config Version


Once the config version has successfully published, log in to the Axsy Mobile app as each Persona User. Check that:

  • Sync completed without any Sync Errors.
  • The correct data is available, including any additional settings such as Axsy Dashboards.
  • All automations run as expected.
  • No additional or unintended data is synced.