> For the complete documentation index, see [llms.txt](https://help.stackdx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stackdx.com/projects/company-owned-projects/overview.md).

# Overview

Company Owned Projects are projects that have been created by your company to easily manage and share their Land & Asset data and documents either with internal users or externally with other companies. Land Files or Assets and their documents are organized into specific projects for easier access and management and can be utilized when transferring documents when transactions occur between companies. The projects can be accessible to certain individuals at the company or all users depending on the project settings. 

Navigate to the Projects Grid by clicking the 'Projects' menu to the left of the page. This will display all of the available Company Owned Projects you have access to view.

<div align="left"><figure><img src="https://3514207084-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FClAjQMgk4tfbLAMWKVCZ%2Fuploads%2FWuWMBWNKCoXysaWQVe4L%2Fimage.png?alt=media&amp;token=b6024dd8-e2c4-4a54-a460-9738371285c5" alt="" width="563"><figcaption></figcaption></figure></div>

The project information will be displayed on the Projects Grid including the Project Description/Name, Type, Owner, Internal Access and summary of the content totals.

To view the contents of a project click either the links in the ‘Related To’ column (ie. Mineral, Surface, Location, Wells, etc.) or the project description.

<div align="left"><figure><img src="https://3514207084-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FClAjQMgk4tfbLAMWKVCZ%2Fuploads%2FfVbOirlUV888wQlDEpNG%2Fimage.png?alt=media&amp;token=11994439-9ff5-4983-bd9b-b69ed0fa1ea4" alt=""><figcaption></figcaption></figure></div>

#### Projects Grid Overview <a href="#projects-grid-overview" id="projects-grid-overview"></a>

<div align="left"><figure><img src="https://3514207084-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FClAjQMgk4tfbLAMWKVCZ%2Fuploads%2FeCgdsATE5Tcsx2HiTDEK%2Fimage.png?alt=media&amp;token=a8078366-8062-4cbd-af98-fe3bf3dd29e5" alt=""><figcaption></figcaption></figure></div>

1. **Search/Filter** - Search for projects by the available criteria (ie. Description, Owner, Origin, Project Type, Project Status, Has External Access). See Search & Filter section for more details.&#x20;
2. **Description** - The name of the project
3. **Project Type** - The type of project

There are 6 different types of projects - Internal, Land System, Corporate Layer, Vendor, Partner, VDR.

<details>

<summary>Types of Projects</summary>

**Internal**: The project is created for internal users to view and organize land files or assets

**Land System**: The project was originally created in CS Land and added to StackDX in the nightly data sync.&#x20;

{% hint style="info" %}
Note: Projects created from CS Land cannot add/remove Land Files or Assets within StackDX any changes will need to done in the land system.
{% endhint %}

**Corporate Layer**: Layers created in your site for users to quickly access specific data (ie. All Active Wells, All Active Mineral Files, etc.). These layers are typically updated nightly.

**Vendor**: The project is created with the intention to share and receive land and asset documents with a vendor company (ie. Environmental Company)

**Partner**: The project is created with the intention to share and receive land and asset documents with a partner company (ie. Another Oil & Gas Company)

**VDR**: The project is created with the intention to share and potentially transfer land and asset documents to another company

</details>

4. **Owner** - The user that created the project
5. **Origin** - Indicates where the project was created (Stack or Land)

{% hint style="info" %}
**Stack** - The project was created within StackDX

**Land** - The project was originally created in CS Land and added to StackDX in the nightly data sync
{% endhint %}

6. **Active** - Indicates the project status (ie. Active or Inactive)
7. **Criteria** - Indicates if the project uses a set criteria to populate. There are options to have it updated manually or auto update nightly. See Create & Manage section for more details.
8. **Internal Access** - The user permissions required to access the project

There are 6 different internal access settings - Contacts Only, All Internal, Land Read, Land Write, Assets Read, Wells & Locations Write.

<details>

<summary>Internal Access Settings</summary>

**Contacts Only**: The project is only accessible to specific internal or external users&#x20;

**All Internal**: The project can be accessed by all users at your company

**Land Read**: The project is only accessible to users with Land Read role

**Land Write**: The project is only accessible to users with Land Write role

**Assets Read**: The project is only accessible to users with Assets Read role

**Wells & Locations Write**: The project is only accessible to users with Wells & Locations Write role

</details>

9. **Related To** - The totals for the land files or assets in the project
10. **Added** - The Date/Time the project was created


---

# 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, and the optional `goal` query parameter:

```
GET https://help.stackdx.com/projects/company-owned-projects/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.