> For the complete documentation index, see [llms.txt](https://docs.diracinc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diracinc.com/how-to-be-successful-in-buildos/concepts/sharing-and-ownership.md).

# Sharing and ownership

This will cover ownership and share functionality for your projects.

## Project ownership

A project in BuildOS has an owner user, and the latest revision in a project has an owner (these can be the same person). These owners and team administrators can control who has access to the project and its instruction revisions.

Note that only the owner of the latest instruction revision can make edits to the drafted instructions.

## Sharing and access

A project can be shared with an individual user or across your entire team. BuildOS can be deployed in GovCloud secure networks, and its sharing functionality provides need-to-know access controls for sensitive documents.

When a project is created, it is not shared with any other user by default. To share a project with a user:

1. Click the share button in the top right to open the Share menu
2. Add users, or make the project available to your entire team

## Transferring ownership

If you are a project or revision owner, or a team admin, you can transfer ownership to another user from the Share menu.

{% hint style="info" %}
Each [subassembly](/how-to-be-successful-in-buildos/concepts/phantoms-and-subassemblies.md) has its own work instruction, and therefore its own owner. This lets you hand individual subassemblies to different engineers and build out a large project in parallel.
{% endhint %}

## Floating Licenses

Floating licenses allow your organization to share a pool of BuildOS licenses among multiple engineer accounts. Instead of assigning a fixed license to each engineer, licenses are checked out when someone logs in and returned when they log out, making them available for other users.