> 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/partner-enablement/assets/define-access-on-assets.md).

# How to define access on assets?

In Kiflo an asset can be shared with everyone, to your team, or a specific partner, partner level, or group.

## How to define access?

Under **Manage** > **Assets**, you can either **edit** a current asset or **add** a new asset to define **"Who has access"**; the main reason to define **"who has access"** is to give the user the ability to share assets with the relevant party. For example, a reseller program will have more sales-orientated assets whereas an affiliate will have more marketing-orientated assets. **"Who has access"** allows you to differentiate assets.

The screenshot below shows you wherein the user interface you can define who has access:

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

## Access type: My team

The first type of **"Who has access"** is called **"My team"**. If you want to share internal assets with your coworkers you can do so by defining the access as **"My team"**. Partners won't have access to those assets at all.

## Access type: Some partners

The second type of **"Who has access"** is called **"Some partners"**. Below are the types under **"Some partners":**

#### Select one or multiple programs

* You can define access to a specific partner program level. An example of this is everyone in your Referral Program Gold Level/Tier will have access to these asset/s.

#### ![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-a728513a23fb2d4592899224230bbb96d671ff05%2F6124ef53b55c2b04bf6e11c0.png?alt=media)Select one or multiple groups

* You can define access to a specific group. Groups are defined under **Manage** > **Groups.** An example of this is everyone in the group Asia gets access to these asset/s.

#### ![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-00d302d1939a311fe92b909156e78e4ce08edd98%2F6124efcc6ffe270af2a9b999.png?alt=media)Select one or multiple partners

* You can define access to a specific partner. An example of this is your partner "Amazon" gets exclusive access to these asset/s.

<figure><img src="https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-acbd23c68915cf673b982fcb524f050fb14da20b%2F6124f061f886c9486f8db94a.png?alt=media" alt="" width="337"><figcaption></figcaption></figure>

## Access type: Everyone

The third type of **"Who has access"** is called **"Everyone"**. If you want to share assets with all users (coworkers & all partners) you can do so by defining the access as **"Everyone"**.


---

# 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/partner-enablement/assets/define-access-on-assets.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.
