Karini AI Documentation
Go Back to Karini AI
  • Introduction
  • Installation
  • Getting Started
  • Organization
  • User Management
    • User Invitations
    • Role Management
  • Model Hub
    • Embeddings Models
    • Large Language Models (LLMs)
  • Prompt Management
    • Prompt Templates
    • Create Prompt
    • Test Prompt
      • Test & Compare
      • Prompt Observability
      • Prompt Runs
    • Agentic Prompts
      • Create Agent Prompt
      • Test Agent Prompt
    • Prompt Task Types
    • Prompt Versions
  • Datasets
  • Recipes
    • QnA Recipe
      • Data Storage Connectors
      • Connector Credential Setup
      • Vector Stores
      • Create Recipe
      • Run Recipe
      • Test Recipe
      • Evaluate Recipe
      • Export Recipe
      • Recipe Runs
      • Recipe Actions
    • Agent Recipe
      • Agent Recipe Configuration
      • Set up Agentic Recipe
      • Test Agentic Recipe
      • Agentic Evaluation
    • Databricks Recipe
  • Copilots
  • Observability
  • Dashboard Overview
    • Statistical Overview
    • Cost & Usage Summary
      • Spend by LLM Endpoint
      • Spend by Generative AI Application
    • Model Endpoints & Datasets Distribution
    • Dataset Dashboard
    • Copilot Dashboard
    • Model Endpoints Dashboard
  • Catalog Schemas
    • Connectors
    • Catalog Schema Import and Publication Process
  • Prompt Optimization Experiments
    • Set up and execute experiment
    • Optimization Insights
  • Generative AI Workshop
    • Agentic RAG
    • Intelligent Document Processing
    • Generative BI Agentic Assistant
  • Release Notes
Powered by GitBook
On this page

User Management

User Management is essential for maintaining a secure and organized system. This enables administrators to control user access, ensuring that individuals have the right permissions and roles.

User Roles

Karini AI platform supports the following user roles:

Admin

Admin role has organization-level access, allowing them to manage and access all resources within the organization.

Copilot

Copilot role have access to the deployed chatbots within the organization.

Power User

The Power User role grants access to a variety of features within the product, with certain limitations compared to the Admin role. Power users can interact with models, prompts, recipes, catalogs, and other resources; however, their ability to modify or access organizational settings and user management functions is restricted.

The specific permissions and capabilities assigned to users with the Power User role are listed below.

Permissions and Access

  1. Model Endpoint

    • Admin Access: Admins have the ability to create both Embedding Model Endpoints and LLM (Large Language Model) Endpoints.

    • Power User Access: Power users can view model endpoints created by Admins but do not have the permission to create or modify model endpoints.

  2. Prompt Management

    • Create Prompts: Power users can create new prompts.

    • View Prompts: Power users can only view and manage their own prompts and do not have access to prompts created by other power users.

  3. Prompt Templates

    • View Templates: Power users can access the default system prompt templates as well as templates created by other users.

    • Create Templates: Power users can create and manage their own prompt templates.

  4. Prompt Optimization

    • Create Optimization Experiments: Power users can design prompt optimization experiments aimed at improving prompt performance.

    • View Optimization Experiments: Power users can only view and track their own optimization experiments.

  5. Catalog Management

    • Create Catalog Schemas: Power users can create new catalog schemas.

    • View Catalog Schemas: Power users can view and manage only the catalog schemas they have created, with no access to schemas created by other users.

  6. Export Functionality

    • Export Recipes: Power users can export their own recipes to build copilots, with access restricted to recipes they have created.

  7. Copilot Management

    • View Copilots: Power users can view their own copilots and access the history of interactions related to those copilots. They do not have access to copilots created by other users.

  8. Recipe Management

    • Create Agent 2.0 Recipes: Power users can create Agent 2.0 recipes for enhancing their applications.

    • View Recipes: Power users can only view their own Agent 2.0 recipes. They do not have access to other types of recipes, such as QnA or GraphRAG.

    • Recipe Execution: Power users can execute their own recipes and view the corresponding results.

  9. Recipe Evaluations

    • Execute Evaluations: Power users can run evaluations on their own recipes to assess their performance.

    • View Evaluations: Power users can only view the evaluations of their own recipes and do not have access to evaluations of recipes created by other users.

  10. Knowledgebase

    • Admin Access: Admins have the ability to create and manage the knowledgebase.

    • Power User Access: Power users can view datasets and use them in prompts and agents but cannot modify or add new datasets.

  11. Guardrails

    • View Guardrails: Power users can view only the guardrails created by Admins. They can utilize these guardrails in prompts, agents, and copilots, but are not permitted to create or modify them.

  12. Organization

    • View Organization Page: Power users have access to the organization page in a read-only capacity. They cannot edit or make changes to organizational settings.

  13. User Management

    • Admin Access: Admins can add, remove, and manage user accounts.

    • Power User Access: Power users do not have access to user management functionalities and cannot view or manage user accounts within the system.

PreviousOrganizationNextUser Invitations

Last updated 1 month ago