Data Connectors | Kamiwaza Docs

Documentation for Kamiwaza 0.12.0

Overview

Data connectors in Kamiwaza allow administrators to configure external data source connectors, enabling integration with Microsoft 365, Google Workspace, and other cloud services.

Connector Configuration Includes:

Connectors are managed through the Kamiwaza web UI at Settings → Data Connectors.

Configuring a Connector

Prerequisites

Using the Web UI

  1. Navigate to Settings → Data Connectors
  2. You'll see available connector types:
    • Microsoft 365 - Connect to SharePoint, OneDrive, Outlook, and Calendar
    • Google Workspace - Connect to Drive, Gmail, and Calendar (Coming Soon)
    • Dropbox - Connect to Dropbox storage
  3. Click Configure on the connector you want to set up
  4. Fill in the required configuration details:
    • For Microsoft 365: Azure AD application credentials (Client ID, Client Secret, Tenant ID)
    • Service-specific settings and permissions
  5. Click Save to complete the configuration

Once configured, the connector status will show as "Configured" and users will be able to connect their accounts.

Managing Connectors

Viewing Connectors

In the Settings → Data Connectors page, you can view all available connector types. Each connector card shows:

Viewing Connector Configuration

Click on a configured connector to view its configuration details, including:

Updating a Connector

To update a connector's configuration:

  1. Navigate to Settings → Data Connectors
  2. Click Configure on the connector you want to update
  3. Modify the configuration fields as needed:
    • Application credentials (Client ID, Client Secret, etc.)
    • Service-specific settings
    • Permissions and scopes
  4. Click Save to apply changes

Note: Updating connector configuration may require users to reconnect their accounts if authentication settings change.

Removing a Connector Configuration

To remove a connector configuration:

  1. Navigate to Settings → Data Connectors
  2. Click Configure on the connector
  3. Click Delete to remove the configuration

Warning: Removing a connector configuration will disconnect all users who have connected their accounts.

User Connection Flow

Once an administrator has configured a connector, users can connect their accounts:

  1. Users navigate to their profile or data sources section
  2. They see available connectors that have been configured by administrators
  3. Users click to connect their account (e.g., "Connect Microsoft 365")
  4. They are redirected to authenticate with the external service (OAuth flow)
  5. After successful authentication, their account is connected and they can access data from that service

Security and Access Control

Application Credentials

User Access

Data Access

Connector Status

Each connector displays its configuration status:

Supported Connector Types

Connector Services Status
Microsoft 365 SharePoint, OneDrive, Outlook, Calendar Available
Google Workspace Drive, Gmail, Calendar Coming Soon
Dropbox Dropbox storage Coming Soon

Microsoft 365 Connector

The Microsoft 365 connector allows users to connect their Microsoft accounts to access:

Configuration Requirements:

Best Practices

  1. Application Registration: Create dedicated Azure AD applications for Kamiwaza connectors rather than reusing existing applications
  2. Principle of Least Privilege: Request only the minimum API permissions needed for the connector's functionality
  3. Credential Security: Store application credentials securely and rotate them regularly
  4. User Communication: Inform users about what data and permissions will be requested before they connect their accounts
  5. Testing: Test connector configuration with a test account before making it available to all users
  6. Documentation: Document the required Azure AD permissions and configuration steps for your team
  7. Monitoring: Regularly review which users have connected accounts and ensure connectors remain properly configured

Troubleshooting

Connector Configuration Fails

Users Cannot Connect Their Accounts

Authentication Errors