Each Mapsly user is assigned a user profile that defines to which objects, records and Mapsly features users will have access, and whether they’ll be able to only view or also modify (create new and update existing) records.
Please note that user profiles (roles) are not automatically synced with your CRM, so to adjust access beyond Mapsly’s default configuration you’ll need to create and assign user profiles in Mapsly independently of your CRM.
Default profiles & their access level
By default, your Mapsly account has two user profiles: Administrator and Standard user. You may add more profiles as needed.
The person who created the Mapsly account and linked your data source to it automatically becomes the first Mapsly administrator.
If your CRM supports Single Sign-On, users from your CRM organization who log into Mapsly will be automatically added to your user account as Standard users. By default, Standard users will automatically be granted access to objects that were added at the Mapsly account sign-up but will only have access to records that they own (in your CRM).
Access to data
Object-level and field-level access. Adjustable record ownership.
Each object in a user profile has two permissions: for record owners and non-owners. Ownership is determined by whether the CRM user ID of a Mapsly user matches the value in the Owner field of a particular record. For records of an object owned by the given user Mapsly will apply the owner’s permissions; for other records – the non-owner’s permissions.
Both the CRM user ID and the Owner field mapping for all objects are configurable, so you can also use the Ownership concept for manually added Mapsly users who are NOT your CRM users.
The owner’s and non-owner’s permission can be to Hide, View and Modify. Alternatively, you may specify access level for fields individually.
In addition to permissions for owners and non-owners of records, you may define up to two record sharing rules, each consisting of a condition and the target permission: when a record meets the condition of a rule, the user’s access level will be raised based on the specified permission, which can also be Hide, View, Modify, or defined at the per-field level.
Please note that – by design – sharing rules can only be used to raise the access level (grant additional permissions) to records, and cannot be used to restrict access.
Access to Mapsly features
In a user profile you can also deactivate Mapsly features that users should not have access to (for example, exporting data into a file or changing field mapping for exporting prospects) and configure various user interface features (like side panels, search bar filer and many more).