Permission profiles determine who can view and manage custom, live, and big objects, the objects you add to Rippling. These profiles are configured in the Object Permissions app.
For Rippling objects, including employee and people data, see Permissions for data in Rippling.
Components of an object permission profile
Object permission profiles have three key components:
- Assignment. The people to whom the profile is assigned.
- Access. The type of access assignees have to objects and records.
- Scope. Criteria that determine the specific set of records assignees can access.
Assignment
Each object permission profile can be assigned to one or more people.
You can assign profiles to any user in Rippling. Use Supergroups to assign profiles dynamically based on user attributes, or assign them to specific individuals.
Access
Each permission profile specifies the level of access that assignees will receive. There are three types of access:
- Access to the object schema.
- Access to the record data.
- Access to the fields in the records.
Object access
If you think of an object as a spreadsheet, access to the object lets you see and manage the spreadsheet. There are two levels of access:
- Standard access lets you view the spreadsheet.
- Admin access lets you change the columns and settings of the spreadsheet.
Record access
Access to records lets you see or change the contents of the data in the object, which are like the rows in a spreadsheet. This includes access to view, edit, create, or delete records.
Field access
Once you have access to records, your access can then be restricted to specific fields. Fields are like the columns in a spreadsheet.
Scope
Permission profiles that grant record access (view, edit, create, or delete) also include criteria that define the scope of the access, in other words, the specific set of records assignees will be able to access.
There are four ways you can set the scope:
- All company. The assignee can view all of the records that exist in the object.
- Direct and indirect reports. The assignee can view records owned by their direct and indirect reports.
- Self. The assignee can view records they themselves own.
- Custom. The assignee can view records identified by custom criteria you define. For example, you could give teachers access to view all of the classes offered by their department, or give sales engineers access to view all deals with amounts over $50,000.
The owner of a record is the person populated in the owner field.
By default, the person who creates a custom object is the object’s owner. The owner receives implicit permission to manage the objects they create. However, you can remove this access by removing them as the owner. They will then be subject to the permission profiles you've set up for the object.
Best practices & examples
As a best practice, we recommend setting up one permission profile for each type of user that needs data access.
Example 1: Vehicle maintenance
Imagine you want to capture vehicle maintenance logs and store them in a custom object in Rippling.
You have a data analyst who will be responsible for importing the initial dataset to Rippling and managing its fields, settings, and permissions. The people in your delivery department will log vehicle maintenance activities, but you don’t want them to be able to change the data’s structure.
In this case, you will set up the following object permission profiles:
- A Data analyst profile that gives your data analyst admin permission for the object and no access to the records in the object.
- A Delivery driver profile that gives people in your delivery department standard permission for the object and access to view and edit their own records.
Example 2: Incident reporting
Say you’ve set up a custom app to track company incidents. Your company’s incident manager is responsible for managing the process and tracking incident data. You’ll want to set up the following custom object permission profiles:
- An Incident reporter profile that gives everyone access to create incident records.
- An Incident supervisor profile that gives managers the ability to create their own incidents and view the details of incidents created by the people who report to them.
- An Incident manager profile for your company’s incident manager, providing full access to view and manage all incident records, as well as admin access to the custom objects containing the data.
Example 3: Help desk ticketing
Say your company has a custom app that lets employees file requests with the HR department. Each request includes a field that calculates the cost to resolve the ticket based on the amount of time it remained open. However, you only want the HR department and your operations team to be able to see this field. Set up the following permission profiles:
- A Ticket requester profile that gives everyone access to create tickets and view the tickets they’ve created, but that keeps the Cost field hidden.
- A Ticket reviewer profile that gives members of your HR team and your operations team access to view all tickets, including the Cost field.
For additional examples, see Access to custom apps.