Customer

Use Case
User Persona: {{variable.Role - Super Admin}}

Solution

Scenario 1: Customer Configuration

A company, "Tech Innovations," needs to be added to the application as a Customer under the "Technology" domain and subdomain. The Super Admin logs into the system, navigates to the Customer configuration section, and fills in the required details such as the domain, subdomain, customer name, and email ID. Additionally, they fill in optional fields like contact person and address.

The Super Admin logs into the application. They navigate to the Platform Studio and access the Access Control Centre to select Customer. The Super Admin clicks New to add a new customer, enters the necessary details on the configuration screen, and proceeds by clicking Next. The configuration is then submitted and "Tech Innovations" is added as a Customer under the specified domain and subdomain.

Scenario 2: Access Mapping to Tenants

The Super Admin needs to map "Tech Innovations" to multiple tenants, such as "Tenant A" and "Tenant B," along with specific locations for each tenant. This setup is crucial for ensuring that when issues are logged, the correct requestors linked to these tenants are displayed.

During the Customer configuration process, the Super Admin reaches the Access Mapping step. Selects "Tenant A" and "Tenant B" from the dropdown list, choosing the relevant locations for each tenant. After selecting the tenants and locations, clicks Submit to complete the configuration. Now, "Tech Innovations" is mapped to the specified tenants, ensuring appropriate user visibility during issue logging.

Scenario 3: Logging Issues with Tenant Selection

A Service Desk User needs to log an issue for a project associated with "Tenant A." When selecting the tenant, the user must see all requestors related to the "Tech Innovations" customer mapped to this tenant.

The Service Desk User logs into the application and navigates to Manage Incidents page. They select "Tenant A" from the Tenant dropdown. The system automatically displays all Requestors associated with "Tech Innovations" who have been mapped to "Tenant A." The user can then choose the appropriate requestor, complete the issue details, and Submit the request. This streamlined visibility ensures accurate requestor selection and efficient issue logging.