Tenant Management

Overview

Tenant management enables organizations to create and configure separate, isolated environments within mindzie Studio. Each tenant represents an independent organizational unit with its own users, data, and configurations.

What is a Tenant?

A tenant is a dedicated instance within mindzie Studio that provides:

  • Data Isolation - Complete separation of data between tenants
  • User Management - Independent user accounts and permissions
  • Custom Configuration - Tenant-specific settings and preferences
  • Security Boundaries - Isolated security contexts

Tenant Management Tasks

Create a New Tenant

Step-by-step guide for creating new organizational tenants.

Tenant Configuration

Configure tenant-specific settings including:

  • Display name and branding
  • Default permissions
  • Data retention policies
  • Integration settings

Authentication Setup

Configure how users authenticate to your tenant:

  • Standard identity authentication
  • Azure Active Directory integration
  • Multi-factor authentication settings

Multi-Tenant Scenarios

Enterprise Deployments

Large organizations often use multiple tenants for:

  • Department Separation - Different business units
  • Geographic Regions - Compliance with local regulations
  • Development/Production - Separate environments for testing

Service Provider Model

Managed service providers use tenants for:

  • Client Isolation - Each customer gets their own tenant
  • Service Accounts - Cross-tenant access for support staff
  • Centralized Management - Oversight across multiple clients

Tenant Administration Requirements

Required Roles

  • Tenant Admin - Can manage all aspects of a single tenant
  • Administrator - Can create new tenants and manage cross-tenant settings
  • IT Admin - Can configure technical settings and integrations

Key Responsibilities

  1. Initial Setup - Configure tenant during creation
  2. User Onboarding - Add and configure initial users
  3. Security Configuration - Set authentication and access policies
  4. Ongoing Maintenance - Monitor usage and adjust settings

Best Practices

Tenant Naming

  • Use clear, descriptive names
  • Include organizational unit or purpose
  • Avoid special characters that might cause issues
  • Consider a naming convention for consistency

Security Configuration

  • Enable appropriate authentication methods
  • Configure session timeouts
  • Set password policies (if using identity authentication)
  • Review and audit permissions regularly

Data Management

  • Plan data retention policies upfront
  • Configure backup strategies
  • Document data ownership and access
  • Implement appropriate compliance measures

Common Scenarios

Single Tenant Setup

Most organizations start with a single tenant:

  1. Create primary tenant during initial setup
  2. Configure authentication method
  3. Add users and assign roles
  4. Begin using mindzie Studio

Multi-Tenant Setup

Larger organizations may require multiple tenants:

  1. Plan tenant structure based on organizational needs
  2. Create tenants for each unit/region/purpose
  3. Configure service accounts for cross-tenant access
  4. Implement governance policies

Troubleshooting

Common Issues

  • Cannot Create Tenant - Verify you have Administrator role
  • Authentication Not Working - Check authentication configuration
  • Users Cannot Access - Verify user permissions and tenant assignment
  • Data Not Visible - Confirm correct tenant selection

Next Steps

  1. Create Your First Tenant
  2. Configure Authentication
  3. Add Users to Tenant
An error has occurred. This application may no longer respond until reloaded. Reload ??