> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: Permissions

## Article: Permissions

## Article Link: https://dev.wix.com/docs/api-reference/business-management/calendar/permissions.md

## Article Content:

# Permissions

By default, site visitors can see only public information for
[schedules](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/introduction.md)
and [events](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/introduction.md).
They can't access any personal information. For your app, you can choose the
[permission scopes](https://dev.wix.com/docs/build-apps/develop-your-app/access/authorization/about-permissions.md)
that give the necessary access and request which data is returned in each method
of the [Schedules](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/introduction.md)
and [Events](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/introduction.md)
APIs.

## Retrieve personal information

Use the `field` parameter in requests for the Schedules and Events APIs to
customize which fields are included in the response.

| Value passed in `field` | Returned fields and values |
|--------------------------|----------------------------|
| `null` or not provided    | Only non-personal fields are returned. For a list of fields considered personal, see [Events: Fields with personal information](#events-fields-with-personal-information) and [Schedules: Fields with personal information](#schedules-fields-with-personal-information). |
| `PI_FIELDS`              | Returns complete objects, including all values. <br/> Requires the `Read Calendars - Including PI` [permission scope](https://dev.wix.com/docs/build-apps/develop-your-app/access/authorization/configure-permissions-for-your-app.md). |
| `OWN_PI_FIELDS`          | Returns complete objects, but excludes personal information of anyone other than the caller's [identity](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities.md) from the returned values. |

### Events: Fields with personal information

In methods of the [Events API](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/introduction.md),
the following fields aren’t returned by default:

+ `participants`
+ `conferencingDetails`
+ `notes`
+ `location.name` and `location.address` (if `location.type` is set to `CUSTOMER`)

These fields are only returned if you set `fields` to `PI_FIELDS` or `OWN_PI_FIELDS`
and your app has the necessary permissions.

### Schedules: Fields with personal information

In methods of the [Schedules API](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/introduction.md),
the following fields aren’t returned by default:

+ `defaultConferencingDetails`
+ `defaultLocation.name` and `defaultLocation.address` (if `defaultLocation.type` is set to `CUSTOMER`)

These fields are only returned if you set `fields` to `PI_FIELDS` or `OWN_PI_FIELDS`
and your app has the necessary permissions.

## Roles

For both [schedules](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/schedule-object.md)
and [events](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/event-object.md),
you can assign roles to [Wix users](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities.md#wix-users)
giving them specific access to the relevant entity.

This table summarizes permission roles and their access levels:

| Role     | Access Level                             |
|----------|------------------------------------------|
| `WRITER` | Full read and write access.              |
| `COMMENTER` | Full read access, write access limited to `event.notes`. |

### Roles for schedules

To grant a Wix user access to a
[schedule](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/schedule-object.md),
include the relevant ID in `schedule.permissions.identity.wixUserId` and specify their
role in `schedule.permissions.role`.

### Roles for events

You can assign access levels to
[Bookings staff members](https://dev.wix.com/docs/rest/business-solutions/bookings/staff-members-and-resources/about-staff-members-and-resources.md)
associated with an event by specifying their role in the
`event.resources.permissionRole` field. By default, Bookings staff members don't
have access to [classes](https://dev.wix.com/docs/rest/business-solutions/bookings/terminology.md#class)
they conduct, as the schedule is linked to the service rather than the individual
staff member.

To check which additional Wix users have access to the
[event](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/event-object.md),
refer to the `event.permissions.identity.wixUserId` field along with the
corresponding `event.permissions.role`.