Customers
|
New to Sentinel EMS?
|
What Is a Customer?
A customer can be an organization that owns an entitlement or a current or potential buyer of an entitlement. Typically, entitlements are generated for customers. A customer can have one or more contacts.
Prerequisites for Creating a Customer
A role that includes Customer Management permissions. At minimum, the user needs Add permissions. For details, see Roles.
Customer Status
The Status attribute for a customer can be one of the following:
>Enabled: The customer can log on to Sentinel EMS.
>Disabled: The customer is blocked from logging on to Sentinel EMS.
Creating a Customer
You create a customer from the Customers page.
To create a customer:
1.From the navigation pane, select Customers > Customers to view the Customers page.
2.Click the Add Customer button.
3.Fill in the customer attributes.
4.Click Save.
Customer Attributes
The following table explains the attributes that are used to create a customer:
| Attribute | Description | Required/Optional | Valid Values |
|---|---|---|---|
| Market Group |
Market group to which the customer belongs. The market group specifies a target market for specific catalog elements and their entitlements. The customer can only work with catalog elements and entitlements of its own market group. Each customer can be associated with only one market group. NOTE The Market Group drop-down is available only if the logged-in user is associated with more than one market group. |
Required |
>List of market group names associated with the logged-in user. >The system automatically picks the logged-in user's market group if a single market group is associated with the user. >A "default" value is used if the logged-in user is not associated with any market group. This value is not visible to the user. |
| Name | Name of the customer. Two or more customers can have the same value for customer name. Two or more customers who have the same name are differentiated by the Customer ID. |
Required |
>Alphanumeric >Special characters >0 to 255 characters |
| Customer ID |
Unique identifier for the customer. If not specified, then the value is automatically generated by the system. After you create a customer, the value is read-only and cannot be edited. |
Required |
>Must be unique >0 to 100 characters |
 CRM ID |
