# Script and media review permission

### Script permission

| Script                                         | Who can access                                       |
| ---------------------------------------------- | ---------------------------------------------------- |
| Private script (doesn't belong to any project) | Script collaborator                                  |
| In private-to-member project                   | Project member and script collaborator               |
| In public-to-team project                      | Team member, project member, and script collaborator |

#### Private script

<figure><img src="/files/IAMJLizksw06R0KPtmu8" alt=""><figcaption></figcaption></figure>

Script tasks created in "[**My task**](/en-us/fundamentals/my-task.md)" by default are not assigned to any project or collaborators. Only the script creator and those invited as collaborators can access these private scripts not linked to a project.

**To share a private script:**

1. Add a script to a project so all project members and the team associated with the project can access the script;
2. Add someone as a collaborator so he can access the script.

#### Private-to-member script <a href="#h_01hh23zjwpt6td0qyk4ef4ze9w" id="h_01hh23zjwpt6td0qyk4ef4ze9w"></a>

<figure><img src="/files/tLQUCN4KpJcExtCzz7mC" alt=""><figcaption></figcaption></figure>

The "Private to Members" privacy setting for a project limits access exclusively to current project members and script collaborators. When others obtain the script link and try to access it, they will see a prompt indicating they do not have permission to access it.

<figure><img src="/files/lRD0DmEdnf9c5SbbBHe1" alt=""><figcaption></figcaption></figure>

**To share a private-to-member script**:

1. **Add someone as a script collaborator** - This action grants the individual access only to that specific script. If they are already a member of the project, they would already have access to the script;
2. **Add someone as a project member** - This gives the individual access to all scripts within the project;
3. **Change the project's privacy setting to public-to-team** - Making the project public to its team and sharing it allows all team members to access the project and scripts.

#### Public-to-team script

<figure><img src="/files/sBTzOn8TWRWTj1Rsrvwm" alt=""><figcaption></figcaption></figure>

Public-to-team scripts can be accessed by project members, script collaborators, and members of the team to which the project belongs.

**To share a public-to-team script:**

1. **Add someone as a script collaborator** - Doing so grants them access to the script. If they are already project or team members, they would already have access to the script.
2. **Add someone as a project member** - After being added as a project member, they can access all scripts within the project. If they are team members, they already have access to the script.
3. **Add someone as a team member** - Once added as a team member, they can access all public-to-team scripts.

### Media review permission

| Media review                 | Who can access                                             |
| ---------------------------- | ---------------------------------------------------------- |
| in private-to-member project | Project member and media review collaborator               |
| In public-to-team project    | Team member, project member, and media review collaborator |

**Media review in a private-to-member project**

<figure><img src="/files/8J2WccBWcmEVuLLnmhLF" alt=""><figcaption></figcaption></figure>

The "Private to Members" privacy setting for a project limits access exclusively to current project members and media review collaborators. When others obtain the media review link and try to access it, they will see a prompt indicating they do not have permission to access it.

<figure><img src="/files/lRD0DmEdnf9c5SbbBHe1" alt=""><figcaption></figcaption></figure>

**To share a private-to-member media review task:**

1. **Add someone as a media review collaborator** - This action grants the individual access only to that specific media review task. If they are already a member of the project, they would already have access to the task;
2. **Add someone as a project member** - This gives the individual access to all media review tasks within the project;
3. **Change the project's privacy setting to public-to-team** - Making the project public to its team and sharing it allows all team members to access the project and media review tasks.

**Media review in a public-to-team project**

<figure><img src="/files/dsaPYC3VrcQCsneQdLCZ" alt=""><figcaption></figcaption></figure>

Public-to-team media review tasks can be accessed by project members, media review collaborators, and members of the team to which the project belongs.

**To share a public-to-team media review task:**

1. **Add someone as a media review collaborator** - Doing so grants them access to the media review task. If they are already project or team members, they would already have access to the task.
2. **Add someone as a project member** - After being added as a project member, they can access all media review tasks within the project. If they are team members, they already have access to the task.
3. **Add someone as a team member** - Once added as a team member, they can access all public-to-team media review tasks.

> Like what you see? Get started with a free 30-day CreatiBI trial today. [<mark style="color:blue;">Try for free</mark>](https://creatibi.com/)<mark style="color:blue;">.</mark>

### Related articles

{% content-ref url="/pages/18CzZSNa0OzlZk8gmm1E" %}
[Project](/en-us/fundamentals/project.md)
{% endcontent-ref %}

{% content-ref url="/pages/SCDoG6FQvNCdhUwaO2Td" %}
[Project setting](/en-us/fundamentals/project/project-setting.md)
{% endcontent-ref %}

{% content-ref url="/pages/i9hS5SDS6JfdrufSVBHM" %}
[Project owner and member](/en-us/fundamentals/project/project-owner-and-member.md)
{% endcontent-ref %}

{% content-ref url="/pages/kowurVpvufK47IAueai6" %}
[Project permission](/en-us/fundamentals/project/project-permission.md)
{% endcontent-ref %}

{% content-ref url="/pages/OBZrERslk2IXZ1mB9zj8" %}
[Project overview](/en-us/fundamentals/project/project-overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/hSfyWKsMWp7FUmpgNKCq" %}
[Project tab](/en-us/fundamentals/project/project-tab.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://help.creatibi.com/en-us/fundamentals/project/script-and-media-review-permission.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.