Configuration - Workspaces

Configuration - Workspaces

1. Collector

• Purpose: Retrieves and summarizes data from linked dataspaces, preparing it for analysis.

• Configuration: Choose models with large context windows (e.g., 16k tokens). Set specific pre-prompts and adjust settings like Top P, Temperature, Presence Penalty, and Frequency Penalty.

• Best Practice: Select a Collector model that aligns with the volume and complexity of the data in your dataspaces.

• Additional Notes: The Collector's efficiency impacts the overall data processing and response quality in the workspace.

• Sample: Pre-prompt configuration for a marketing use case:

Always search for Company Info, any Marketing Material, styling guides.

2. Analyzer

• Purpose: Analyzes the data retrieved by the Collector and formulates detailed responses.

• Configuration: Adjustable for various analysis requirements, including pre-prompts and standard LLM settings (Top P, Temperature, etc.).

• Best Practice: Tailor the Analyzer's settings to suit the specific analysis needs of your workspace's use case.

• Additional Notes: The Analyzer's precision is crucial for the accuracy and relevance of the insights generated.

• Sample: Pre-prompt configuration for a marketing use case:

Purpose: Create a personalized and impactful marketing message based on collected data.

Marketing Content Generation:

Identify Message Type:
Craft the specific type of marketing message the user wants (e.g., promotional email, social media advertisement, personalized offer).
Integrate Relevant Details:
Incorporate all relevant information provided, such as:
Target audience characteristics
Preferred tone (e.g., professional, friendly, humorous)
Desired call-to-action (e.g., "Sign up now," "Learn more," "Get 50% off")
Utilize Company-Specific Data:
If company-specific data is available, seamlessly weave it into the marketing message to personalize and tailor the content.
General Inquiry Handling:

Handle General Queries:
If the user's query does not involve marketing content or company-specific data, proceed by generating a response based on general marketing knowledge and best practices.
Execution:

Generate a highly relevant and effective marketing message by thoughtfully incorporating the collected data.

3. Base Model - "Conductor"

• Purpose: Serves as the orchestrator, managing the workflow between the Collector and Analyzer.

• Configuration: Users can customize pre-prompts and model settings like Top P, Temperature, Presence Penalty, and Frequency Penalty.

• Best Practice: Ensure the Base Model's settings are optimized to facilitate effective interaction between the Collector and Analyzer.

• Additional Notes: The Base Model's configuration significantly influences the efficiency and efficacy of the workspace.

• Sample: Pre-prompt configuration for a marketing use case:

Purpose: Gather essential information to create a tailored and impactful marketing message.

Marketing Content Inquiry:

Identify Message Type:
Determine the specific type of marketing message the user intends to create (e.g., promotional email, social media advertisement, personalized offer).
Extract Relevant Details:
Gather all relevant information provided by the user, including:
Target audience characteristics (demographics, interests, etc.)
Preferred tone (e.g., professional, friendly, humorous)
Desired call-to-action (e.g., "Sign up now," "Learn more," "Get 50% off")
Incorporating Company-Specific Data:
Assess Company-Specific Data:
Determine if the user has provided any data related to their company or target audience.
If available, incorporate this data seamlessly to personalize and tailor the marketing message.
Clarification Questions:

Audience Details: Are there any additional target audience characteristics or segmentation criteria that should be considered?
Preferred Tone: What tone or style would best resonate with the intended audience?
Primary Goal/Objective: What is the primary goal or action that the user wants to achieve with this marketing content?
Company-Specific Data Availability: Is there any existing company-specific data available to enhance the personalisation of this message (e.g., customer personas, brand guidelines)?

4. Dataspaces Linking

• Purpose: To provide the workspace with a relevant scope of data for processing.

• Configuration: Link dataspaces that are closely related to the workspace's intended function.

• Best Practice: Keep dataspaces tightly scoped to the workspace’s specific use case for better data quality and more accurate results.

• Additional Notes: While there's flexibility in linking multiple dataspaces, a strategic selection is crucial for optimal performance.

   

5. Access Control

• Purpose: Manages user permissions within the workspace, controlling data access and operations.

• Configuration: Utilize Active Directory for assigning user and group access to the workspace.

• Best Practice: Assign access based on user roles and workspace requirements, ensuring appropriate data security and functionality.

• Additional Notes: Access control settings are integral to maintaining the security and integrity of the workspace.

   

6. Sandbox

• Purpose: Provides an environment for testing and fine-tuning workspace settings.

• Configuration: Simulate real-world scenarios to validate the workspace's setup.

• Best Practice: Use the Sandbox to experiment with settings made to the workspace.

• Additional Notes: The Sandbox is a valuable tool for preventing potential issues in a live environment.

   

7. API Test

• Purpose: Facilitates testing of API integrations and prompt responses.

• Configuration: Test API calls and validate responses; access Swagger profiles for detailed interactions.

• Best Practice: Regularly test API calls to ensure seamless integration and response accuracy.

• Additional Notes: This feature is essential for maintaining the functionality and reliability of API-based interactions.

   

8. Audit Logs

• Purpose: Tracks changes and activities within the workspace for security and compliance.

• Configuration: Enable audit logging to record all relevant workspace interactions and modifications.

• Best Practice: Regularly review audit logs to monitor workspace usage and identify potential security concerns.

• Additional Notes: Audit logs are crucial for transparency and accountability in workspace operations.