Tenant Structure Overview

This page provides a comprehensive overview of how SignalSync organizes tenants, users, products, and access control. Understanding this structure is essential for effective tenant administration.

Hierarchy Diagram

The following diagram illustrates the relationships between all major components in the SignalSync tenant structure:

Core Concepts

Tenant

The Tenant represents your organization in SignalSync. It is the top-level entity that encompasses all users, customers, products, and configurations.

Key characteristics:

• Products are licensed at the Tenant level
• Created by SignalSync System Administrator (Cloud Administrator)
• One Tenant Admin user is created during initial setup
• All organizational data and configurations exist within the tenant boundary

note

Example: If your company "ABC Corporation" subscribes to SignalSync, "ABC Corporation" is the Tenant.

Products

Products are the functional modules that your organization licenses from SignalSync. Each product provides specific business capabilities.

Relationship: Tenant → Products (1:many)

Key characteristics:

• Licensed at the Tenant level (organization-wide availability)
• Each product contains predefined Processes
• Products generate System Profiles automatically upon licensing
  

note

Examples of Products:

• Master Data - Define and manage core entities
• Facility Maintenance - Manage maintenance tasks, work orders, and service requests
• Contract Management - Handle contracts and agreements
• Graphical Workflow Engine (GWE) - Create and manage business processes
• Rule Chains Engine - Build and execute integration rules

---

Processes

Processes are logical groupings of related tasks within a Product. They represent distinct business workflows or functional areas.

Relationship: Products → Processes (1:many)

Key characteristics:

• Grouped by the Product they belong to
• Two types:
  • Default Processes: Predefined by SignalSync (cannot be modified)
  • Custom Processes: Created by Tenant Administrator for specific needs
• Assigned to Profiles to grant user access
  

note

Examples from Facility Maintenance Product:

• Corrective Work - Handle reactive maintenance and repairs
• Preventive Work - Schedule and manage preventive maintenance
• Client - Request maintenance services
• Supplier - Process and fulfill maintenance requests
• Reports - Generate maintenance analytics and reports

---

Tasks

Tasks are individual UI components within a Process. They represent specific actions or screens that users can access.

Relationship: Processes → Tasks (1:many)

Key characteristics:

• Appear as items in the Process Navigator
• Each Task opens a specific user interface
• Tasks are the finest-grained level of access control
  

note

Example: Within the "Corrective Work" Process, Tasks might include:

• "Report Incident"
• "Maintenance Console"
• "Maintenance Portal"

---

Customers

Customers represent distinct business entities, departments, or subdivisions within your organization.

Relationship: Tenant → Customers (1:many)

Key characteristics:

• All Users must belong to a Customer
• Used for organizational segmentation
• Future functionality will include Security Groups assigned to Customers for RBAC/ABAC access control
• Enables multi-department or multi-location management
  

note

Examples:

• Departments: "IT Department", "Facilities", "HR"
• Business units: "East Region", "West Region"
• Subsidiaries: "ABC Manufacturing", "ABC Services"

Future Enhancement

Security Groups will be assigned to Customers to restrict access to specific Entities (Buildings, Assets, PM Procedures, etc.) using Role-Based Access Control (RBAC) and Attribute-Based Access Control (ABAC).

---

Users

Users are individual people who access the SignalSync application. Every user must be associated with a Customer.

Relationship: Customers → Users (1:many)

Key characteristics:

• Must belong to exactly one Customer
• Access to functionality is determined by assigned Profiles
• Can have multiple Profiles assigned
• Linked to User Identity for Employee/Supplier association

---

Profiles

Profiles are access containers that group Processes together. They determine what functionality a User can access.

Relationships:

• Users → Profiles (many:many) - Users can have multiple Profiles
• Processes → Profiles (many:many) - Profiles can contain Processes from multiple Products

Key characteristics:

• Two types:
  • System Profiles: Automatically generated when Products are licensed (e.g., "Facility Manager", "Supplier", "Client")
  • Custom Profiles: Created by the Tenant Administrator by combining processes from multiple licensed products
• Profiles contain Processes, which in turn contain Tasks
• Can optionally have a Default URL or Home Page assigned
  

note

System Profile Examples:

• Facility Manager - Contains: Corrective Work, Preventive Work, Reports
• Supplier - Contains: Supplier Process (to report and manage maintenance requests)
• Client - Contains: Client Process (to request maintenance tickets)

Custom Profile Example: A "Supervisor" who needs access to both maintenance and contract management might receive a Custom Profile containing:

