> For the complete documentation index, see [llms.txt](https://support.pears.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pears.io/plan/community-events/collaborators.md).

# Collaborators

Learn how to add, edit, and remove collaborators on a community event in PEARS.

The Collaborators section allows the creator of a community event to grant other PEARS users access to view or edit the record. Collaborators can also be designated as contributors to the event.

{% hint style="info" %}
**TIP:** Only staff members that have active PEARS accounts can be added as collaborators. The creator of the record is automatically listed as a collaborator with **View & Edit** access, **Contributor** status, and **Event Organizer** status.
{% endhint %}

## Navigate to Collaborators

After saving a new community event, PEARS automatically takes you to the Collaborators page. You can also access it by opening an existing event and clicking the **Collaborators** tab in the progress panel.

## Add a Collaborator

{% stepper %}
{% step %}

#### Click Add Collaborator

On the Collaborators page, click the **Add Collaborator** button. A dialog box appears.
{% endstep %}

{% step %}

#### Select a User

In the **User** field, search for and select the PEARS user you want to add as a collaborator.
{% endstep %}

{% step %}

#### Set Access Level

In the **Access** field, choose the level of access for the collaborator. The default is **View & Edit**.

* **View & Edit** — The collaborator can view and make changes to the event.
* **View Only** — The collaborator can view the event but cannot make changes.
  {% endstep %}

{% step %}

#### Mark as Contributor (optional)

Check the **Contributor** checkbox if this collaborator directly contributed to the planning or delivery of the event.

Check **This user is an event organizer.** to send replies to registration emails to this user and let people filter events by this user on the public site.

{% hint style="info" %}
**TIP:** Marking a collaborator as a contributor allows you to track who was involved in organizing the event. Contributors are displayed on the event detail page and may be included in reports.
{% endhint %}
{% endstep %}

{% step %}

#### Save the Collaborator

Click **Save** to add the collaborator. The collaborator now appears in the list on the Collaborators page.
{% endstep %}
{% endstepper %}

## Edit a Collaborator

To edit an existing collaborator, click the **Edit** button next to their name. Update the access level, contributor status, or event organizer status, then click **Save**.

## Remove a Collaborator

To remove a collaborator, click the **Remove** button next to their name. If you are removing yourself, PEARS asks you to confirm before your access is revoked.

![Screenshot: The Collaborators page for a community event showing the list of collaborators with their names, access levels, contributor status, and Edit/Delete buttons](https://2560412328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff0820LrBGQ9ZA8SC4BR1%2Fuploads%2Fgit-blob-e5b06c7ed60845ae40139a92be4264594ca1cf4f%2Fcommunity-event-collaborators-list.png?alt=media)

{% hint style="warning" %}
**NOTE:** Removing a collaborator immediately revokes their access to the event. This action cannot be undone — you will need to re-add them if you want to restore their access.
{% endhint %}

## Continue to the Next Step

After adding collaborators, click the **Save and Continue** button to proceed to the next section of the workflow. If your organization has set up [custom data](/getting-started/getting-started/custom-data.md) for community events, the next step is **Custom Data**. Otherwise, if the event has multiple sessions, the next step is [Event Sessions](/plan/community-events/event-sessions.md). If the event is promotional, you proceed to [Publish](/plan/community-events/publish-an-event.md). Otherwise, you will proceed to [Registration Types](/plan/community-events/registration-types.md).