# Overview of people data sensitivity classifications

> How Rippling categorizes employee and people data as personal or employment, and as basic, non-sensitive, or sensitive.

## How Rippling categorizes people data

As your people management platform, Rippling is home to a large amount of company and employee data. Some of that data is visible to everyone, and some data is only visible to users with certain permission profile settings, as set up in the Permissions app.

Everyone hired into Rippling has a profile that contains information about them and their role with the company. Each data field within the profile is categorized in two different ways:

-   It’s categorized as either **personal** or **employment** data.
-   It’s assigned a **data sensitivity classification**.

## Personal vs. employment data

Each person’s profile contains both personal details and information about their employment.

| Examples of personal data | Examples of employment data |
| --- | --- |
| -   Preferred first name<br>-   Home address<br>-   Phone number<br>-   Date of birth | -   Employment type<br>-   Work location<br>-   Compensation<br>-   Pay schedule |

You can assign permission to manage personal data separately from permission to manage employment data. For example, you may give HR business partners permission to view both personal and employment details, while preventing Finance admins from seeing most personal information.

## Data sensitivity classifications

Each personal or employment data field in Rippling is assigned one of three sensitivity classifications.

| Classification | Examples | Description |
| --- | --- | --- |
| Basic | -   Preferred name<br>-   Department<br>-   Title<br>-   Manager<br>-   Work email<br>-   Start date | Basic data is information that is generally considered okay to share with anyone. |
| Non-sensitive | -   Home address<br>-   Personal email<br>-   Phone number<br>-   Date of birth<br>-   T-shirt size<br>-   Level<br>-   Teams\*<br>-   Employment type<br>-   Manager’s email | Non-sensitive data includes information that you may want a more limited set of people to see. This includes information you want to hide from most employees, but that managers or admins may need to see in order to fulfill their duties. |
| Sensitive | -   Social Security number<br>-   EIN<br>-   Compensation details<br>-   Termination details | Sensitive data includes information you only want a few people to see so they can complete important tasks such as running payroll or processing a termination. |

\*Teams is classified as non-sensitive employment data in user profiles, but available for anyone to view and use in automations and reports.

This table lists just a few examples of the types of fields you’ll find within each sensitivity classification. You can see a full listing of the fields belonging to each classification when you’re setting up a permission profile in the Permissions app.

> **Tip:**
> Field classifications for the Super admin profile are listed on the **People data** tab.

## How custom fields are classified

When you add custom fields to the _Employee_ object Rippling, you assign a data category (personal or employment) and sensitivity classification (basic, non-sensitive, or sensitive) to each field. Together, these determine who will be able to view and edit the field.

## See also

-   [Permissions for data in Rippling](https://developer.rippling.com/documentation/rippling-platform/data-model/permissions)
-   [Assign permission to people data](https://developer.rippling.com/documentation/rippling-platform/data-model/assign-people-data-permissions)
-   [Object permissions](https://developer.rippling.com/documentation/rippling-platform/data-model/object-permissions)

Source: https://developer.rippling.com/documentation/rippling-platform/data-model/employee-data-classifications

> For the complete documentation index, see [llms.txt](https://developer.rippling.com/llms.txt). Public pages have a Markdown version at the same URL with .md added.
