# What is a project?

{% hint style="danger" %}
Please note, for most people, including no-code developers, it is not a requirement to understand this structure. This page was written primarily for extra information in order to better understand how instances are related or not related to each other. This content would mainly be of interest to anyone who has a Reseller agreement with Blocworx.\
\
If you are an Enterprise Level client it is likely you are on your own project and do not share with others. Please contact us at <support@blocworx.com> if you'd like to find out more information about your instance.
{% endhint %}

A project represents a codebase + database. An instance is subdomain + domain that is pointing to this project, e.g example1.mydomain.com. It is possible however to have several instances in one project...\
\
example1.mydomain.com\
example2.mydomain.com\
example3.mydomain.com\
\
Some of these instances may be [owners/parents](/blocworx-documentation/no-code-development/manage-blocworx-instances/parent-and-child-instances.md) of other instances.

Each instance has its own admins and user base, however a [Super User](/blocworx-documentation/no-code-development/extra-hidden-features.md#super-user) can access all instances in a project.

If you are reading this and you are being managed by a reseller/Blocworx representative then it is likely they have their own project of which your instance is on.


---

# Agent Instructions: 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://manual.blocworx.com/blocworx-documentation/the-structure-of-blocworx/what-is-a-project.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.