Skip to main content

Tenant Settings

Tenant Settings provides administrators with centralized control over tenant configuration.
It enables the management of users, roles, policies, namespaces, and settings from one place—ensuring secure access, clear visibility, and consistent administration across the platform.

Tasks Overview


Tip: Start by defining Policies, then create Roles, then add Users and assign them to Namespaces.

Overview​

Tenant Settings ensures each tenant is configured with the right access controls, structure, and platform-level settings.

Tenant Settings helps administrators:

  • Control who can access the platform and what they can do
  • Organize users and resources into namespaces
  • Enforce security using roles and policies
  • Configure tenant-level settings such as branding and integrations

Core Functional Areas​

These are the core building blocks of tenant configuration. Together, they define structure, permissions, and administration workflows.

Namespaces

What you do:

  • Organize assets and devices into logical namespaces.
  • View namespace details such as associated users, assets, and devices.
  • Add, edit, or remove namespaces as needed.

Why it matters: Namespaces isolate business divisions so each team can operate independently without data overlap (e.g., airport staff vehicles vs catering vs ground handling).

Users

What you do:

  • Create, edit, and manage users.
  • Assign roles, namespaces, and policies to control access.
  • Manage two user types: Normal and Virtual.

Why it matters: Controls who can access the system, enforces accountability, and improves collaboration by assigning the right permissions to the right people.

Roles

What you do:

  • Define roles for applications and corporate functions.
  • Link roles to one or more policies.
  • Assign roles to users for consistent access control.

Why it matters: Ensures the right users have the right level of access, reducing errors and improving security through structured permissions.

Policies

What you do:

  • Configure access permissions for services and modules.
  • Define allowed actions (View, Edit, Create, Delete).
  • Assign policies to roles for scalable control.

Why it matters: Enforces organizational rules, compliance, and secure operational practices across users, data, and assets.

Settings

What you do:

  • Manage tenant-wide branding (logo, currency).
  • Generate and copy API keys for external integrations.
  • Update or delete tenant branding assets.

Why it matters: Ensures the tenant is configured correctly and ready for operational use and integrations.

Persona Use Cases​

Tenant Settings is primarily used by administrators responsible for access control, compliance, and tenant readiness.

System Administrator

  • Sets up policies and roles before adding users.
  • Manages namespaces to separate assets and devices across teams.
  • Uses dashboards and logs for audit and compliance.
  • Updates branding and integrations for tenant requirements.

Key Features​

Tenant Settings combines structure, security, visibility, and configuration into a single administrative experience.

  • Flexible Namespace Management: Group assets and devices into tailored namespaces to match business units or projects.
  • Secure Access with Roles & Policies: Enforce access control with role-based assignment and policy permissions.
  • Real-Time Visibility: Use summaries and logs to understand tenant activity and configuration health.
  • Custom Branding & Integrations: Apply tenant branding and generate API keys to extend integrations.

Why Tenant Management Matters​

Strong tenant management improves security, scalability, and governance across all modules and users.

  • Security: Roles and policies ensure users only access what they need.
  • Efficiency: Centralized control reduces time spent on configuration.
  • Compliance: Structured roles and audit-ready logs support accountability.
  • Scalability: Namespaces simplify operations as the tenant grows.
  • Consistency: Branding and API integration keep platform experience aligned.

Examples and Scenarios​

These scenarios represent common setup flows and best practices for configuring a new or growing tenant.

1) Setting Up a New Tenant​

  • Create core Policies defining allowed actions.
  • Group policies into Roles such as Admin, Supervisor, Technician.
  • Add Users and assign them to roles and namespaces.
  • Validate setup using Dashboard summaries and activity overview.

2) Multi-Namespace Management​

  • Create namespaces for different departments (e.g., Facilities, IT).
  • Assign relevant users and assets to each namespace.
  • Apply role-based access to ensure separation of duties.

3) Policy and Role Alignment​

  • Define a policy granting “View” and “Edit” for a specific module.
  • Create a role (e.g., Facility Manager) using the policy.
  • Assign the role to selected users for controlled access.

4) Branding and API Integration​

  • Upload the tenant logo for portal branding.
  • Select preferred currency for cost reporting.
  • Generate an API key to integrate with third-party systems.