A Document360 project is a self-contained workspace that holds all your knowledge base content — articles, categories, subcategories, home page, users, readers, groups (for private and mixed projects), and custom configurations. Creating a project is the first step to building any knowledge base in Document360, whether you're documenting software, SOPs, APIs, or user manuals.
How to create a project in Document360
Access the dashboard
Log in to the Document360 portal with your account to access the Dashboard.
If you are already inside a project, click the Document360 logo in the top navigation bar to return to the Dashboard.Click the + Project button in the top-right corner.
Choose your use case
Select your primary use case and click Get started.
Use case | Description |
|---|---|
Knowledge base platform | Create a centralized hub where all your team's knowledge and resources are stored. It helps your team quickly find answers and enhances customer self-service. |
Software/Technical documentation | Efficiently organize and maintain all your software or technical documentation — product features, APIs, release notes, and more. |
SOP documentation | Create detailed SOPs that your team can follow consistently, reducing errors and facilitating employee onboarding. |
User manual | Develop comprehensive user manuals that guide customers or team members through your product's features and usage. |
API documentation | Document detailed information about API endpoints, request and response formats, authentication methods, and examples. Selecting this redirects you to the API setup flow. |
Others | Choose this if your use case does not fall into the predefined categories. |
Select a template
Select up to two content templates that match the type of documentation you plan to create. These templates are embedded in your project during creation to give you a head start.
NOTE
Based on your selection, these templates will be embedded within your project during creation. However, your selection does not limit you from using other features or creating different types of content.
If you selected API Documentation as your use case, this step is skipped and you are redirected to API setup instead.
Knowledge base platform templates
If you have selected the Knowledge base platform in step 3, you can choose any two templates from the list below.
Template | Purpose |
|---|---|
Getting started guides | Help new users quickly understand and begin using your product with clear, step-by-step instructions. |
How-to guides | Provide detailed instructions for specific tasks, enabling users to fully utilize your product's features. |
FAQs | Address common questions at any stage of the user journey, reducing support queries. |
Policy & procedures | Outline essential organizational protocols to help users understand and adhere to company guidelines. |
Software/Technical documentation templates
If you have selected Software/Technical documentation in step 3, you can choose any two templates from the list below.
Template | Purpose |
|---|---|
Release notes | Keep users informed about updates, new features, bug fixes, and improvements with each software release. |
Software Design Documentation (SDD) | Outline software architecture and design, including diagrams and specifications for development guidance. |
Software Requirement Documentation | Describe the software's purpose, functionalities, and environment to ensure development aligns with project goals. |
Product Requirement Documentation (PRD) | Define the product's purpose, value, and functionalities to meet user needs and business objectives. |
Process documentation | Document detailed steps and procedures involved in software development to standardize workflows. |
User guide | Give comprehensive instructions on using your product, covering all features and functionalities. |
SOP documentation templates
If you have selected SOP documentation in step 3, you can choose templates from the list below.
Template | Purpose |
|---|---|
Compliance policies and procedures | Ensure your organization meets regulatory requirements by documenting policies that enforce compliance. |
Operation SOP | Enhance efficiency and productivity by standardizing operational procedures across your organization. |
User manual templates
If you have selected the User manual in step 3, you can choose any two templates from the list below.
Template | Purpose |
|---|---|
Installation manual | Provides all necessary setup information, including product overview, specifications, and assembly instructions. |
Instruction manual | Offers step-by-step assembly and usage instructions with diagrams and safety warnings. |
Maintenance manual | Provides detailed instructions for regular upkeep, troubleshooting, and repair procedures. |
Training manual | Provides comprehensive guidance on installation, operation, troubleshooting, and user training. |
Operations manual | Provides detailed instructions for daily maintenance and troubleshooting for effective platform management. |
Personalize your knowledge base
Enter your company's website URL. Document360 analyzes your site and uses AI to generate relevant content, branding elements, and a structured documentation framework.
If you want to skip this step, the domain defaults to the one linked to your registration email.
Set brand guidelines
Review the automatically populated project name, default language, branding logo, and brand colors extracted from your website URL. Edit any fields as needed.
Your browser's language settings determine the default language. English is selected by default if your browser language is not supported.Preview your knowledge base site in the right-side panel.
NOTE
If you choose Spanish or Brazilian Portuguese as your default language, the portal language is set to Spanish or Brazilian Portuguese. Otherwise, English is the default portal language.
The branding logo and primary/secondary colors are extracted from your website. If you choose to Skip this step, the project name is derived from your registration email and Document360's default logo and colors are applied.
Set documentation privacy
Choose the privacy setting for your knowledge base site:
Privacy mode | What it means |
|---|---|
Private | Restrict access so that only registered users can view and interact with the content, keeping it secure and internal. |
Public | Make the knowledge base accessible to everyone, including external users, with no login required. |
Mixed | Combine private and public access — some sections are visible to the public while others are restricted to registered users only. |
Click Next to proceed.
NOTE
You can update privacy settings at any time after project creation from Settings > Users & permissions > Reader access. For more information, see Site access.
Beyond site-level privacy, Document360 also lets you control access at the user level. You can assign roles and permissions to team members, restricting or granting access to specific features and content based on their responsibilities. For more information, see Roles and permissions.
Access the knowledge base portal
Once setup is complete, you are taken into the Document360 knowledge base portal.
For Knowledge base platform, Software documentation, SOP documentation, or User manual use cases: Document360 automatically generates relevant articles and categories based on your selected use case and website content. Each category includes at least 2–3 AI-generated articles, and subcategories are created where necessary. If your selected language is supported by Eddy AI, the documentation is generated in that language; otherwise it defaults to English. If no relevant content is found at the provided URL, pre-loaded articles based on your use case and templates are shown.
NOTE
Articles generated by Eddy AI are published first and then automatically set to draft mode. You can review and update them as needed.
Once your project is created, you can customize its appearance and structure from Settings — including the home page, themes, branding, and category hierarchy.
For API documentation use case: You are redirected to the API documentation workspace. You will see the API reference for the specification you provided during onboarding. If no specification was provided, a sample Pet Store API reference is available.
Switching between projects
Once you have multiple projects, you can switch between them from within the knowledge base portal in two ways.
Using the Projects dropdown
From the Projects dashboard
Switching projects using the project selection menu
From any module in the knowledge base portal, click the project selection menu in the top navigation bar.
Each project entry shows the Project Name, Reader access type — Public , Private , or Mixed — and a Sandbox label if it is a Sandbox project.
Click the project you want to open.
Switching projects using the projects dashboard
Click the Document360 logo in the top navigation bar.
Alternatively, click the project selection dropdown in the top navigation bar and select Manage projects footer at the bottom of the dropdown.
You are redirected to the Your projects page, where all projects you own or are associated with are listed.
Click the project tile you want to navigate to.
NOTE
You can identify which project you are currently working in by checking the project name displayed in the top navigation bar of the knowledge base portal.
Project details
Item | Detail |
|---|---|
Project trial period | Each new project includes a 14-day free trial. A separate subscription is required after the trial ends. |
Onboarding language support | The onboarding flow supports English, Spanish, Brazilian Portuguese, German, and Swedish. The portal itself supports English, Spanish, and Brazilian Portuguese only. |
Best practices
Name your project clearly before creating it. The project name influences the default URL and branding. Changing it after setup requires additional configuration steps.
Use a sandbox project for testing. Before changing themes, workflows, or integrations in a live project, test your changes in a sandbox to avoid disrupting your readers. See Creating a sandbox project.
Keep one project per distinct knowledge base. Avoid mixing unrelated documentation in a single project. Separate projects ensure independent access control, branding, and analytics.
FAQ
Does Document360 support different languages in the onboarding flow?
Yes, the onboarding flow supports English, Spanish, Brazilian Portuguese, German, and Swedish. However, the Document360 portal itself currently supports only English, Spanish, and Brazilian Portuguese.
What is a "Sandbox" project, and how is it different from a regular project?
A Sandbox project is an isolated test environment where you can experiment with settings, designs, and workflows without affecting your live knowledge base. It appears with a Sandbox label in the project dropdown. For more information, see Creating a sandbox project.
How does Document360 handle version control for articles?
Document360 maintains a comprehensive article version history called Article revisions. Every change to an article is automatically saved and tracked, allowing you to revert to any previous version if needed.
How can I request access to a project I am not associated with?
Contact your team administrator or the project owner and ask them to add you. They can assign you an appropriate portal role and content access from Settings > Users & permissions.