> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/account-settings/properties/change-properties-visibility.md).

# How to change properties visibility for partners?

When you edit available properties on leads, deals, contacts, or customers you can change the partner's permissions.

{% hint style="info" %}
**This article concerns only**

* Leads
* Deals (only for *Scale* plan)
* Contacts (only for *Scale* plan)
* Customers
  {% endhint %}

## Available options

It's possible to choose between those 3 options:

**Is the property visible for all partners?**

By checking this option all partners can see the property and the value associated. It is read-only access.

**Is the property editable for all partners?**

By checking this option all partners can edit the property. No matter what you set on your side, partners can overwrite the value.

**Is the property displayed by default as a column in all tables?**

By checking this option the property will be displayed as a default column. It's useful to be sure your partners see the information you provide on leads or deals.

Example:

You create a new "NPS" (Net Promoter Score) property on **Leads** and you want it to be visible next the to lead's name on the Leads page.

## Edit partner's permissions

To change partner permissions on an existing property:

* Go in **Account > Properties** (top right corner menu)
* Select the object you want to edit (**Leads, Deals, Contacts, Customers**)
* Click the **Edit** button on the property you want to edit:

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-967e3f768c40f82d8095adb2b9c6a25b10bec68f%2F60c0f0f94173c622df92a160.png?alt=media)

## Visibility confirmation

If you have private information that you absolutely don't want to share with partners, you need to be sure that the data won't be disclosed.

The level of visibility is displayed next to each property. If you see this icon it means the property is visible by the partner:

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-e3e1e50486cb83f9920dcf4dd5a074ed4c145ceb%2F60c0f499bf1166357a3ff77e.png?alt=media)

Example on a lead:

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-410f5df408dce2af98a71ce1e53958a80569a2ff%2F60c0f45e4173c622df92a181.png?alt=media)


---

# 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://docs-vnext.kiflo.com/account-settings/properties/change-properties-visibility.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.