Skip to main content

Tenants

In AutomatR Orchestrator, a "tenant" is a logical grouping mechanism that allows organizations to isolate and manage their robotic process automation (RPA) resources, such as bots, processes, and credentials. Tenants are particularly useful in multi-tenant environments where multiple organizations or business units share the same Orchestrator instance.

Here's a more detailed explanation of tenants in AutomatR:

Tenants in AutomatR​

  1. Logical Isolation: A tenant provides logical isolation, allowing different entities (organizations, departments, or projects) to operate independently within the same Orchestrator environment.

  2. Separate Environments: Each tenant has its own set of resources, including bots, processes, credentials, and queues. This separation ensures that the activities of one tenant do not interfere with those of another.

  3. User Management: Tenants have their own user management, allowing administrators to control access and permissions for users within a specific tenant. Users assigned to a tenant can perform actions only within that tenant's scope.

  4. Credentials and Queues: Credentials and queues are also tenant-specific. This means that credentials and queues are isolated and can be defined separately for each tenant.

Adding Tenants in AutomatR​

Adding tenants in AutomatR Orchestrator involves the following steps:

  1. Log in to AutomatR Orchestrator as an administrator.

  2. In Orchestrator, go to the Hubs page.

  3. Click on the Add(+) button to add a new Hub(Tenant). Provide the necessary information, such as the Hub Name and Hub Type.

    FieldDescription
    Hub NameIt is a user-defined identifier that distinguishes the hub from other network components or computing entities. It serves as a human-readable label for easy recognition and management of the hub. Users can choose a descriptive and meaningful name that aligns with the purpose or location of the hub within their organization.
    Hub TypeYou can choose between On-Premises and Cloud Hubs based on factors such as security requirements, cost considerations, scalability needs, and the nature of their applications. In many cases, hybrid solutions that combine elements of both On-Premises and Cloud environments are also adopted to leverage the benefits of each approach.
    The Hub Types in AutomatR refers to the deployment model or location of the hub. It offers two main types of Hubs:
    Hub Type Description
    Cloud A Cloud Hub refers to a network infrastructure or computing environment where applications, services, and data are hosted and delivered over the internet by a third-party cloud service provider. The organization outsources its computing needs, gaining benefits like scalability, pay-as-you-go pricing, reduced maintenance overhead and users can access the resources remotely via the internet.
    On-Premises (On-Prem) In an On-Premises Hub, all hardware, software, and networking components are physically located within the organization's own premises or data center. The organization owns, operates, and maintains the infrastructure, offering higher control, security, and customization options.

    Both Cloud and OnPrem Hubs are integral parts of the AutomatR Automation Platform, empowering organizations to maximize their automation potential and drive digital transformation initiatives. By offering dedicated environments for different automation-related activities, AutomatR Hubs enhance collaboration, streamline automation workflows, and facilitate data-driven decision-making for more successful automation implementations.

  4. Configure additional settings for the tenant, including user permissions, host settings, and licensing information.

  5. Click Add to save the tenant configuration, and if required, activate the tenant to make it operational.

Using Tenants in AutomatR​

Once tenants are added, they can be used to organize and manage RPA resources effectively:

  1. User Assignment: Assign users to specific tenants, controlling their access and permissions within the assigned tenant.

  2. Resource Configuration: Configure bots, processes, credentials, and queues specific to each tenant. This ensures that resources are dedicated to the tenant's needs.

  3. Isolation of Data: Tenants provide isolation of data, ensuring that processes and data from one tenant do not impact or interfere with those of another tenant.

  4. Independent Operation: Tenants operate independently, allowing organizations to scale their RPA initiatives across different business units or projects within a single Orchestrator instance.

  5. Security and Compliance: Tenants contribute to enhanced security and compliance by segregating data and ensuring that access is restricted to the appropriate users within the defined scope of the tenant.

In summary, tenants in AutomatR Orchestrator provide a structured and isolated environment for managing RPA resources, allowing organizations to scale their automation initiatives and collaborate effectively in multi-tenant environments.