> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/3d-modeling-and-design/t4r/list-of-features/bimsign.md).

# BIMSign

Protect your projects, families or templates with permanent invisible signature

**Icon:** <img src="https://content.gitbook.com/content/qtUsszuAWXIZhQhrvjnb/blobs/qgIPYzISKNTNjZ8IdGk3/image" alt="" data-size="line">

**Location:** ribbon Be.Smart T4R, panel Project

**Packages:** Be.Smart T4R

{% hint style="info" %}

#### Main functionalities and benefits:

* Allows you to prove ownership of the BIM-document
* Solves the need to provide a certain level of security for your BIM-content
  {% endhint %}

### **Overview**

The function BIM Sign watermarks your BIM document (a RVT project, RFA family or template .RTE/.RFT) with a permanent invisible signature. At any moment, you can then read this signature from the document and prove ownership (intellectual property, IP) of the given document. The signature reading functionality is active even without the Holixa T4R license, e.g. after its Trial version expires.

BIMsign does not prove an unmodified state of the original document (like digital signature does), it proves that a document is based on your original data. Non-authorized users cannot remove the BIM signature. The signature remains part of the BIM file even if the BIMsign utility is not installed on a Revit workstation.

### **1. Main screen**

Document status signed/not signed

![](https://content.gitbook.com/content/qtUsszuAWXIZhQhrvjnb/blobs/yqbPJANfsKDkda4XE6BZ/image)

### 2. Signing a document (password is not set yet)

![](https://content.gitbook.com/content/qtUsszuAWXIZhQhrvjnb/blobs/5muiXNUQh0LnLaHVi6e9/image)

### 3. Setting/changing password

![](https://content.gitbook.com/content/qtUsszuAWXIZhQhrvjnb/blobs/uUrhoFoj32opYcEBXCby/image)

### 4. Signing a document

![](https://content.gitbook.com/content/qtUsszuAWXIZhQhrvjnb/blobs/xO1Sf8vH6ESZkZp0yTVG/image)

### 5. Document is signed

![](https://content.gitbook.com/content/qtUsszuAWXIZhQhrvjnb/blobs/NbG9UQ6mchWuUsTGU5wL/image)

### 6. Deleting Sign

![](https://content.gitbook.com/content/qtUsszuAWXIZhQhrvjnb/blobs/1dcwDow5xEmFVqwyl8yw/image)


---

# 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.besmart.software/3d-modeling-and-design/t4r/list-of-features/bimsign.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.