> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/engineering-reference/db/tables/tpri_multisite.md).

# tPri\_MultiSite

{% hint style="info" %}
Generated from the staging database schema, with descriptions drafted by agents ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/db/tables/tPri_MultiSite.md).
{% endhint %}

## Description

A multi-site (UI name "Multi-Site Console"), a named set of sites managed together that can share checklist templates and members. Its sites are in tPri\_MultiSiteParent.

<details>

<summary><strong>Table Definition</strong></summary>

```sql
CREATE TABLE `tPri_MultiSite` (
  `id` int NOT NULL AUTO_INCREMENT,
  `uuid` varchar(255) DEFAULT NULL,
  `fName` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `fDescription` text CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci,
  `fImage` varchar(255) DEFAULT NULL,
  `enum_Origin` int DEFAULT '0',
  `fInActive` tinyint DEFAULT '0',
  `fVisible` tinyint DEFAULT '1',
  `fDeleted` tinyint DEFAULT '0',
  `fCreatedTs` bigint DEFAULT '0',
  `fModifiedTs` bigint DEFAULT '0',
  `fDeletedTs` bigint DEFAULT '0',
  `fServerTs` bigint DEFAULT '0',
  `uuid_tUser_CreatedBy` varchar(255) DEFAULT '',
  `uuid_tUser_ModifiedBy` varchar(255) DEFAULT '',
  `excludeFromApi` tinyint DEFAULT '0',
  `excludeFromApiTs` bigint DEFAULT NULL,
  `uuid_tUser_DeletedBy` varchar(255) DEFAULT '',
  PRIMARY KEY (`id`) USING BTREE,
  UNIQUE KEY `uuid` (`uuid`) USING BTREE
) ENGINE=InnoDB DEFAULT CHARSET=latin1
```

</details>

## Columns

| Name                    | Type         | Default | Nullable | Extra Definition |
| ----------------------- | ------------ | ------- | -------- | ---------------- |
| id                      | int          |         | false    | auto\_increment  |
| uuid                    | varchar(255) |         | true     |                  |
| fName                   | varchar(255) |         | true     |                  |
| fDescription            | text         |         | true     |                  |
| fImage                  | varchar(255) |         | true     |                  |
| enum\_Origin            | int          | 0       | true     |                  |
| fInActive               | tinyint      | 0       | true     |                  |
| fVisible                | tinyint      | 1       | true     |                  |
| fDeleted                | tinyint      | 0       | true     |                  |
| fCreatedTs              | bigint       | 0       | true     |                  |
| fModifiedTs             | bigint       | 0       | true     |                  |
| fDeletedTs              | bigint       | 0       | true     |                  |
| fServerTs               | bigint       | 0       | true     |                  |
| uuid\_tUser\_CreatedBy  | varchar(255) |         | true     |                  |
| uuid\_tUser\_ModifiedBy | varchar(255) |         | true     |                  |
| excludeFromApi          | tinyint      | 0       | true     |                  |
| excludeFromApiTs        | bigint       |         | true     |                  |
| uuid\_tUser\_DeletedBy  | varchar(255) |         | true     |                  |

## Viewpoints

| Name                                                                                         | Definition                                                                                                                                             |
| -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [console](https://docs.snapfix.com/engineering-reference/db/tables/viewpoint-12.md)          | Site Console and Multi-Site Console: site details and addresses, site settings, multi-sites, devices and username logins.                              |
| [people-and-sites](https://docs.snapfix.com/engineering-reference/db/tables/viewpoint-20.md) | Who belongs where: organisations, sites, groups, accounts, their site and group memberships, multi-sites, addresses and the user and group type codes. |

## Constraints

| Name    | Type        | Definition             |
| ------- | ----------- | ---------------------- |
| PRIMARY | PRIMARY KEY | PRIMARY KEY (id)       |
| uuid    | UNIQUE      | UNIQUE KEY uuid (uuid) |

## Indexes

| Name    | Definition                         |
| ------- | ---------------------------------- |
| PRIMARY | PRIMARY KEY (id) USING BTREE       |
| uuid    | UNIQUE KEY uuid (uuid) USING BTREE |

## Relations

```mermaid
erDiagram


"tPri_MultiSite" {
  int id PK
}
```

***

> Generated by [tbls](https://github.com/k1LoW/tbls)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/engineering-reference/db/tables/tpri_multisite.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
