> For the complete documentation index, see [llms.txt](https://docs.clickai.vn/clickai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clickai.vn/clickai-docs/clickai-docs-en/function/database/using-templates.md).

# Using Templates

## Table of Contents

·       \[Introduction to Templates]\(#introduction-to-templates)

·       \[Create a Base from Template]\(#create-a-base-from-template)

·       \[Available Template Categories]\(#available-template-categories)

·       \[Build a Base with AI]\(#build-a-base-with-ai)

·       \[Customizing After Template Creation]\(#customizing-after-template-creation)

·       \[Templates by Popular Use-case]\(#templates-by-popular-use-case)

·       \[Best Practices]\(#best-practices)

&#x20;

## Introduction to Templates

ClickAI Tables provides a Template Gallery with pre-built database structures designed for various industries and departments. Instead of starting from a blank table, you can choose a matching template and start working immediately with optimized tables, fields, views, and relationships.

💡 TIP: Templates save you hours of database design work. You can always customize after creation — add/remove tables, fields, and views to match your actual needs.

&#x20;

## Create a Base from Template

There are 3 ways to create a new Base in ClickAI Tables:

\+ New Base\
├── From Scratch       → Create an empty base\
├── From Template      → Choose from the template library\
└── Build with AI      → AI generates structure from your description

### Steps to Create from Template

1\.     Click + New Base on the Bases tab in your workspace

2\.     Select From Template

3\.     Browse templates by Departments or Industries

4\.     Click on a template to preview its structure:

·       List of tables in the template

·       Fields and data types

·       Pre-configured views

·       Relationships between tables

5\.     Click Create to build the base from the selected template

📝 NOTE: Templates create structure only (tables, fields, views) — they do not include sample data. You can start entering data right away, or import from CSV/Excel files.

&#x20;

## Available Template Categories

### 🏢 By Department

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Department</td><td valign="top">Example Templates</td><td valign="top">Description</td></tr><tr><td valign="top">Marketing</td><td valign="top">Content Calendar, Campaign Tracker, Competitive Analysis</td><td valign="top">Content management, campaign tracking, competitor analysis</td></tr><tr><td valign="top">Project Management</td><td valign="top">Project Tracker, Product Roadmap, Sprint Planning</td><td valign="top">Project management, product roadmap, sprint planning</td></tr><tr><td valign="top">HR &#x26; Recruiting</td><td valign="top">Applicant Tracker, Employee Directory, Onboarding</td><td valign="top">Candidate tracking, employee directory, onboarding process</td></tr><tr><td valign="top">Finance &#x26; Legal</td><td valign="top">Expense Tracker, Invoice Management, Compliance</td><td valign="top">Expense management, invoicing, legal compliance</td></tr><tr><td valign="top">Sales</td><td valign="top">CRM Pipeline, Lead Tracker, Customer Database</td><td valign="top">Sales pipeline, lead tracking, customer database</td></tr><tr><td valign="top">IT &#x26; Operations</td><td valign="top">Bug Tracker, IT Asset Management, Facilities</td><td valign="top">Bug tracking, IT asset management, facilities</td></tr><tr><td valign="top">Supply Chain</td><td valign="top">Inventory Tracking, Order Management, Vendor List</td><td valign="top">Inventory, order management, vendor tracking</td></tr></tbody></table>

&#x20;

## Build a Base with AI

In addition to pre-built templates, you can use AI to automatically generate a database structure tailored to your needs:

### Steps to Build with AI

6\.     Click + New Base → Build with AI

7\.     Select a pre-defined use-case or describe your needs in natural language:

&#x20;  Example: "Manage orders for an online store, including\
&#x20;  customers, products, orders, and delivery status tracking"

8\.     AI analyzes and suggests a structure:

·       Required tables

·       Fields for each table (with appropriate data types)

·       Optimized views (Grid, Kanban, Calendar...)

·       Relationships between tables

9\.     Review and edit the suggestion as needed

10\.  Click Create Base to finalize

💡 TIP: The more detailed your description, the more accurate the AI-generated structure. Be sure to mention: entities to manage (customers, products...), information to capture (name, email, status...), and business processes (pipeline, approvals...).

&#x20;

## Customizing After Template Creation

After creating a base from a template, you have full control to customize:

### Add / Remove Tables

·       Add new tables for data not covered by the template

·       Remove tables that aren't needed

### Edit Fields

·       Add new fields to match your business needs

·       Rename fields for clarity

·       Change data types as needed

·       Remove unused fields

### Create Additional Views

·       Add Kanban Views for workflow management

·       Create Calendar Views for scheduling

·       Add Form Views for data collection

·       Create Gallery Views for visual content

### Set Up Relationships

·       Create Links between new and existing tables

·       Add Lookup/Rollup fields for linked data

·       Build complex relationships (many-to-many)

### Configure Automations

·       Set up Webhooks for data events

·       Connect with ClickAI Workflows for automation

·       Configure permissions for your team

&#x20;

## Templates by Popular Use-case

### 📦 CRM — Customer Management

Template structure:

CRM Base\
├── 📋 Contacts\
│   ├── Fields: Name, Email, Phone, Company, Source, Status\
│   └── Views: Grid (All), Kanban (by Status)\
├── 🏢 Companies\
│   ├── Fields: Company Name, Industry, Size, Website, Revenue\
│   └── Views: Grid (All), Gallery (by Logo)\
├── 💰 Deals\
│   ├── Fields: Deal Name, Value, Stage, Close Date, Owner\
│   └── Views: Kanban (by Stage), Calendar (by Close Date)\
├── 📝 Activities\
│   ├── Fields: Type, Subject, Contact (Link), Date, Notes\
│   └── Views: Grid (All), Calendar (by Date)\
└── Relations:\
&#x20;   ├── Contacts ↔ Companies (Many-to-One)\
&#x20;   ├── Deals ↔ Contacts (Many-to-One)\
&#x20;   └── Activities ↔ Contacts (Many-to-One)

&#x20;

### 📋 Project Management

Template structure:

Project Management Base\
├── 🎯 Projects\
│   ├── Fields: Project Name, Description, Start Date, End Date, Status, Owner\
│   └── Views: Grid (All), Kanban (by Status)\
├── ✅ Tasks\
│   ├── Fields: Task Name, Project (Link), Assignee, Priority, Status, Due Date\
│   └── Views: Kanban (by Status), Calendar (by Due Date)\
├── 🏷️ Milestones\
│   ├── Fields: Milestone Name, Project (Link), Due Date, Completed\
│   └── Views: Calendar (by Due Date)\
└── Relations:\
&#x20;   ├── Tasks ↔ Projects (Many-to-One)\
&#x20;   └── Milestones ↔ Projects (Many-to-One)

&#x20;

### 🛒 E-Commerce — Online Store Management

Template structure:

E-Commerce Base\
├── 📦 Products\
│   ├── Fields: Product Name, SKU, Category, Price, Stock, Image\
│   └── Views: Grid (All), Gallery (by Image)\
├── 👥 Customers\
│   ├── Fields: Name, Email, Phone, Address, Total Orders\
│   └── Views: Grid (All)\
├── 🛍️ Orders\
│   ├── Fields: Order ID, Customer (Link), Total, Status, Order Date\
│   └── Views: Kanban (by Status), Calendar (by Date)\
├── 📋 Order Items\
│   ├── Fields: Product (Link), Order (Link), Quantity, Unit Price, Subtotal\
│   └── Views: Grid (All)\
└── Relations:\
&#x20;   ├── Orders ↔ Customers (Many-to-One)\
&#x20;   ├── Order Items ↔ Orders (Many-to-One)\
&#x20;   └── Order Items ↔ Products (Many-to-One)

&#x20;

### 📰 Content Management

Template structure:

Content Base\
├── 📝 Content Ideas\
│   ├── Fields: Title, Topic, Type, Status, Assigned To\
│   └── Views: Kanban (by Status)\
├── 📅 Editorial Calendar\
│   ├── Fields: Content (Link), Publish Date, Channel, Status\
│   └── Views: Calendar (by Publish Date)\
├── 📊 Performance\
│   ├── Fields: Content (Link), Views, Engagement, Conversions\
│   └── Views: Grid (with Sort by Views)\
└── Relations:\
&#x20;   ├── Editorial Calendar ↔ Content Ideas (Many-to-One)\
&#x20;   └── Performance ↔ Content Ideas (One-to-One)

&#x20;

## Best Practices

💡 TIP: \*\*Choosing the right template:\*\* - Pick the template closest to your use-case — it doesn't need to be a 100% match - Start with a simpler template and expand gradually - Review the preview carefully before creating to understand the structure

⚠️ IMPORTANT: \*\*Effective customization:\*\* - Rename fields/tables to your team's language if needed - Add \*\*Single Select\*\* fields for statuses you want to track with Kanban - Set up \*\*Form Views\*\* early if you need to collect data from external users - Configure \*\*Webhooks\*\* to connect with ClickAI Workflows for automation

📝 NOTE: \*\*Combining with AI:\*\* - Use "Build with AI" when you can't find a suitable template - Describe your business needs in natural language - AI will suggest views and relationships, not just tables and fields


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.clickai.vn/clickai-docs/clickai-docs-en/function/database/using-templates.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
