Connections

Connections allow you to configure how you interact with AI models and manage your document database settings. Each connection provides a unique configuration for accessing AI models and includes various settings for document handling, prompt templates, and audit logging.

Creating a Connection

To create a new connection, you'll need to configure several key components:

Name

Every connection requires a unique name that helps you identify its purpose. The name can be up to 40 characters long and should be descriptive of the connection's intended use.

Documents

The Documents feature allows you to enable and configure how your connection interacts with your document database. When enabled, this feature:

• Allows the connection to search through your document database
• Enables document-based interactions with AI models
• Provides tracking capabilities for search results

Prompt Template

Prompt templates help standardize AI responses and ensure consistent output formats. When enabled, you can:

• Use predefined prompt templates for this connection
• Maintain consistency across AI responses
• Standardize the format of AI outputs

Audit Settings

The audit section provides detailed logging options for monitoring and tracking connection usage:

Log Request Body

• Captures the full request body sent to the AI model
• Includes sensitive data
• Should be used with caution due to data sensitivity

Log Response Body

• Records the complete response from the AI model
• May contain sensitive information
• Useful for debugging and monitoring purposes

Best Practices

When configuring connections:

1. Use descriptive names that reflect the connection's purpose
2. Enable document features only when needed to optimize performance
3. Implement prompt templates for standardized interactions
4. Configure audit logging based on your security and monitoring requirements
5. Be cautious with logging sensitive data

Performance Considerations

Keep in mind that enabling certain features, particularly audit logging options, may impact performance. Consider the following:

• Logging full request and response bodies can increase storage requirements
• Extensive logging may affect response times
• Document features may require additional processing time

Security Notes

When working with connections:

• Carefully consider which audit logging features to enable
• Be aware that logged data may contain sensitive information
• Follow your organization's security policies when configuring logging options