The customer relationship management identifier. | Optional |
>0 to 255 characters |
| Description | Additional information about the customer. | Optional |
>Alphanumeric >0 to 510 characters |
|
Additional Attributes |
|||
| External ID | External reference identifier that uniquely identifies the customer in an external system. | Optional |
>Unique across Sentinel EMS for all customers. >Alphanumeric >0 to 60 characters |
| Ref ID | Reference identifier that identifies the customer in an external system. | Optional |
>Alphanumeric >0 to 255 characters |
| Time Zone |
Customer time zone. The start date and the end date of a license belonging to the customer are calculated according to the customer's time zone. This value helps customize the usability period of the licenses and orders for a customer. For example, the order taker and the customer may be located in separate time zones. Specifying this value ensures that the licenses and orders are valid based on the customer's location. You can override the customer time zone by specifying the activatee time zone during activation. For details, see Activations. |
Required |
A time zone from the list. For a list of time zone values, refer to the Sentinel EMS REST API Guide. |
Service-Hosted Cloud Licensing Permissions
The Service-Hosted Cloud Licensing Permissions tab is displayed when a CL key is associated with a customer. This occurs when you create an entitlement that specifies a customer and then activate that entitlement using Produce and Push.
By default, customers inherit the global settings defined in Cloud Licensing Permissions. You can modify the cloud licensing permissions for a specific customer if needed. All accounts associated with the customer inherit any changes that you make.
| Attribute | Description |
|---|---|
| Maximum Number of Accounts |
The maximum number of accounts that can be defined. Possible values: >Unlimited (default) >Number of Network Seats |
| Maximum Number of Registered Machines |
A client machine may be automatically registered with the account when a protected application runs for the first time. Possible values: >1-10. The maximum number of remote machines that are allowed to use this account to access the license server machine. Each machine is automatically registered the first time it accesses the license server machine. When the maximum number of machines are registered, no additional machines can use the account. >Unlimited. An unlimited number of remote machines are allowed to use the account to access the license server machine. The machines are not registered. Default: 5 |
| Waiting Period for Reusing Deleted or Disabled Registered Machines (Days) |
The waiting period represents the number of days that the administrator contact must wait before changing the status of a machine that they disabled or deleted using the Sentinel EMS customer portal. This is relevant only after the first time that the registration status changes. The purpose of this setting is to discourage administrator contacts from performing unauthorized license sharing. How does the waiting period work? Suppose the Sentinel EMS vendor administrator created an account profile for Alex, who is an administrator contact. The first time that Alex runs an application that uses a CL key, his laptop is automatically registered to his account profile. Both the vendor administrator and Alex can see this registration in the Registered Machines tab under the record for Alex's profile on the Accounts page in Sentinel EMS. One day, Alex decides to give his license to his friend, Joan. Alex uses the self-service customer portal to delete or disable the machine where the protected application ran (his laptop). Joan, pretending to be Alex, runs the protected application from her machine. After two days, Joan tells Alex that she doesn't want to use the application anymore. So, Alex opens the customer portal and disables or deletes the machine that was automatically registered when Joan ran the application (Joan's laptop). Since Joan is no longer using the application, Alex decides to run the application on his laptop again, but only two days have elapsed. Since the Waiting Period for Reusing Deleted or Disabled Auto-Registered Machines is set to the default seven days, Alex must now wait for five more days before he can run the application on his laptop. Possible values: >1-30 (An integer representing 1-30 days) >No waiting period. Select the Allow Immediate Reuse check box to override the waiting period and allow deleted or disabled machines to be automatically re-registered immediately. Default: 7 |
| Allow Online Connection to Licenses |
Enables a remote machine with an installed identity string to consume a license from the service-hosted, cloud license manager server. Possible values: Yes or No |
| Allow License Detaching |
(Relevant for both automatic and on-demand detaching) Enables a client machine to detach a license (a network seat) for a protected application from the service-hosted, cloud license manager server whenever a license is required. >Automatic detaching. Detached licenses are deducted from the pool of available networks seats on the CL key. The client machine retains the license up to the number of hours specified even if the connection to the license server is interrupted. This enables the protected application to continue to operate without connection to the license server machine. When the detached license expires, it automatically returns to the pool of network seats on the CL key and is disabled on the machine. Maximum offline duration: 2 hours >On-demand detaching. End users can access a manually detached license from a CL key for a specified number of days. This is useful if they want to work with a protected application and expect to be disconnected from the company’s network for an extended period. On-demand detaching works only in offline mode. To use a manually detached license: On the machine where the CL key is located, an administrator can generate an H2R file that contains a detached license. The administrator transfers the file to the recipient (for example, the end user) who then applies the H2R file on the machine. Maximum duration: 14 days Possible values: Yes or No |
| Allow Concurrency for Detached Licenses |
(Relevant only for on-demand detaching and visible only if Allow License Detaching is set to Yes) Enables a machine with the identity string to detach one or more network seats with concurrency from the license server machine. These seats can then be accessed concurrently on the machine that receives the detached license. A detached license with concurrency can be used to: >Set up second-level license servers. These can be used to provide greater control over the distribution of network seats within an organization and to minimize the overhead of license administration. For more information, see the Sentinel LDK Software Protection and Licensing Guide. >Control the number of local hardware resources used by an application. For example, a protected application can be limited to use 4 out 8 CPUs. This requires a detached license with 4 seats, where access to each CPU is granted after the application logs in to the license. In this example, the fifth login will be denied, ensuring that only 4 CPUs are in use. Possible values: Yes or No |
Associate Contacts
After providing the attribute details, you can use the Associated Contacts pane displayed below to associate contacts with the customer that you are creating. This step is optional. You can create a customer without associating any contact.
If the required contact is not displayed in the list, you can use the Add Contact button in this pane to create a new, standard contact and associate it with the customer. If you want to create an administrator contact, use the Add Contact button on the Contacts page to create and associate the contact with the customer.
Actions for a Customer
The following table lists the actions available for customers:
| Action | Description | |
|---|---|---|
|
Edit |
Updates information for an existing customer. Note: >Customer ID and customer name are not case-sensitive. >Use the Edit action to move a customer from one market group to another. >Editing the market group will also update the associated entitlements and activations of the customer to the modified market group. >When moving a customer from one market group to another, all namespaces of each product in each entitlement of the customer should be available in the modified market group. |
|
Disable | Prevents the customer from logging on to Sentinel EMS. |
|
Enable | Re-enables a customer that is marked as disabled, enabling the customer to access Sentinel EMS. |
|
Delete |
Deletes a customer. You can delete a customer for whom no entitlements |