Administrator: Glossary

Updated by Jennifer B.

  • 360Value: A valuation, replacement cost estimating product that provides replacement cost estimates for residential, commercial, and agricultural properties. A contract is required to use this service.
  • Accessibility: Means websites, tools, and technologies are designed and developed so people with disabilities can use them. More specifically, people can: perceive, understand, navigate, interact with, and contribute to the Web.
  • Account info page: Instance administrator page containing the name, type, account number, instance ID, subdomain URL, resource ID, and IP restrictions for an instance.
  • Accessible: Things that are easy to use for everyone, including people with disabilities.
  • Additional living expenses (ALE): Extra expenses policyholders incur if they must leave their permanent residence because of a loss.
  • ALE payment method: How ALE totals are calculated. The total ALE for each category is calculated as such, Approved - Normal Expenses = Total ALE. The Total ALE from each column is then combined together to arrive at the Total balance owed.
    There are two ALE payment method settings:
    • Do not offset category totals: Sets the Total ALE column to 0 if there is a negative balance for that category (approved - normal).
    • Offset category totals: Leaves a negative balance for a category where the approved is less than the normal (approved - normal = negative balance). This negative balance then reduces the amount owed.
  • API (application programming interface): A way for computer programs to communicate with each other. Similar to EDIs but more capable of handling real-time data exchange.
  • API key: A code or token used to authenticate a program or user and allow data transfer.
  • Assign a team as a primary contact: An option that allows a resource team to be assigned as the primary contact and have all permissions typically granted to a single primary contact.
  • Auto-create XactAnalysis dataset preference: An XactAnalysis dataset preference that
    • Automatically creates a ClaimXperience project within a designated instance without offering a review of the create project drawer before project creation.
    • Assigns either the logged in XactAnalysis user or a designated resource as the primary contact.
    • Automatically adds the logged-in XactAnalysis user as a resource if they aren't already part of the associated instance.
  • Auto-generate projects: Projects created from a linked Verisk product, such as Xactimate, XactAnalysis, and XactContents.
  • Auto-launch XactAnalysis dataset preference: An option that, when enabled,
    • Automatically launches ClaimXperience in a new tab
    • Assigns the logged in XactAnalysis user as the primary contact
    • Automatically adds the logged in XA user to the associated instance as a resource if they haven't already been added
    • Takes the user directly into the ClaimXperience project if no required fields (such as a signature) are missing.
  • Automated triggers: A setting that triggers the automatic launch of a task assignment upon the completion of a prerequisite task.
  • Batch adding / updating resources: An option supported in the add resources drawer that can be used to both add groups of new resources and update existing resources.
  • Calendar / shared calendar: A shared calendar that displays a list of upcoming events and syncs project participants' calendars, allowing everyone involved in the project to be aware of the events taking place. Project participants can add, edit, and delete events, as well as decide who is notified of any changes.
  • Claims administrator: A resource who can view all ClaimXperience projects within a specific instance.
  • ContentsTrack integration: A way for users to access ClaimXperience personal property items from ContentsTrack.
    • If ContentsTrack is linked to ClaimXperience, if ContentsTrack users attempt to access ClaimXperience and the claim doesn't exist in ClaimXperience, a claim will be automatically created.
    • Items in ContentsTrack assigned 'Replace' status are copied over to ClaimXperience. In this case, future edits to those same items in ContentsTrack will not be reflected in ClaimXperience.
    • Items in 'Clean,' 'Storage,' or 'Questionable' status are displayed in ClaimXperience but cannot be edited. Any updates to these items in ContentsTrack will be reflected in ClaimXperience upon refresh. Items that are not at the policyholder's location or already requested may be requested for return by the policyholder.
  • Custom tasks: Method for delivering forms to users. Only those forms with a task can be sent. Tasks can be assigned within the portal on a project or externally to recipients on a project. It also can be assigned via API. Tasks can be assigned to pending companies in the portal and via API to streamline workflows.
  • Damage assessment automation (DAA): A feature that automatically generates an estimate value for expedited payment. DAA allows a ClaimXperience custom task configured with line items to be passed over to Xactimate automatically so that an estimate total can be returned. Additional configuration options allow the estimate total to be viewed by the task assignee and accepted/rejected, as well as estimate reports to be viewed and downloaded.
  • Event trigger: An action or event that when complete initiates another action or event.
  • File types: The types of files that can be uploaded to ClaimXperience. ClaimXperience currently supports only the following file types:
    • Audio: MP3, OGG, WAV
    • Documents: CXV, DOC, DOCX, EML, ESX, MSG, PDF, XLS, XLSX
    • Images: BMP, JPEG, JPG, PNG, ZIP
    • Videos: 3GP, 3GPP, AVI, GIF, M4A, M4V, MOV, MP4, MPEG, WMV
  • Flagged (tab): A tab in the Personal Property module that lists personal property inventory items requiring attention. Only submitted items can be flagged for review.
  • Flagged items: A personal property inventory item that requires attention, usually additional information.
  • Form accessibility scan: A personal property inventory item that requires attention, usually additional information.
  • Full access: Access to a project that is comparable to that of a primary contact without the user being assigned role of primary contact.
  • Hazard recognition: A scan used to analyze images for potential hazards. Users see warnings and receive notifications if potential hazards are identified.
  • Hide from policyholder: An option that hides a team member who is not the primary contact from the policyholder.
  • Hide primary contact: An option that allows the primary contact can be hidden from the policyholder, but only if other full-access team members of the product are visible.
  • Image analytics: A feature that includes image inspection, privacy checks, and hazard recognition.
  • Image inspection: A part of image analytics that analyzes images and provides warnings and notifications if there are potential issues. It
    • Analyzes
      • Metadata by checking the software signature, modified date, and dimensions.
      • Date discrepancy (only available for JPG files) and flags images taken a predetermined number of days or more before the date of loss.
      • Location (only available for JPG file) and flags images taken more than a predetermined distance from the location of loss.
    • Performs an internet check and flags images that also exist on the internet.
  • In-app notifications: Project-related notifications received within ClaimXperience. In-app notifications are automatically removed from the Notifications drawer and the Notification history after 30 days.
  • In-portal messaging: Direct messaging within the ClaimXperience portal. In addition to being visible to the sender and recipient, messages are viewable by the project's primary contact and their company and become a permanent part of the project.
  • Instance administrator: A resource who can add new resources and configure instance-wide settings
  • Integrated service: Company or individual outside of ClaimXperience contracted to provide a service within the portals.
  • Linking to XactAnalysis via MFN: An option to link a ClaimXperience project to an XactAnalysis assignment on a team member level using a main file number (MFN). More than one ClaimXperience team member can link a specific ClaimXperience project to XactAnalysis.
  • Measure tool: A video collaboration feature that allows users to take measurements in real time during a video collaboration live call. A live call participant must be using the OneXperience app and an augmented reality- (AR-) compatible device to use this tool.
  • Messages: In-portal messaging between team members.
  • Notification history: A list of all the notifications received in the last 30 days. Notifications are removed after 30 days.
  • Notification preferences: A way for team members to specify which notification they want to receive and how they want to receive them (email or in-app). Policyholders cannot change their notification preferences.
  • Notification signatures: A way for carriers to have specific information related to the lines of business, divisions, states, and so forth in the notifications going out to customers. Notification signatures are configured by instance administrators.
  • Offline tasks: Custom tasks without a personal property question type that can be downloaded to the OneXperience mobile app and completed with or without an internet connection. If submitted when offline, they will be submitted once a connection is established.
  • Offset payment method (ALE): If the approved expenses are less than the normal expenses for a given category, the "offset" payment method reduces the total approved balance by the negative amount, while the "do not offset" method does not.
  • Open ClaimXperience from XactAnalysis: A way for ClaimXperience resources in one or more instances to open a ClaimXperience claim from XactAnalysis.
  • Personal property (feature): An option that allows policyholders to build an inventory of personal property contents. The personal property task can be shared with any team member so an inventory can be built.
  • Personal property searching: A way for users to search for personal property items based on administrator settings. For example, searching for vendor items and general quote items. Administrator settings for this feature can be different from settings for the personal property question type within the form builder.
  • Personally identifiable information (PII): Information that can be used to distinguish or trace an individual's identity either directly or indirectly by linking with other information.
  • PLNAR: A third-party measuring service that provides a 3D model of a room that has been scanned by the requestor.
  • PLNAR Snap: The image package returned from a PLNAR request.
  • Privacy checks (image analytics): Part of image analytics that allows users to scan uploaded images in the Files page, or images being uploaded, for faces and text. If found, a new image with blurred faces and text is saved to the project.
  • Project administrator: Also known as a claims administrator. The individual who can view all projects in an instance, reassign a primary contact, and has additional permissions in a project. These administrators can also add, remove, and modify team members, but they cannot fully participate in the project (for example, upload files and send messages) unless assigned as a team member.
  • Project email: An email address that project notifications can be sent to in addition to or in place of an adjuster's email address.
  • Resource adding automation: A setting that supports establishing one or more rules to govern how resources are added to an instance.
  • Scope changes: Changes to the key properties of an estimate; for example, job type, type of loss and job size.
  • Services: Services outside of ClaimXperience, such as PLNAR, that can be added to a contract and used within the collaboration portal.
  • Shared calendar: A calendar that displays a list of upcoming events and syncs with those of other project team members.
  • Sync Content to additional MFN custom task setting: A setting that allows custom tasks and files to be shared with an additional MFN as long as the policy and claim numbers match.
  • Team: A group of resources that can be treated as an individual team member. A team can be assigned the role of primary contact, which allows each member of the team to perform the duties of a primary contact.
  • Team members: Individuals, teams, or companies who participate in a claim. Examples of team members include the policyholder, adjusters, contractors, and primary contacts.
  • Theming: Changes an instance administrator can make to customize their ClaimXperience portal.
  • Third party: Company or individual outside of ClaimXperience contracted to provide a service within the portal.
  • Tokenize: A method of replacing personally identifiable information (PII) with random identifiers to protect against unauthorized access or use.
  • Video collaboration: A way to collect real-time video and photos to triage a claim using a policyholder's mobile device.
  • Video collaborator: A resource who can perform video collaborations within ClaimXperience projects.
  • XactAnalysis ID (MFN): Main File Number/Master File Name. In ClaimXperience, this is required for a team member to link a ClaimXperience project with an XactAnalysis assignment. Each team member can link a ClaimXperience project to their own XactAnalysis assignment; one ClaimXperience project can be linked to multiple MFNs.
  • XactAnalysis integration: A configuration that allows a ClaimXperience non-policyholder user to link a specific ClaimXperience project with an associated XactAnalysis assignment. When a project is linked to an assignment, information can be shared between the two.
  • XactContents integration: A configuration that allows for linking between a ClaimXperience product and its XactContents counterpart. Some information can be passed between the two.
  • Xactimate integration: A configuration that allows a ClaimXperience non-policyholder user to link a specific ClaimXperience project with an associated Xactimate assignment. Some files can be shared between the two.

How Did We Do?