Create New Tenant

Step-by-step guide to creating new tenants in Authonomy Nexus with naming conventions and best practices

Create New Tenant

Add new isolated environments to your Authonomy Nexus instance for different departments, environments, or customer configurations.

Overview

Creating a new tenant establishes a completely isolated environment within Authonomy Nexus. Each tenant maintains its own:

  • User directories and authentication flows
  • SAML/OIDC configurations
  • Application registrations
  • Audit logs and analytics
  • Custom policies and authorization rules

Creation Process

Step 1: Access Tenant Management

Navigate to Settings > Tenants tab to view your current tenant list.

Tenants Tab Tenants tab showing the tenant management interface

Step 2: Open Add Tenant Modal

Click the “Add Tenant” button in the tenant management interface.

The Add Tenant modal will appear with:

  • Tenant name input field
  • Validation rules and requirements
  • Create/Cancel buttons

Step 3: Enter Tenant Name

Provide a descriptive name for your new tenant:

  1. Enter the tenant name in the provided field
  2. Follow naming conventions (see guidelines below)
  3. Verify the name is unique and descriptive

Step 4: Create the Tenant

  1. Review the tenant name for accuracy
  2. Click “Create” to submit the new tenant
  3. Wait for confirmation - The system will validate and create the tenant

Step 5: Verify Creation

After successful creation:

  • A success message will appear
  • The new tenant will be added to the tenant list
  • The tenant will have a unique UUID automatically generated

Naming Conventions

Environment-Based Naming

production
staging
development
testing-2024-q1

Department-Based Naming

hr-department
finance-team
engineering-dev
sales-sandbox

Customer-Based Naming

client-acme-corp
customer-widgets-inc
partner-tech-solutions
demo-environment

Project-Based Naming

project-alpha-dev
migration-testing
integration-staging
security-audit-env

Naming Best Practices

Do:

  • Use descriptive names that indicate purpose
  • Include environment indicators when appropriate
  • Keep names concise but meaningful
  • Use consistent naming patterns across your organization
  • Include dates for temporary environments

Don’t:

  • Use special characters that might cause URL issues
  • Create names that are too similar to existing tenants
  • Use generic names like “test1” or “temp”
  • Include sensitive information in tenant names

Validation Rules

Tenant names must adhere to these requirements:

  • Length: Typically 3-64 characters
  • Characters: Letters, numbers, hyphens, and underscores
  • Uniqueness: Must be unique within your Authonomy instance
  • Format: Cannot start or end with special characters

Automatic Configuration

When a new tenant is created, Authonomy automatically:

Generated Properties

  • Tenant ID: Unique UUID automatically assigned
  • Creation Timestamp: Date and time of tenant creation
  • Default Settings: Basic configuration applied
  • Isolation Boundaries: Security boundaries established

Default Configurations

New tenants start with:

  • Empty user directory
  • Default authentication settings
  • Basic audit logging enabled
  • Standard security policies applied
  • Clean application registry

Post-Creation Setup

After creating a tenant, you’ll typically want to:

Initial Configuration

  1. Configure Identity Providers - Set up SAML/OIDC connections
  2. Create User Accounts - Add initial administrators and users
  3. Register Applications - Configure applications for this tenant
  4. Set Up Policies - Define authorization and security rules

Integration Setup

  1. API Access - Configure API keys and permissions
  2. Webhook Configuration - Set up event notifications
  3. Monitoring Setup - Configure logging and analytics
  4. Backup Procedures - Establish data protection policies

Use Cases for New Tenants

Development Workflows

  • Feature Development: Isolated environments for new features
  • Testing Scenarios: Dedicated spaces for integration testing
  • User Acceptance Testing: Controlled environments for stakeholder review

Organizational Separation

  • Department Isolation: Separate HR, Finance, and Engineering systems
  • Geographic Regions: Different configurations for various locations
  • Compliance Requirements: Isolated environments for regulatory needs

Customer Management

  • Multi-Customer SaaS: Dedicated environments for each customer
  • Partner Integration: Separate spaces for business partner access
  • Demo Environments: Clean environments for product demonstrations

Troubleshooting Creation Issues

Common Problems

Tenant Name Already Exists

  • Error: “Tenant name already in use”
  • Solution: Choose a different, unique name
  • Prevention: Check existing tenant list before creation

Invalid Tenant Name

  • Error: “Invalid characters in tenant name”
  • Solution: Use only letters, numbers, hyphens, and underscores
  • Prevention: Follow naming convention guidelines

Permission Denied

  • Error: “Insufficient permissions to create tenant”
  • Solution: Verify you have tenant management permissions
  • Escalation: Contact system administrator

Creation Timeout

  • Error: “Tenant creation timed out”
  • Solution: Check network connectivity and retry
  • Investigation: Verify system resources and database connectivity

Validation Failures

If tenant creation fails validation:

  1. Check the error message for specific requirements
  2. Verify tenant name meets all validation rules
  3. Ensure uniqueness by checking existing tenant names
  4. Try alternative names if conflicts exist

Best Practices

Planning Before Creation

  • Define the purpose - Clearly identify why you need this tenant
  • Plan the lifecycle - Consider how long the tenant will be needed
  • Design naming strategy - Use consistent, meaningful names
  • Consider dependencies - Think about integrations and data flows

Organizational Standards

  • Approval Process: Implement approval workflows for production
  • Documentation: Record tenant purpose and ownership
  • Lifecycle Management: Plan for tenant maintenance and eventual cleanup
  • Resource Planning: Consider storage and performance implications

Security Considerations

  • Access Control: Plan who will have access to the new tenant
  • Data Classification: Understand what type of data will be stored
  • Compliance Requirements: Ensure the tenant meets regulatory needs
  • Monitoring Setup: Plan security monitoring and audit trails

Next Steps After Creation

Tenant Management Tasks

đź’ˇ Tip: Start with clear naming conventions and document your tenant strategy to make management easier as your organization grows.