Instinct IQ Platform Overview and Management

Chapter 1: Introduction

• Introduction to Instinct IQ as a platform
    - The platform operates with different instances for each customer.
    - Users log in as specific types (e.g., CTPL) to separate instances.
    - Each instance operates under a unique domain URL, hosted separately:
      - Example: ctplqa.flowsmart.ai versus sop.flowsmart.ai, each pointing to different servers.
      - Ensures that customer data is isolated per instance.

• Example Scenario with Safety App:
    - Use case involving Tarapagati restaurant chain.
      - Centers located in Tamil Nadu, Karnataka, Andhra Pradesh (AP), and Telangana.
      - Participation in a survey program requires separate reporting structures.
      - Employee hierarchy includes:
        - General Manager: e.g., Tamil Nadu GM.
        - Reporting Managers: e.g., various managers at different centers.
        - Survey Participants: E.g., 800 survey participants in total across different states.
    - Expansion example with Whirlpool, which has factories in Uttar Pradesh, Mumbai, and Pune, each with unique roles and responsibilities.

Chapter 2: Select The Company

• Development of the Safety App:
    - Designed as a common application for all users, accessible via different URLs.
    - User experience involves selecting:
      - Company (Level 1 choice)
      - Workplace (second level choice)
    - After selecting company and workplace, users can browse tailored content.
    - URL structures depend on logged-in user and company affiliation:
      - Example: Deepakar might see workpool.safety.com or talapagati.safety.com based on his selection.

• The user association system ensures:
    - Automatic company selection with auto-selected workplace for those with only one option.
    - Ability for users to switch workplaces after initial login.

Chapter 3: Create New User

• Customer limitations:
    - A customer can only belong to one company, while back office users can access multiple companies.

• Back office user access explained in detail:
    - Upon logging in, back office users must still select a company and workplace before accessing the site.
    - Admin access allows management of various aspects, but selection of a company is necessary for navigation.

• User creation process:
    - Users can create new accounts within their designated company scope.
    - The interface remains tenant-scoped which means user actions are linked to the company currently being viewed.
    - New user accounts are created under the selected tenant for permissions management.

Chapter 4: User Navigation

• Typical user navigation structure outlined:
    - Upon logging in, the application identifies the customer based on the domain name.
    - Automatically redirects to the default workplace (e.g., Tamil Nadu). Users can switch workplaces easily within the app.
    - Admins, even when logging in, are required to select a tenant each time for security.

Chapter 5: New System User Privileges

• System user capabilities:
    - Not all system users can create new users or tenants; this is access-controlled.
    - The user interface will reflect privileges some logged-in users will have based on their access level.
• The creation of new users can only occur in the relevant tenant, ensuring that the user only interacts with their assigned tenant.

Chapter 6: Creating a Ticket

• Overview of ticket creation and its associated processes:
    - Users must establish a reusable service approach to avoid redundancy when developing.
    - Importance of centralized permission checks discussed to avoid security vulnerabilities when users develop features.
    - User experience and design frameworks need to be emphasized, promoting user feedback during iterations.

Chapter 7: Conclusion

• Acknowledgment of the complexity in coding and user interface discussions.
• Continuous feedback loop encouraged throughout the development process to enhance the final output.
• Final thank yous exchanged; emphasis on collaboration and feedback moving forward.