> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-essentials/using-the-platform/about-page.md).

# The About page

The *About* page gives you information about the SAM version, your unique Account Key, your Spectralink Account Number, and two methods of using the SAM certificate for HTTPS security. It also provides a mechanism for updating the SAM server.

![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-fdb92f9f8acdf5dbec26850d1316d06615d2c7b2%2Fimage30.png?alt=media)

## Versity DPC Initial Enrollment QR Code

*For Versity phones running Android 13 only*\
If you are administering Versity phones running Android 13 and are not using an EMM, you can scan this QR code to automatically set the permissions needed for Spectralink apps to run on the phone. See the *Versity Applications Administration Guide* for step-by-step instructions.

## App Version

The app version is the software version currently running on SAM. After applying an update, this version number will change.

Understanding the app version

The app version code includes both the Release version, the VM version and the SAM version. The App version 1.15.0.xxx.1441 provides this information:

| SAM release branch | Virtual appliance | SAM deploy version |
| ------------------ | ----------------- | ------------------ |
| `<major>`          | `<minor>`         | `<patch>`          |
| 1.15.0             | xxx               | 1454               |

The VM version and the SAM version are provided to guide engineering and support in recreating customer scenarios for testing and development. Please provide all numbers when contacting Spectralink service. Upon upgrade the minor version and the SAM version will change. The VM version only changes when the VM is upgraded.

## Bulk Delete Device Level Settings

This setting is only visible if enabled on SAM’s [Preferences](/amie-essentials/using-the-platform/the-console.md#preferences) page.

![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-5c8a91be29c52d5d99269e07b753cbdf0549d843%2Fimage31.png?alt=media)

{% hint style="danger" %}
**This procedure cannot be undone!**

Once you’ve followed the steps below and clicked the **Delete** button, the selected *Device*-level configurations will be erased. They will need to be reconfigured if you wish to restore them.
{% endhint %}

After enabling this new setting on SAM’s *Preferences* page, follow the steps below to select and delete *Device*-level settings from multiple phones at a time. Once the *Device*-level settings are deleted, devices will use their *Group*, *Enterprise*, or default setting values.

1. Click **Bulk Delete Device Level App Settings**.\
   ![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-307d9697f30f3b8f8767a742f20911dbda841419%2Fimage33.png?alt=media)
2. In the pop-up, click **Yes, proceed**.\
   ![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-aad48d3d20969baec7e5eb29cef831e64f56c676%2Fimage34.png?alt=media)
3. The resulting *Bulk Delete Device Level Settings* page shows a list of Spectralink apps in a column of tiles to the left. Tiles with green ovals contain settings set at the *Device* level; the number in each oval shows how many *Device*-level settings are configured in the app.

   Clicking on an app tile with an oval shows a hierarchical list of settings set at *Device* level. Here’s how to read the information displayed:

|                                                 |                                             |   |
| ----------------------------------------------- | ------------------------------------------- | - |
| *AMIE Agent has 3 settings set at Device level* | *Device-level settings are set on 1 device* |   |

![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-f73955f4806499bb392476a948404742d00f0902%2Fimage35.png?alt=media)

1. Select the *Device*-level settings you want to delete.

   Note in the example below that as settings are selected to be deleted, the app tile changes: the green oval now shows how many settings will not be changed, and the blue oval that appears when you start selecting shows how many settings will be deleted:\
   ![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-67562b17abacfa1b89af4b0a8115ca311ff75817%2Fimage36.png?alt=media)
2. When you’ve finished making your selections, click **Delete Selected Settings** at the bottom of the page. (The number in parentheses is the number of *Device*-level settings that will be deleted.)\
   ![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-f6289479f275c97e5956d25f3db92bd73e9e667f%2Fimage37.png?alt=media)
3. In the resulting pop-up, review the settings to be deleted:\
   ![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-0098b7f6337ae78eda229003e601074c7d408813%2Fimage38.png?alt=media)
4. In the field provided, type **DELETE** (in all caps) to enable the **Delete** button. (If you do not want the new configuration to be sent to the affected devices immediately, uncheck *Send configuration to affected devices now*, in which case devices will update within their standard cycle of one hour.)
5. Click the **Delete** button.

## Account Key

The Account Key is a random string of 22 characters, generated by SAM internally. This number provides additional security for EMM enrollment and is required by the SAM Client app.

## Account Number

The Account Number is generated by Spectralink and sent to the customer for licensing and identification purposes.

## SAM Server Certificate

SAM uses a certificate to establish a secure connection between Versity smartphones and itself. Click **Copy Certificate to Clipboard** to copy the SAM certificate to the clipboard and paste it into an EMM attribute field for loading onto a Versity.

## Cert Signing Request File

For full deployments, a Certificate Signing Request (CSR) is provided. Using this method, a private or public CA signs the certificate, which is then imported into SAM.

The root certificate provided by the CA server can be loaded into an EMM, which sends it to the smartphones, that in turn use it to automatically establish a secure connection with SAM.

{% hint style="info" %}
**Private CA**

Our expectation is that most customers will have their own Private CA. They will need to import the CSR into that CA and have it signed, then export the signed request for importing back into SAM. The signed certificate can be copied into an EMM for delivery to the smartphones as a .crt file.
{% endhint %}

## Change SSH Access

SSH is disabled by default in this release. See [Enabling/Disabling SSH](/amie-essentials/maintenance/backup-and-restore.md#enabling-disabling-ssh) for more information.

## Upload Signed Certificate (.crt)

Click **Browse File** to find and select the desired file.

![](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-1aa7ff984c3efc49dca9cfaf8b5dd50d27980611%2Fimage39.png?alt=media)

{% hint style="info" %}
**SAM expects an ASCII format file**

When using a Windows 2012 CA server, be sure the cert is produced with Base 64 encoding.
{% endhint %}

1. Copy the now-signed certificate file with a .crt extension into your file system, along with the private key of the originating machine if using a multi-domain or wildcard certificate.
2. Log into SAM web interface. Navigate to the *About* page. Click **Browse File**. Navigate to the .crt file and select it. Click **Open**.
3. *If you are using a multi-domain or wildcard certificate, generated on an outside machine:* It is required that you also upload the RSA private key from that outside machine as well. This will replace SAM’s initial private key. Click **Browse File** again. Navigate to the .key file and select it. Click **Open**.
4. After upload is complete, log into the VM host for SAM, change to the bin directory (`cd bin`) and run the importCert script (`./importCert.sh`).

{% hint style="info" %}
At this point if you disconnect from and browse back to SAM, and you have the SlnkEngrCA cert in your PC's trusted Root Store, then you should no longer see https warnings in your browser.
{% endhint %}

## Multi-domain and Wildcard certificates

Multiple domain certificates (SAN), covering several machine names, and wildcard certificates, covering entire DNS domains, are accepted by SAM (R1.2 and beyond). To deploy these kinds of certificates, both the certificate and private key from the originating machine must be uploaded to SAM.

Upload Multi-domain or Wildcard Certificate (.crt/.key)

1. Copy the certificate file with a .crt extension into your file system, along with the private key of the originating machine.
2. Log into SAM web interface. Navigate to the *About* page. Click **Browse File**. Navigate to the .crt file and select it. Click **Open**.
3. Click **Browse File** again. Navigate to the .key file and select it. Click **Open**. This will replace SAM’s initial private key.
4. After upload is complete, log into the VM host for SAM, change to the bin directory (`cd bin`) and run the importCert script (`./importCert.sh`).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spectralink.net/amie-essentials/using-the-platform/about-page.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.