• Facility Maintenance: Corrective Work, Preventive Work
• Contract Management: Manage Contracts, Invoices and Payments

---

Default URL and Home Page

Profiles can be configured with either a Default URL or a Home Page to customize the user's landing experience.

Default URL

A Default URL is a management console page (typically built with the Graphical Workflow Engine) where users can initiate and manage workflows.

Key characteristics:

• Takes priority over Home Page if both are configured
• Users are automatically redirected to this URL upon sign-in
• Provides action-oriented interface for workflow management
  

note

Example: A Service Catalog page where users can submit different types of maintenance requests.

Home Page

A Home Page is a dashboard that displays widgets, charts, and summarized information.

Key characteristics:

• Used if no Default URL is configured
• Users can select their preferred Home Page in "My Account" settings
• Provides overview and analytics

note

Example: A Maintenance Dashboard showing request statistics by type, location, status, and priority.

Priority

If a Profile has both Default URL and Home Page configured, the Default URL takes priority and will be displayed when the user signs in.

---

User Identity

User Identity creates the link between a SignalSync User and an organizational entity (Employee or Supplier).

Relationship: Users → User Identity (1:1)

Key characteristics:

• One-to-one relationship with User
• Links to either Employee (internal) or Supplier (external) entity
• Each User Identity must be assigned to one entity type
• Synchronization can be:
  • Automatic: Based on email address matching
  • Manual: Tenant Admin manually maps Users to identities

Synchronization Process:

1. Tenant Admin clicks "Synchronize Users"
2. System matches User email addresses with Employee/Supplier email addresses
3. Or, Tenant Admin manually selects the corresponding identity for each User

---

Employee

Employee represents an internal member of your organization.

Relationship: User Identity → Employee (1:1)

Key characteristics:

• Part of your organization
• Internal entity with full access rights
• Typically has broader access to organizational data
  

note

Example: A facility manager, maintenance technician, or department supervisor employed by your organization.

---

Supplier

Supplier represents an external entity that provides services or products to your organization.

Relationship: User Identity → Supplier (1:1)

Key characteristics:

• External entity
• Limited access focused on specific tasks
• Can access the application to fulfill assigned work
• Typically has restricted access to only their assigned tasks
  

note

Example: An external contractor who receives maintenance work orders, completes tasks, and logs work hours and costs.

Relationship Summary

From	To	Cardinality	Description
Tenant	Products	1:many	A tenant can license multiple products
Tenant	Customers	1:many	A tenant can have multiple customers
Products	Processes	1:many	Each product contains multiple processes
Processes	Tasks	1:many	Each process contains multiple tasks
Customers	Users	1:many	Each customer can have multiple users
Users	Profiles	many:many	Users can have multiple profiles; profiles can be assigned to multiple users
Processes	Profiles	many:many	Profiles can contain processes from multiple products
Users	User Identity	1:1	Each user has one user identity
User Identity	Employee	1:1	User identity links to either employee or supplier (exclusive)
User Identity	Supplier	1:1	User identity links to either employee or supplier (exclusive)

Practical Example

Let's walk through a complete example:

Scenario: ABC Corporation licenses SignalSync as an integrated platform for real estate portfolio management, covering lease contracts and facility maintenance operations.

1. Tenant: ABC Corporation
2. Products Licensed: Facility Maintenance, Contract Management, Master Data
3. Customers Created:
   • IT Department
   • Facilities Department
4. Users in Facilities Department:
   • John Smith (Facility Manager)
   • Jane Doe (Maintenance Supervisor)
   • Mike Wilson (External Contractor)
5. Profiles Assigned:
   • John Smith: "Facility Manager" System Profile (Corrective Work, Preventive Work, Reports)
   • Jane Doe: Custom Profile (Corrective Work, Preventive Work, Contract Viewing)
   • Mike Wilson: "Supplier" System Profile (Supplier Process only)
6. User Identities:
   • John Smith → Employee (FMS001)
   • Jane Doe → Employee (FMS002)
   • Mike Wilson → Supplier (SUP001)
7. Home Page:
   • John and Jane see a Maintenance Dashboard
   • Mike sees a Service Catalog to view assigned work orders

Configuration Workflow

As a Tenant Admin, you typically follow this workflow:

1. License Products - Handled by SignalSync System Administrator
2. Create Customers - Define your organizational structure
3. Create Users - Add users and assign them to Customers
4. Assign Profiles - Grant users access by assigning System or Custom Profiles
5. Synchronize Identities - Link users to Employee/Supplier entities
6. Configure Profiles - Optionally set Default URLs or Home Pages for each Profile